Actions4
- Automation Actions
- Autoresponder Actions
- Contact Actions
- Send Mail Actions
Overview
This node integrates with the BCP Mail API to manage email marketing-related resources. Specifically, for the Contact - Create Contact operation, it allows users to create new contacts in their BCP Mail account by providing contact details as merge fields.
Typical use cases include:
- Adding new subscribers or contacts collected from forms or other sources into a mailing list.
- Automating contact creation as part of a larger workflow that manages email campaigns.
- Synchronizing external CRM or database contacts with BCP Mail.
For example, you might use this node to automatically add a new user who signed up on your website into your BCP Mail contact list, including custom fields like name, email, and preferences.
Properties
| Name | Meaning |
|---|---|
| Merge Fields | A collection of key-value pairs representing contact data fields. Each field has: |
| - Field Name or ID: Selectable from available merge fields fetched dynamically from BCP Mail. | |
| - Value: The value to assign to the selected field for the new contact. |
The "Merge Fields" property is required to provide at least an email address under the emails field; otherwise, the node will throw an error.
Output
The node outputs JSON data representing the response from the BCP Mail API after attempting to create the contact. 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 node.
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 is necessary in the credentials setup.
Troubleshooting
Missing Email Field: The node requires the
emailsfield in the merge fields to be set and non-empty. If omitted, it throws an error:"Email is required in the "Merge Fields" section."
To fix, ensure you provide a valid email address in the merge fields.API Authentication Errors: If the API key is invalid or missing, requests will fail. Verify that the API key credential is correctly configured.
HTTP Request Failures: Network issues or incorrect API endpoint URLs can cause failures. Check connectivity and credential settings.
Invalid Merge Fields: Providing unknown or unsupported field names may result in API errors. Use the dynamic options loader to select valid fields.
Links and References
- BCP Mail API Documentation (example placeholder, replace with actual)
- n8n Expressions Documentation — for using expressions in field values
- n8n Node Development Guide