Rovo Slack integration fails with HTTP 400 despite Org Admin access

[Maxime Doucet]

Hello Atlassian Community,

I’m trying to connect Rovo to Slack for our Atlassian organization, but I’m blocked during the onboarding with the following error:

HTTP error! status: 400

However, I am an Atlassian Org Admin, and the issue persists.

Context:

• Atlassian site: a******.atlassian.net

• I am confirmed Org Admin in admin.atlassian.com

• Slack app installation flow reaches the “Add site” step, then fails

• Rovo agent selected correctly

• Bot account: *******

• Same user is Org Admin but not Slack admin

• Slack workspace and Atlassian org are already connected

• Error occurs consistently (multiple attempts, same result on different browser)

Questions:

1. Does this error indicate a missing Rovo / Atlassian Intelligence activation at the org or site level?

2. Are there known limitations or prerequisites for enabling Rovo in Slack (plan, rollout, site eligibility)?

3. Is this a known issue with the Slack ↔ Rovo onboarding flow returning a generic “org admin” error?

4. Are there logs or checks we can run to diagnose the HTTP 400 response?

Happy to provide screenshots or additional details if needed.

Thanks in advance for your help.

Best regards,

[Dr Valeri Colon _Connect Centric_ · Accepted solution]

Welcome to the community @Maxime Doucet A 400 during the Slack→Rovo onboarding usually isn’t an Org Admin issue. It happens when the Slack workspace hasn’t granted the required permissions, when the site isn’t fully enabled for Rovo in Slack, or when rollout flags aren’t active for your tenant. Being Atlassian Org Admin isn’t enough if you’re not a Slack Admin—Slack must approve the app install. Also confirm Rovo is enabled under Administration → Rovo. If it still fails, Support must check backend flags; a 400 is a known generic error in this flow.

[Maxime Doucet]

Thanks again — really appreciate the help.

Just to confirm: Rovo is already enabled in our org under admin.atlassian.com → Rovo, and our IT team (Slack workspace admins) has also validated that the Slack app install/approval is allowed.

Despite that, the onboarding still fails consistently at the “Add site” step with:

HTTP error! status: 400

At this stage, it feels like this may indeed be related to tenant rollout flags or a backend prerequisite rather than permissions on our side.

One challenge is that when we try to open a Support ticket for Rovo, we get redirected back to the Community instead of a support request form.

Is there an official escalation path or Atlassian Support channel for cases like this, where backend checks are required?

Thanks in advance.