Actions6
- Email Actions
- WhatsApp Actions
- SMS Actions
Overview
This node integrates with the TouchBasePro API to manage email subscribers within mailing lists. Specifically, the "Add/Update Subscriber" operation allows users to either add a new subscriber to an email list or update an existing subscriber's details. This is useful for maintaining up-to-date contact information and managing subscription statuses in marketing or transactional email campaigns.
Practical examples include:
- Adding a new user who signed up on your website to a mailing list.
- Updating an existing subscriber’s email address or name after they request changes.
- Changing a subscriber’s status (e.g., unsubscribed or active) based on their preferences.
- Managing custom fields for subscribers such as preferences or demographic data.
Properties
| Name | Meaning |
|---|---|
| List Name or ID | Select the target mailing list by name or ID where the subscriber will be added or updated. |
| Action | Choose whether to "Add" a new subscriber or "Update" an existing one. |
| Email (Add) | The email address of the new subscriber to add (required when adding). |
| Current Email Name or ID (Update) | Select the current subscriber by email or ID to update (required when updating). |
| New Email (Update) | The new email address to update to (optional, used when updating). |
| Name | The subscriber's full name (required). |
| Re-subscribe | Boolean flag indicating if the subscriber should be re-subscribed if previously unsubscribed (default: true). |
| Consent To Track | Boolean flag indicating if tracking consent is given by the subscriber (default: true). |
| Status | The subscriber's status in the list. Options are: Active, Bounced, Deleted, Unconfirmed, Unsubscribed. Default is Active. |
| Custom Fields | A collection of custom fields to set for the subscriber. Each field requires selecting a field name or ID and providing a value matching the field's type. Useful for storing additional subscriber data beyond email and name. |
Output
The node outputs JSON objects representing the response from the TouchBasePro API for each processed item. This typically includes confirmation of the subscriber addition or update, along with any metadata returned by the API such as subscriber IDs or status.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the TouchBasePro API.
- The node depends on the TouchBasePro service being accessible and properly configured.
- The node uses dynamic loading methods to fetch options for lists, subscribers, and custom fields from the API to assist user input.
Troubleshooting
Common issues:
- Providing an invalid or non-existent list ID/name will cause errors.
- Attempting to update a subscriber that does not exist in the specified list will fail.
- Incorrectly formatted custom field values may be rejected by the API.
- Missing required fields like email or name will result in validation errors.
Error messages:
"Operation 'addOrUpdateSubscriber' not implemented for resource 'email'"indicates a misconfiguration or unsupported operation call.- API authentication errors suggest invalid or missing API credentials.
- Validation errors from the API usually specify which field is incorrect or missing; ensure all required inputs are provided and correctly formatted.
Resolution tips:
- Verify list and subscriber selections using the dropdowns or expressions.
- Double-check email formats and required fields.
- Ensure API credentials are valid and have necessary permissions.
- Use the node’s option loaders to select valid custom fields and lists.
Links and References
- n8n Expressions Documentation
- TouchBasePro API documentation (refer to your TouchBasePro account or developer portal for detailed API specs)
- n8n official docs on creating and managing credentials