Overview
This node integrates with the One Mail API to import subscribers into a specified automation. It is designed to push subscriber data, including email and custom contact fields, into an existing automation workflow managed by One Mail.
Common scenarios where this node is beneficial include:
- Adding new subscribers collected from forms or other sources directly into marketing automations.
- Synchronizing user data from external systems into One Mail for targeted email campaigns.
- Enriching subscriber profiles with custom fields during import to personalize communications.
For example, you might use this node to import a list of users who signed up on your website into a welcome email automation, specifying their email addresses and additional profile information such as name, signup date, or preferences.
Properties
| Name | Meaning |
|---|---|
| Automation Name or ID | Select the target automation by name or specify its unique ID. This determines which automation the subscriber will be imported into. |
| The email address of the subscriber to import. | |
| Contact Fields | A collection of custom contact fields to associate with the subscriber. Each entry requires selecting a contact field (by name or ID) and providing its value. Values can be strings, numbers, ISO dates, or JSON objects. |
The "Contact Fields" property supports multiple entries, allowing you to enrich the subscriber's profile with various custom attributes.
Output
The node outputs the response from the One Mail API after attempting to import the subscriber. The output is structured as JSON containing details about the import operation, such as success status or error messages.
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 to fetch automations, contact fields, and to perform the import operation. - Proper configuration of the API key credential in n8n is necessary for successful execution.
Troubleshooting
- Invalid or missing API key: If authentication fails, ensure that the API key credential is correctly configured and has sufficient permissions.
- Automation not found: Selecting an invalid or deleted automation UUID will cause errors. Verify the automation exists by using the dropdown or checking via the One Mail dashboard.
- Invalid contact field values: Providing values that do not match the expected type (e.g., string instead of JSON) may result in rejection by the API. Ensure values conform to the expected formats.
- Network issues: Connectivity problems to the One Mail API endpoint will cause request failures. Check network access and proxy settings if applicable.
Common error messages typically originate from the One Mail API and should be interpreted according to their content, such as authorization errors, validation failures, or rate limits.
Links and References
- One Mail API Documentation (assumed based on base URL)
- n8n Expressions Documentation – for using expressions in property values
- One Mail Automation Management (general reference for managing automations)
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.