Overview
This node acts as a trigger for workflows based on specific contact-related events occurring in the Autocust system. It listens for changes such as new contacts being created, contacts being updated, contacts being blocklisted, or campaigns being sent. When one of these events happens, the node activates the workflow, allowing subsequent nodes to process the event data.
Common scenarios where this node is useful include:
- Automatically sending follow-up emails when a new contact is added.
- Updating CRM records when contact information changes.
- Notifying teams when a contact is blocklisted due to compliance reasons.
- Triggering analytics or reporting workflows after a campaign is sent.
Properties
| Name | Meaning |
|---|---|
| Event | Selects which event will trigger the workflow. Options: |
| - Campaign Sent: Trigger when a campaign is sent | |
| - Contact Blocklisted: Trigger when a contact is blocklisted | |
| - New Contact: Trigger on creation of a new contact | |
| - Update Contact: Trigger on updating of a contact |
Output
The node outputs JSON data representing the events detected since the last check. The structure depends on the event type but generally includes arrays of event objects corresponding to the selected event:
- For New Contact and Update Contact, the output contains arrays of contact objects with their details.
- For Contact Blocklisted, it outputs arrays of contacts who have been blocklisted.
- For Campaign Sent, it outputs arrays of campaign event objects indicating campaigns that were sent.
The node does not output binary data.
Dependencies
- Requires an API key credential to authenticate with the Autocust service.
- Uses polling internally every 10 seconds to check for new events.
- Depends on external modules implementing the polling logic for each event type (e.g.,
pollNewContacts,pollUpdatedContacts, etc.).
Troubleshooting
- Unknown trigger type error: If the selected event is not recognized, the node throws an error indicating an unknown trigger type. Ensure the "Event" property is set to one of the supported options.
- No events triggering: Since the node polls every 10 seconds, there might be a delay between the actual event occurrence and workflow activation.
- Authentication issues: Make sure the API key credential is correctly configured and has sufficient permissions to access Autocust events.
- Network or API errors: Temporary connectivity issues may cause polling failures; verify network stability and Autocust API availability.
Links and References
- Autocust API Documentation (replace with actual URL)
- n8n documentation on Creating Triggers