Current status.
Atlas lists a Slack connector in Settings, then Integrations, and our team is building it now. Until it is finished there is no Connect button. You cannot link a Slack workspace to Atlas today, and nothing on this page should be read as a working Slack integration.
If Slack matters to your team, tell us. Until then, the options below work with Slack now.
What the listing describes.
When Atlas enables it, the listing describes a connector that an Atlas owner or administrator links with OAuth 2.0. It would post task and project notifications into channels you choose, with a default channel and one channel per project, turn a Slack message into an Atlas task from the message actions menu, and add an /atlas command for creating tasks and lookups. None of this works yet, and the details may change before it ships.
What works today.
Register a signed webhook for events such as task.created, task.completed, and comment.created. Send it to a Slack workflow that starts from a webhook, or to a short relay script that posts to Slack.
An Atlas automation can call a webhook when something happens, for example when a deal changes stage or a form is submitted.
From a Slack workflow or your own bot, create a task in Atlas with one authenticated POST to the REST API.
Point an AI client that already has Slack access at the Atlas MCP server, so one agent can work across both.
If requests reach your team by email, the Gmail connector is available now and brings threads into Atlas.
Example: send Atlas task events to a Slack workflow
# Register a webhook. The URL is your Slack workflow's webhook trigger or your relay. curl -X POST https://api-atlas.wrxstack.com/v1/webhooks \ -H "Authorization: Bearer $ATLAS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "url": "https://hooks.slack.com/triggers/YOUR_TRIGGER_PATH", "events": ["task.created", "task.completed"] }'
Example: create an Atlas task from Slack
# Call this from a Slack workflow step or your own bot. Sample project ID. curl -X POST https://api-atlas.wrxstack.com/v1/tasks \ -H "Authorization: Bearer $ATLAS_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "projectId": "YOUR_PROJECT_ID", "title": "Follow up on the request from #support" }'
Today versus listed.
| Need | Direction | Today | Notes |
|---|---|---|---|
| notifications | Atlas → Slack | Webhooks | Signed webhook to a Slack workflow or relay. No native channel picker yet. |
| message to task | Slack → Atlas | REST API | A Slack workflow step or bot calls POST /v1/tasks. No message action yet. |
| /atlas command | Slack → Atlas | In development | Needs the Slack connector, which is in development. |
| AI across both | Both | MCP server | An AI client with Slack access can also use the Atlas MCP server. |
Security model.
Atlas signs each webhook delivery, so your receiver can check that it came from Atlas. Webhook URLs must be public HTTPS endpoints. API calls use a personal access token or OAuth, scoped to what the token allows. Because the Slack connector is still in development, Atlas holds no Slack credentials and reads nothing from Slack.
Questions.
- There is no Connect button for Slack.The connector is in development for every workspace. There is nothing for you to configure.
- When will it be available?There is no date. This page will change when the connector ships.
- My webhook deliveries fail.Check that the URL is public HTTPS and returns a 2xx status. Atlas lists each delivery and lets you replay one from the webhook settings.