Slack Integration
Run your AI DevOps team where your team already talks. Currently in private beta.
IaCConsole can answer infrastructure requests directly in Slack: describe what you need in a DM, mention the bot in a channel, or use a slash command. The same agents that power the web console — Team Leader, Senior DevOps, DevSecOps, and FinOps — reply in the thread, and drafts are posted as interactive cards with a review link.
Availability
Slack is in private beta. We onboard workspaces one at a time: there is no self-serve signup, and we set it up together on a short call.
| Status | Private beta |
| Self-serve | Not yet — we onboard each workspace with you |
| Demo | The IaCConsole community Slack |
| Get access | Book a 15-minute call or email dima@iacconsole.com |
You can try the demo in the community workspace before requesting access for your own Slack. That workspace runs on a sample account, so the projects and environments you see there are illustrative, not customer infrastructure. If the beta fits what you need, we set it up for your workspace.
What you can do
- Ask in plain language. “Create a staging VPC in eu-central-1 with two private subnets” works the same way it does in the console.
- Work in threads. The bot keeps the conversation context, so follow-up questions do not need to repeat the original request.
- Review before applying. When a request produces a change, the bot posts a Project Draft as a Block Kit card with a summary and a link to review it in the console.
- Use the Assistant. The Slack Assistant framework is supported, with suggested prompts such as setting up a VPC or running a security audit.
- Stay on standard Terraform. Anything generated remains standard Terraform or OpenTofu HCL you can export and run yourself.
Entry points
| How | Example |
|---|---|
| Direct message | Message the IaCConsole bot directly |
| Channel mention | @iacconsole-teamlead what is in my prod workspace? |
| Slash command | /iacconsole-teamlead create a staging environment for the api service |
Slack requires an acknowledgement within three seconds, so the bot replies immediately with a short “working on it” message and posts the real answer when the agents finish.
How the connection works
- Book a call and we set Slack up for your account.
- In the web console, open Settings and click Connect Slack.
- Authorize the app for your workspace. You are redirected back to Settings with a confirmation.
- Invite the bot to the channels where you want to use it, or message it directly.
- Try a read-only request first, for example:
/iacconsole-teamlead list the dimensions in my org.
You can remove the app from your workspace at any time in Slack’s admin settings. That immediately stops all Slack-side access; your infrastructure and Terraform state are unaffected.
Permissions requested
The OAuth install requests these scopes:
| Scope | Why |
|---|---|
commands |
Slash commands |
chat:write |
Post replies and Block Kit cards |
app_mentions:read |
Respond when the bot is mentioned |
files:write |
Attach generated files to a thread |
channels:history, groups:history, im:history, mpim:history |
Read thread context so follow-ups work |
assistant:write |
Slack Assistant suggested prompts |
reactions:write, reactions:read |
Status reactions while a request is running |
For what we store on our side, see Privacy.
Billing
Slack conversations are billed like any other Managed Cloud interaction, against your organization’s token quota at the standard rates: $0.55 per 1M input tokens and $3.30 per 1M output tokens. Nothing is billed from within Slack itself.
Write protection
VirtualGitOps branch protection applies to Slack exactly as it does to other AI entry points. Agents can read the master workspace, but set_dimension and delete_dimension calls against master are rejected. Changes must happen on an isolated workspace and be merged through the normal review flow.
Requirements
- A Managed Cloud account (the beta is not available on the free CLI tier).
- Admin permission on the Slack workspace, to install the app.
- An AWS or GCP environment you already control. IaCConsole does not need your cloud credentials for Slack; execution follows the same Secure Agent Mode path as the console.
Related
- MCP integration — connect other AI clients to your inventory
- VirtualGitOps — how workspaces and branch protection work
- CLI guide — run the same workflow locally
Frequently asked questions
Is the Slack integration available to everyone?
No. It is in private beta and we onboard workspaces one at a time. You can try the demo in our community Slack, then book a call to set it up for your own workspace.
How do I connect my own Slack workspace?
Once it is set up for your account, open Settings in the web console, click Connect Slack, and authorize the app. Then invite the bot to a channel or message it directly.
Can the Slack bot change my production infrastructure?
Not directly on master. VirtualGitOps branch protection blocks write tools against the master workspace from every AI entry point, including Slack. Changes are proposed on an isolated workspace for review.