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,