BCP Mail icon

BCP Mail

Interact with BCP Mail API

Actions4

Overview

This node integrates with the BCP Mail API to manage email marketing automations, autoresponders, contacts, and sending emails. Specifically, for the Automation - Create Subscriber operation, it allows users to add new subscribers to a selected automation workflow by providing subscriber details as merge fields.

Common scenarios include:

  • Adding new subscribers to an email automation campaign.
  • Importing subscriber data dynamically from other workflows or sources.
  • Personalizing subscriber information using merge fields for targeted campaigns.

Practical example:

  • When a new user signs up on your website, this node can automatically add them as a subscriber to a specific email automation, passing their name and email as merge fields.

Properties

Name Meaning
Automation Name or ID Select the target automation by name or UUID to which the subscriber will be added.
Merge Fields Key-value pairs representing subscriber data fields (e.g., email, first name). Multiple fields can be specified. Each field is chosen from a list or specified by ID, with corresponding values provided.

Output

The node outputs JSON data containing the response from the BCP Mail API after attempting to create the subscriber. The structure typically includes success status and any relevant data returned by the API.

If an error occurs and "Continue On Fail" is enabled, the output JSON will contain an error field with the error message.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the BCP Mail API.
  • The node makes HTTP requests to the BCP Mail API endpoints.
  • Proper configuration of the API base URL and API key in the credentials is necessary.

Troubleshooting

  • Missing Email Field: If the "emails" field is not provided in the merge fields or is empty, the node throws an error stating that the email is required. Ensure the email address is included in the merge fields.
  • API Authentication Errors: Invalid or missing API keys will cause authentication failures. Verify that the API key credential is correctly set up.
  • Invalid Automation UUID: Selecting an invalid or non-existent automation UUID may result in API errors. Confirm the automation 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 even if some items fail.

Links and References

Discussion