Tool integrations
Connect Notion, Google Workspace, and Slack so agents can pull context and push updates.
Tool integrations
Wire up the tools your agency already uses. Don't re-paste data you've already typed once.
The 30-second version
From Settings → Integrations → Tools, connect Notion, Google (Drive / Workspace), or Slack via OAuth. Connected providers show up as available tools you can grant to a custom agent. Pulling pasted-content from connected tools at workroom creation, and pushing approval notifications to Slack, are the most common uses.
Why this matters
Your client briefs already live somewhere — in a Notion page, a Drive folder, or a Slack thread. Connecting those tools to AtelyaOS means agents can read that context directly instead of you copy-pasting. It also means workroom approvals can land where your team already works (Slack), not in a separate inbox.
How it works
Supported providers
| Provider | Status | Use cases |
|---|---|---|
| Notion | OAuth wired | Pull client briefs, push approved deliverables. |
| Google Drive / Workspace | OAuth wired | Pull brand assets, sample work, brief documents. |
| Slack | OAuth wired | Approval notifications, workroom status updates. |
| MCP custom | Self-host | Wire up a custom tool via the Model Context Protocol. |
| Custom webhook | Outgoing | Send workroom events to your own endpoint. |
[SCREENSHOT: integrations tools page with providers listed]
Connecting a provider
- Go to Settings → Integrations → Tools.
- Click the provider tile (Notion, Google, Slack).
- You'll be redirected to the provider's OAuth screen. Approve the requested scopes.
- You'll land back on AtelyaOS with the connection visible in the list.
OAuth tokens are encrypted at rest with a per-workspace key — see encryption.
Granting tools to agents
Connecting a provider doesn't automatically expose it to every agent. You grant tools per agent in the Tools tab of the agent builder. Each grant is explicit: "Aurora Coffee — Proposal Drafter has read access to Notion workspace X."
This is intentional — you don't want a general-purpose writing agent silently calling out to your CRM.
Workroom-level tool calls
When the Planner produces a task plan, it may include tool_call task types. Those tasks invoke a granted tool (e.g. fetch a Notion page, list a Drive folder). The tool's output feeds the next task.
Note: pulling content from connected tools into a workroom at creation time is best done by pasting the content yourself today. Direct "import from Notion" workroom creation is on the roadmap; the current "Use connected tools" entry point in the new-workroom chooser is a placeholder that links you to the integrations settings.
Roles and access
Only owner and admin roles can connect or disconnect providers. member and viewer can use tools that an agent has been granted, via workrooms.
Disconnecting
From the integrations page, click Disconnect on the provider tile. The OAuth token is revoked and removed from the database. Existing tool grants on agents become inactive.
Common pitfalls
- Connecting Slack and never granting any agent the tool. Connection alone doesn't do anything. The agent needs an explicit grant.
- Granting
tool_grantstoo broadly. Don't give a general writer agent access to your CRM "just in case." Grant the minimum. - Expecting auto-import. Today, pulling brief content from a Notion page into a workroom is a manual paste. Direct import is on the roadmap.
- Forgetting to revoke after offboarding. If an admin leaves and they connected the integration, rotate / disconnect their OAuth grant.
What's next
- Custom agents — where you grant tools.
- Encryption — how OAuth tokens are stored.
- API overview — for things integrations can't do.