Category 08 of 12
Reach
How agents reach people and systems: messaging channels, the bilateral MCP plane, integrations, agent-to-agent skills, and outbound safety.
Pages in this category
The Connection primitive: peer identity resolved across channels, durable inbound queues, and rich two-way attachments.
Discord, Slack, Telegram, WhatsApp, and Voice — direction, threading, attachments, and the quirks of each.
A workflow reaches the world with a zero-token channel node — not an agent prompt — that resolves a connection, delivers, and returns a receipt SWIFT can verify.
Recognizing the same human across Slack and WhatsApp, and the grant model that governs what a connection is allowed to do.
How an inbound channel message survives a restart and reliably becomes an agent turn — the queue behind 'messages never get lost.'
Gmail, SMTP, Outlook, and AgentMail — the zero-config agent-native provider where 'email me' just works.
Agentis both consumes external MCP servers and publishes its own workflows as JSON-RPC 2.0 Streamable-HTTP tools — one registry, many projections.
Discovery, dynamic client registration, and PKCE — how Agentis authenticates against an external MCP server on an agent's behalf.
Hand-written connectors, templated HTTP connectors, a generic HTTP fallback, and custom JSON-Schema manifests.
Published workflows exposed as A2A skills through the same execution path as MCP.
Signed trigger ingress, native SaaS connector webhooks, channel webhooks, and the gateways that supervise persistent transports.
The outbound policy gate: quiet hours, claim guards, per-App rate limits, and SSRF protection on every outbound call.