Deliver where the work happens.
Slack, email, Teams, your CMS, your webhook.
An agent that runs but doesn't deliver is a tree falling in an empty forest. Connection nodes ship output to where humans live: Slack channels with proper formatting, email with HTML templates, Teams cards, HMAC-signed webhooks into your existing systems. Conditional routing, per-channel templates, OAuth-secured tokens.
The last mile of an agent, done right.
One payload, rendered for every channel.
Connections combine with
Frequently asked
Slack (OAuth), email (SMTP or SendGrid), Microsoft Teams (webhook), generic HTTPS webhooks (HMAC-signed), CSV and JSON file exports, and direct push to your CMS via published connectors or a custom webhook.
Slack and Teams use OAuth installations into your workspace. Email is per-agent SMTP credentials or a managed SendGrid pool. Webhooks use HMAC-SHA256 with a per-connection secret. Tokens stored encrypted at rest, never exposed in workflow definitions.
Yes. Each connection node has its own template - a Slack message uses blocks, an email uses HTML or Markdown, a webhook gets the JSON schema you define. The same upstream data feeds them all through per-channel templates.
Yes. Place a Condition node before delivery to branch: high-severity alerts to Slack with @here, low-severity to a weekly digest email, regulatory issues to a webhook into your ticketing system. One workflow, multiple delivery paths.
Connect to your team's workflow
Book a strategy session and we'll wire an agent into Slack, email, Teams, or your existing webhook.