Actions4
- Automation Actions
- Autoresponder Actions
- Contact Actions
- Send Mail Actions
Overview
This node integrates with the BCP Mail API to manage email marketing tasks. Specifically, for the Autoresponder - Create Subscriber operation, it allows users to add new subscribers to an autoresponder list by specifying the autoresponder and subscriber details. This is useful in scenarios where you want to automate adding contacts to a drip email campaign or follow-up sequence based on triggers in your workflow.
Practical examples include:
- Automatically subscribing new customers to a welcome email series.
- Adding webinar registrants to a post-event autoresponder.
- Syncing contacts from other systems into an autoresponder list for targeted messaging.
Properties
| Name | Meaning |
|---|---|
| Autoresponder Name or ID | Select the target autoresponder list by name or ID to which the subscriber will be added. |
| Merge Fields | Key-value pairs representing subscriber data fields (e.g., email, first name). These fields are merged into the subscriber profile. |
The Merge Fields property supports multiple entries, each consisting of:
- Field Name or ID: The specific merge field key or label to set for the subscriber.
- Value: The value to assign to that merge field.
Output
The node outputs JSON data representing the response from the BCP Mail API after attempting to create the subscriber. This typically includes success status and any relevant metadata returned by the API.
If the operation fails and "Continue On Fail" is enabled, the output will contain an error object with the error message.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the BCP Mail API via an API key credential.
- The node uses HTTP requests to interact with the BCP Mail API endpoints.
- Proper configuration of the API base URL and authentication token is necessary in the node credentials.
Troubleshooting
- Missing Email Field: If the subscriber's email is not provided in the merge fields, the node throws an error indicating that the email is required. Ensure the "emails" merge field is included and correctly populated.
- API Authentication Errors: Invalid or missing API keys will cause authentication failures. Verify that the API key credential is correctly configured.
- Invalid Autoresponder ID: Selecting an invalid or non-existent autoresponder UUID will result in API errors. Confirm the autoresponder exists and is accessible.
- Network Issues: Connectivity problems can cause request failures. Check network access and API endpoint availability.
- To handle errors gracefully, enable "Continue On Fail" to allow the workflow to proceed while capturing error details in the output.