Messaging integrations

Slack

Use Slack to trigger workflows from Slack Events API messages and to send, reply to or read messages from workflows. A usable Slack integration must include the app credentials and workspace/channel access required by the connector. Slack Message Trigger appears for inbound Slack events. Slack Action appears for send, reply and read-message operations.

Twilio SMS

Twilio SMS is only for phone-message workflows through Twilio. Required data: account SID and auth token. Add a from number or messaging service SID depending on how the Twilio account sends messages. Twilio SMS Trigger is visible for inbound SMS workflows. Twilio SMS Action supports send SMS, reply and read-message operations.

Signal

Signal is separate from Twilio. Use it through a self-hosted bridge such as signal-cli-rest-api. Required data: bridge base URL, Signal account and webhook secret. API token and default recipient are optional depending on the bridge deployment. Signal Message Trigger appears for inbound Signal events. Signal Action supports send message, reply and read-message operations.

Microsoft Teams

Use Teams to trigger workflows from Teams activity and send or read Teams messages through Microsoft Graph. A Teams integration should identify the tenant/app credentials and target chat or channel context needed by the connector. Teams Message Trigger appears for Teams events. Teams Action supports channel or chat message operations.

WhatsApp Business Platform

Use WhatsApp Business Platform for official Cloud API messaging, not for personal WhatsApp accounts. Required data: WhatsApp Business Account ID, phone number ID, access token, app secret and webhook verify token. Optional defaults include display phone number, default recipient, default language code and default template name. Credentials come from Meta for Developers and WhatsApp Manager. Start with the WhatsApp Cloud API overview and the WhatsApp Platform docs.

WhatsApp Business Message Trigger appears for inbound WhatsApp webhook events. WhatsApp Business Action supports send message, reply, send template and mark as read. Use approved templates outside the customer-service window; free-form messages are mainly for active conversations where the platform allows them.