Overview
This node, named "Autocust - Message Activity," is designed to retrieve the activity status of messages sent through different communication channels. Specifically, it checks whether a message has been opened or clicked by a contact. It supports multiple channels such as SMS, WhatsApp, and Email, and distinguishes between regular campaign messages and automated template messages.
Common scenarios where this node is beneficial include:
- Tracking user engagement with marketing campaigns across various channels.
- Monitoring the effectiveness of automated messaging workflows.
- Triggering follow-up actions based on whether a recipient opened or clicked a message.
For example, a marketer could use this node to check if a contact opened an email campaign and then decide to send a reminder or promotional offer accordingly.
Properties
| Name | Meaning |
|---|---|
| Channel | Select the channel through which the message was sent. Options: SMS, WhatsApp, Email |
| Type | Specify whether to observe regular campaign messages or automated template messages. Options: Regular (campaign), Automated (automation) |
| Name or ID | The name or ID of the message template to retrieve. This can be selected from a list or specified via expression. |
| Contact ID | The numeric ID of the contact whose message event status you want to check |
| Event Type | The type of event to check for the contact. Options: Message Opened, Message Clicked |
Output
The node outputs JSON data representing the activity status of the specified message for the given contact. This typically includes information about whether the message was opened or clicked, along with relevant metadata.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authentication with the external Autocust service.
- Depends on the Autocust API to fetch templates and message activity events.
- The node uses a method to dynamically load available message templates based on the selected channel and type.
Troubleshooting
- Missing or invalid API credentials: Ensure that the required API key credential is correctly configured in n8n.
- Invalid Contact ID or Template ID: Verify that the contact ID and template ID exist and are correct; otherwise, the node may return no data or errors.
- Network or API errors: Check connectivity and API availability if the node fails to retrieve data.
- Empty or unexpected output: Confirm that the selected event type matches actual recorded events for the contact.
Links and References
- n8n Expressions Documentation — for using expressions in property fields.
- Autocust API documentation (not provided here) would be useful for understanding the exact structure of returned activity data.