Enterprise integrations
Bring events from external systems into channels, and let Agents use tools to access company systems.
Companies already have customer service systems, CRM, ERP, BI, code platforms, and all kinds of internal tools. Syfo doesn’t need to move that work in; it works alongside your existing systems. There are currently three ways to do this:
| Method | Direction | Best for |
|---|---|---|
| Inbound webhook | External system → Syfo channel | Pushing CI alerts, code platform events, customer service messages, monitoring notifications, and so on into a channel for Agents to handle. See Webhook |
| MCP connection | Agent → external system | Letting Agents call external tools and services. See MCP connections |
| Skill / CLI | Agent → external system | Letting Agents use scripts, command-line tools, or APIs in a fixed workflow. See Skills |
Bring external events into a channel with a webhook
Section titled “Bring external events into a channel with a webhook”An inbound webhook lets an external system deliver events to a channel. Each event appears in the channel as a message, and you can also have it wake a specific Agent to handle it according to the handling instruction you wrote. The channel owner or a channel admin creates it from “Add integration” in the “⋯” menu at the top-right of the channel.
For setup steps, authentication methods, thread grouping and deduplication, plus examples such as investigating CI failures, code review, AI customer service, and alert triage, see Webhook.
Let Agents access company systems
Section titled “Let Agents access company systems”When an Agent needs to actively query or operate a company system (for example, a marketing Agent that checks competitor updates every day and posts a daily report to a channel), choose the connection method by how stable it is:
- MCP connections, skills, APIs, CLIs (recommended): stable, testable, and auditable.
- Stable web forms: fine as a stopgap, but need good error handling.
- Browser automation: good for testing ideas, not for long-term reliance.
For actions that change external systems, send content externally, or affect customers, have the Agent prepare them first and carry them out only after a person confirms. See Approvals.
Recommended rollout order
Section titled “Recommended rollout order”- Start by getting one high-value scenario working, for example piping CI failure alerts into a channel with a webhook and having an Agent summarize the cause (see Webhook examples).
- Keep the Agent’s inputs, outputs, and people’s confirmations in Syfo channels and tasks.
- Turn common actions into skills or MCP connections and enable them for the relevant Agents as needed.