Overview
This node integrates with the One Mail API to import subscribers into a specified automation workflow. It is designed to add or update subscriber information within an automation campaign by providing the subscriber's email and optional custom contact fields.
Common scenarios where this node is beneficial include:
- Adding new subscribers to an email marketing automation.
- Updating subscriber details dynamically based on external data sources.
- Managing subscriber lists programmatically as part of larger workflows.
For example, you could use this node to import a list of new customers into a welcome email automation or update existing subscriber attributes before triggering personalized campaigns.
Properties
| Name | Meaning |
|---|---|
| Automation Name or ID | Select the target automation by name or specify its unique ID. |
| The subscriber's email address to be imported into the automation. | |
| Contact Fields | Optional custom fields for the subscriber. You can specify multiple key-value pairs where keys are contact field names or IDs, and values are strings, numbers, ISO dates, or JSON objects/arrays. |
The "Contact Fields" property supports multiple entries, each consisting of:
- Contact Field Name or ID: Choose from available contact fields or specify an ID.
- Value: The value corresponding to the contact field.
Output
The node outputs the response from the One Mail API after attempting to import the subscriber. The output is structured as JSON containing the result of the import operation, which typically includes success status and any relevant messages or data returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating requests to the One Mail API.
- The node makes HTTP requests to
https://api.onestop.bizdev.vnendpoints. - The following API endpoints are used:
- To load automations:
/api/bizfly/mail/automations - To load contact fields:
/api/bizfly/mail/fields - To import subscriber:
/api/bizfly/mail/automations/import-subscribe-manual
- To load automations:
Ensure that the API key credential is configured correctly in n8n to allow authorized access.
Troubleshooting
- Invalid or missing API key: If authentication fails, verify that the API key credential is set up properly and has sufficient permissions.
- Automation not found: Selecting or specifying an invalid automation ID will cause errors. Use the dropdown to select valid automations or ensure the ID is correct.
- Invalid contact field keys or values: Custom fields must match existing contact field keys and have appropriate value types (string, number, date, or JSON). Mismatches may cause the API to reject the request.
- Network or API errors: Check network connectivity and API availability if requests fail unexpectedly.
- Empty required fields: Ensure that required properties like "Automation Name or ID" and "Email" are provided; otherwise, the node will not execute successfully.
Links and References
- One Mail API Documentation (Assumed URL based on domain, replace with actual if known)
- n8n Expressions Documentation
- n8n Fixed Collection UI Documentation