Autocust - Workflow Activation Trigger
Overview
This node acts as a trigger for workflows based on specific contact-related events occurring in the Autocust system. It continuously polls for changes or actions such as new contacts being created, contacts being updated, contacts being blocklisted, or campaigns being sent. When one of these events is detected, it triggers the workflow to execute.
Common scenarios where this node is beneficial include:
- Automatically processing or enriching new contacts as soon as they are added.
- Reacting to updates in contact information to keep other systems synchronized.
- Handling contacts that have been blocklisted to prevent further communication.
- Initiating follow-up actions or analytics when a campaign has been sent.
For example, a marketing automation workflow could be triggered whenever a new contact is added to start a welcome email sequence, or a CRM update workflow could run when a contact's details change.
Properties
| Name | Meaning |
|---|---|
| Event | The specific event that 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 data in JSON format representing the events detected since the last poll. Each output contains an array of event objects corresponding to the selected event type:
- For New Contact and Update Contact, the output includes contact details reflecting the newly created or updated contacts.
- For Contact Blocklisted, the output includes information about contacts that have been blocklisted.
- For Campaign Sent, the output includes details about campaigns that have been sent.
The output is emitted only when new events are found during polling.
This node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Autocust service.
- Uses internal polling functions imported from separate modules for each event type.
- The node runs a polling interval every 10 seconds to check for new events.
Troubleshooting
- Unknown trigger type error: If the selected event is not recognized internally, 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: If no events appear to trigger the workflow, verify that the Autocust API credentials are valid and that there are recent events matching the selected trigger.
- Polling interval issues: The node uses a fixed 10-second polling interval; if the environment restricts frequent polling, consider adjusting or checking resource limits.
Links and References
- Autocust API Documentation (replace with actual URL)
- n8n documentation on Creating Triggers