Scoped per agent
Read-only CRM, one Slack channel, or a single repo—configured on agent skills, not workspace-wide blast radius.
Connect your stack
Integrations for AI agents
Plug Digio into Slack, email, CRM, and your own systems—via agent skills, webhooks, OAuth sign-in, and Public API v1. One coordinator routes work; integrations keep context in your tools.
Agent skills
Webhooks & API
OAuth ready
Integration hub · week 4
Illustrative setup—scope every connector per agent and workspace.
In the product
One hub for skills, channels, and webhooks
Enable connectors per agent, route events through the coordinator, and keep approvals in Digio—your team still works in Slack, email, and CRM.
Slack
Coordinator
CRM
Support
Events · 12 routed today
Catalog
Same catalog as in your workspace settings
Connect messengers, calendars, and workspaces—the integrations tab in user settings lists every connector agents can use. Store credentials securely and scope access per agent via skills.
Connect messengers, calendars, and workspaces. Configure sign-in details per connector—agents use them when automating tasks you authorize.
- Slack
- Discord
- Telegram
- Microsoft Teams
- Google Chat
- Messenger
- Zoom
- Google Calendar
- Outlook Calendar
- Apple Calendar
- Calendly
- Notion
- Microsoft 365
- Asana
- Trello
- Jira
- monday.com
- ClickUp
- Airtable
- Linear
Open the integrations tab after you create a workspace—pair connectors with agent skills so each agent only sees what you allow.
Why integrate
Context stays in your tools
Agents act inside systems you already trust—scoped skills, coordinator routing, and a full audit trail in the workspace.
Coordinator routing
Inbound webhooks and chat mentions become tasks on To do—the coordinator picks the right agent and skill set.
Auditable actions
Tool calls and webhook payloads are visible in agent chats—pair with security for keys and rotation.
How it works
Connect → authorize → route
From first skill to production webhooks—same workspace your team already uses.
-
Pick a connector
Enable built-in skills or wire custom HTTP and MCP tools from the skills catalog.
-
Authorize & scope
OAuth, API keys, or channel picks—limit what each agent can read or write before the first run.
-
Route through coordinator
Events land as tasks on To do; the coordinator assigns agents with the right skills.
-
Automate at scale
Use Agent API and outbound webhooks when your product or ops stack needs headless runs.
Channels
Where agents meet your team
Enable skills per agent so handoffs stay scoped—read-only CRM, one Slack channel, or a single repo—while the coordinator tracks tasks in Digio.
Slack & chat
Post updates, read threads, and escalate to humans when confidence is low—paired with team chat inside the workspace.
Draft and triage messages, apply tone presets, and queue follow-ups as standing tasks in To do.
CRM & sales tools
Sync notes, update pipeline stages, and prep call briefs—see solutions for sales ops playbooks.
Webhooks
Fire events when tasks complete or agents need approval; receive inbound payloads to start agent runs.
Public API v1
Catalog, locales, usage estimates, and wallet-aware endpoints—documented on Agent API.
OAuth sign-in
Google, Apple, and Telegram on register—same identity layer your workspace uses for team invites.
Developers
Build on skills + API
Agent skills cover productized connectors; Agent API covers billing transparency and automation you own.
HTTP & MCP tools
Custom HTTP tools and MCP servers with typed, auditable actions—enable per agent from the skills UI.
Workspace API keys
Server-to-server calls scoped per workspace—rotate and audit via security.
OpenAPI & clients
Generate clients from the Public API v1 schema—same endpoints your dashboards and CI jobs call.
Use cases
Integrations teams ship first
High-signal automations with a human review step—before you widen scopes or add write access.
Slack
Ops channel digest
Nightly summary of open tasks and blockers posted to #ops—mentions route back into Digio for follow-up.
- Posts
- 7/wk
- Channels
- 2
CRM
Call brief before meetings
Read-only CRM pull + research agent memo—rep reviews in chat before updating the record.
- Briefs
- 15/wk
- Fields
- 8
Webhook
Ticket → agent run
Inbound webhook from helpdesk creates a standing task; coordinator assigns support agent with CRM skill.
- Events
- 40/day
- SLA
- <5m
API
Product-embedded agent
Your app triggers Agent API jobs; users see progress on the Digio board while you stream status to your UI.
- Jobs
- 200/day
- Agents
- 3
Integrations
Digio value for connected teams
Less copy-paste between tools; more routed work with clear ownership.
-
Skills — enable connectors per agent on agent skills.
-
To do — standing syncs and webhook follow-ups on To do.
-
API — headless runs via Agent API with job streaming.
-
Security — keys, scopes, and rotation on security.
FAQ
Integration questions
Scopes, webhooks, and what Digio connects to out of the box.
Do I need code to connect Slack or CRM?
Often no—enable the skill from agent skills, authorize, and assign to an agent. Custom systems use HTTP tools or MCP.
Can agents write to my CRM?
Only if you grant write scopes. Many teams start read-only and add approval gates before updates.
How do webhooks work with To do?
Inbound payloads create or update tasks on To do; outbound webhooks fire when tasks complete or need approval.
Is Public API v1 the same as Agent API?
Public API v1 covers catalog and workspace metadata; Agent API runs agents and streams job progress.
Where are API keys stored?
Workspace keys are scoped and rotatable—see security for isolation and team roles.
What should I connect first?
One read-only channel (Slack digest or CRM brief) with a clear human review step—then add webhooks or write access.
Connected
Go deeper on the stack
Skills, automation API, and security docs for production integrations.
Explore
Related pages
Skills, security, solutions, and plans for connected workflows.
Connect your first integration
Create a workspace, enable skills on an agent, and route a real task through the coordinator.