Overview
This node, named "Autocust - Message Activity," is designed to retrieve the activity status of a message sent through various 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 by checking if recipients have opened or clicked on messages.
- Monitoring automated notification templates to verify delivery and interaction.
- Integrating message activity data into workflows for follow-up actions based on user behavior.
For example, a marketer could use this node to check if a contact opened an email campaign and then trigger a personalized follow-up message if they did not engage.
Properties
| Name | Meaning |
|---|---|
| Channel | Select the channel through which the message was sent. Options: SMS, WhatsApp, Email |
| Type | Specify whether the message is part of a regular campaign or an automated template. Options: Regular, Automated |
| 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, depending on the selected event type.
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 message templates and activity events.
- The node uses internal methods to load available templates dynamically based on the selected channel and message type.
Troubleshooting
Common issues:
- Invalid or missing contact ID may result in no data returned or errors.
- Selecting a template ID that does not exist or is not accessible can cause failures.
- Incorrect API credentials will prevent successful connection to the Autocust service.
Error messages:
- Authentication errors indicate problems with the provided API key; ensure the key is valid and has necessary permissions.
- "Template not found" errors suggest the selected template ID is invalid or unavailable; verify the template exists for the chosen channel and type.
- Network or timeout errors may occur if the Autocust API is unreachable; check network connectivity and API status.
Links and References
- n8n Expressions Documentation — for using expressions in property fields like Template ID.