Connect a messaging channel
Channels let users talk to agents through the messaging platforms they already use. Alquimia Platform normalizes inbound messages from each channel into the same execution pipeline, so the agent itself does not need to know whether a message came from WhatsApp or Email.
Choose the right channel
Section titled “Choose the right channel”| Channel | Best for |
|---|---|
| Mobile customers, field service, rich media | |
| Slack | Internal helpdesks, team collaboration, slash commands |
| Formal requests, long-form content, ticket-style workflows | |
| Kapso WhatsApp | WhatsApp access without direct Meta integration |
You can attach multiple channels to the same agent. For example, a support agent might accept WhatsApp from customers and Slack from employees.
What you will configure
Section titled “What you will configure”Each channel requires three things:
- Provider credentials — tokens, webhooks, or API keys stored as secrets, not in the agent spec.
- Channel configuration — the adapter that maps provider payloads to Alquimia Platform’s normalized request shape.
- Response template — how the agent’s answer is formatted before delivery.
Set up the channel
Section titled “Set up the channel”-
Register the provider secrets in the agentspace registry.
-
Create the channel configuration in the agent spec or registry, selecting the adapter for your provider.
-
Configure the provider webhook to point at the runtime’s channel endpoint. The runtime verifies each inbound request using the provider’s signature or token mechanism.
-
Send a test message and confirm that the agent receives it, produces a response, and the response is delivered back to the sender.
-
Check the worklog to verify normalization, identity mapping, and delivery.
Identity and session mapping
Section titled “Identity and session mapping”Channels map provider-specific sender identifiers to stable Alquimia Platform user_id and session_id values. This preserves conversation history when the same person messages again from the same channel. Make sure the mapping is consistent, especially if you have multiple agents sharing a channel.
Response templates
Section titled “Response templates”Templates let you format answers per channel. An email response might include HTML and a signature, while a WhatsApp response should be concise plain text. Templates can reference metadata such as sender name or original message ID, but keep them simple to avoid rendering issues.
Approval handoffs
Section titled “Approval handoffs”When a tool requires human approval, the approval request can be routed back through the same channel the user is already on. This keeps the workflow natural and reduces the risk of spoofed approvals.