Actions57
- Agents Actions
- Public Answer Actions
- Answer Management Actions
- Communications Actions
- Customers Actions
- Conversations Actions
- Get Conversations
- Get Conversation
- Patch Conversation
- Create Item
- Get Item
- Delete Item
- Get Media
- Get Voice Transcript
- Create Customer Item
- Delete Customer Item
- Get Conversation Items
- Add Topic To Conversation
- Delete Topic From Conversation
- Add Note To Conversation
- Get Note From Conversation
- Reply To Message
- Redact Content
- Export Actions
- Freeform Topics Actions
- Message Automation Actions
- Proactive Conversations Actions
- Tasks Actions
- User Identity Actions
- Topics Actions
- Webhooks Actions
- Payloads Actions
Overview
This node allows sending outbound messages as part of a message automation workflow. It is designed to send different types of messages—such as plain text, menu options, or HTML content—to users within an automation session. This functionality is useful in scenarios like customer support chatbots, automated notifications, or interactive messaging systems where you want to programmatically send messages based on user interactions or system events.
For example, you could use this node to:
- Send a greeting text message when a new chat session starts.
- Present a menu of options for the user to choose from.
- Deliver rich HTML content such as formatted messages or embedded links.
Properties
| Name | Meaning |
|---|---|
| Session Id | The unique identifier of the automation session where the message will be sent. |
| Type | The type of the outbound message. Options: TEXT (plain text), MENU (interactive menu), HTML (rich HTML content). |
| Content | The actual message content to send. For TEXT, it is a simple string; for other types, it can be structured JSON representing menus or HTML content. |
Output
The node outputs data in JSON format representing the response from the message sending operation. This typically includes confirmation details about the sent message, such as message ID, status, or any metadata returned by the API.
If the node supports binary data output (not indicated here), it would represent attachments or media sent along with the message, but this implementation focuses on JSON message content only.
Dependencies
- Requires an API key credential to authenticate with the external messaging service.
- The base URL for the API is set to a placeholder (
https://petstore3.swagger.io/api/v3) in the bundled code, which should be replaced with the actual service endpoint. - The node uses HTTP headers to specify JSON content type and accept JSON responses.
Troubleshooting
- Missing or invalid Session Id: Ensure that the session ID provided corresponds to an active automation session; otherwise, the message will not be delivered.
- Invalid message type or content: The
Typeproperty must be one of the allowed options (TEXT,MENU,HTML). TheContentmust be valid JSON matching the expected structure for the chosen type. - Authentication errors: Verify that the API key or authentication token is correctly configured and has sufficient permissions.
- API endpoint issues: Confirm that the base URL is correctly set to the live API endpoint rather than a placeholder.
- Parsing errors: Since the content is parsed from JSON, malformed JSON strings will cause errors. Validate JSON formatting before execution.
Links and References
- Gladly API Documentation (replace with actual API docs)
- n8n Documentation - Creating Custom Nodes
- JSON validation tools such as JSONLint for verifying message content formatting