Reference · Nodes
Communication integrations and nodes
Communication nodes send and read messages across email, chat, SMS, push notifications and support desks. Slack posts and searches channel messages, Google Gmail sends, replies to and searches mail with attachments, Twilio sends SMS and WhatsApp messages and places calls, and Zendesk creates and updates support tickets. Most of these services also have a trigger, so an incoming email, chat message, text or ticket change can start a workflow.
74 nodes — 62 actions and 12 triggers. Every page documents the shipped node: real parameters, real outputs, real error behaviour.
Email, chat, SMS and support desks
The category spans every channel a business sends messages through.
Email. Google Gmail and Microsoft Outlook work with a mailbox: send, reply, drafts, labels or folders, and attachments. Send Email sends through any SMTP server and Email Read (IMAP) reads from any IMAP server. SendGrid, Mailgun, Mandrill and AWS SES handle transactional sending.
Chat. Slack, Discord, Telegram, Mattermost, Google Chat and Cisco Webex post and read messages in channels, rooms and spaces.
SMS, voice and alerts. Twilio, Vonage, MessageBird and Plivo send texts and place calls. PagerDuty opens and updates incidents, and Pushover and SIGNL4 send alerts to phones.
Support desks and queues. Zendesk, Freshdesk and Zammad manage tickets. AWS SQS, MQTT and AMQP Sender publish to message queues and brokers.
Triggers
Polling triggers check a mailbox on an interval: Gmail Trigger, Microsoft Outlook Trigger and Email Trigger (IMAP). Webhook triggers run as events arrive: Slack Trigger, Microsoft Teams Trigger, Telegram Trigger, WhatsApp Trigger, Cisco Webex Trigger, Twilio Trigger, Zendesk Trigger, Help Scout Trigger and Postmark Trigger.
Example workflows
- Texts become tickets. Twilio Trigger starts the run when a customer sends a text to a Twilio number, Zendesk creates a support ticket from it, and Twilio sends an auto-reply.
- Alert and page. Webhook receives an alert from a monitoring service, PagerDuty creates an incident, and Slack sends a message to a channel.
- Sort the support inbox. Gmail Trigger watches a label for incoming support requests, OpenAI Structured Output classifies each one into predefined categories, and Google Gmail adds labels to organize them.
Actions
Triggers
Nodes that START a workflow when something happens.
Frequently asked questions
Which communication events can start a workflow?
Gmail Trigger, Microsoft Outlook Trigger and Email Trigger (IMAP) poll a mailbox for new mail. Slack Trigger, Microsoft Teams Trigger, Telegram Trigger, WhatsApp Trigger, Cisco Webex Trigger and Twilio Trigger receive webhooks for messages and other events. Zendesk Trigger, Help Scout Trigger and Postmark Trigger cover support tickets, support conversations and email delivery events.
Does a trigger need its own credential?
Usually it shares the action node's credential type. Slack and Slack Trigger both use the Slack API credential, Twilio and Twilio Trigger both use Twilio API, and Gmail Trigger uses the same Gmail OAuth2 credential as Google Gmail. WhatsApp is an exception: WhatsApp Trigger has its own credential type, separate from the one WhatsApp Business Cloud uses to send.
How do communication nodes combine with AI nodes?
A common pattern reads a message, has an AI node decide something about it, then replies or routes it. Gmail Trigger starts the run, Claude Structured Output extracts the request into fields, and Switch sends each request to the right channel. Most of the email nodes accept binary attachments from earlier steps, so a generated report or PDF can go out with the message.
Last reviewed . Spotted something wrong? Tell us.