TouchBasePro icon

TouchBasePro

Interact with TouchBasePro API for Email and WhatsApp operations

Actions6

Overview

This node integrates with the TouchBasePro API to send transactional smart emails using predefined email templates. It is designed for scenarios where you want to automate sending personalized, template-based emails triggered by workflows in n8n. Typical use cases include sending order confirmations, password resets, notifications, or any other transactional communication that benefits from dynamic content and tracking.

For example, you can use this node to send a welcome email to new users after they sign up, automatically populating the email with their name and other custom fields using merge tags.

Properties

Name Meaning
Smart Email Template Name or ID Select a transactional smart email template from your TouchBasePro account by name or ID. This defines the email layout and content structure used for sending.
To List of primary recipients. Each recipient can have a name and an email address. Multiple recipients can be added.
CC List of carbon copy recipients. Similar structure as "To".
BCC List of blind carbon copy recipients. Similar structure as "To".
Attachments Files to attach to the email. For each attachment, specify the name, type (e.g., MIME type), and the binary property name from the input data containing the file content.
Merge Fields Dynamic fields to replace placeholders in the email template. For each field, specify the field name or ID and the value to insert. These allow personalization of the email content.
Allow Tracking Boolean flag to enable or disable tracking of email opens and clicks. Defaults to true (tracking enabled).
Ignore Suppression List Boolean flag to decide whether to ignore the suppression list when sending the email. Defaults to true (suppression list ignored).
Add Recipient To List Boolean flag indicating whether to add the email recipient to a mailing list after sending. Defaults to true.

Output

The node outputs JSON data representing the response from the TouchBasePro API after attempting to send the transactional smart email. This typically includes details such as message IDs, status, and any metadata returned by the API confirming the email was sent or describing errors.

If attachments are included, the node expects binary data input fields but does not output binary data itself.

Dependencies

  • Requires an API key credential for authenticating with the TouchBasePro API.
  • The node depends on the availability of predefined smart email templates configured in the TouchBasePro platform.
  • Proper configuration of merge fields in the selected template is necessary to ensure dynamic content is correctly replaced.
  • n8n environment must have access to the internet to communicate with the TouchBasePro API endpoints.

Troubleshooting

  • Common Issues:

    • Sending fails if the specified smart email template ID or name does not exist or is invalid.
    • Merge fields missing or incorrectly named may cause the email content to be incomplete or fail.
    • Invalid email addresses in To, CC, or BCC fields can cause rejection by the API.
    • Attachments referencing non-existent or improperly named binary fields will not be included.
    • If tracking is disabled but expected, analytics may not be available.

  • Error Messages:

    • "Operation 'sendSmartEmail' not implemented for resource 'email'": Indicates a misconfiguration or unsupported operation; verify the resource and operation parameters.
    • API errors related to authentication usually indicate missing or invalid API credentials.
    • Validation errors from the API about recipient emails or template fields require checking input values carefully.

  • Resolutions:

    • Verify template existence and correct ID/name usage.
    • Ensure all required merge fields are provided with valid values.
    • Validate email formats before sending.
    • Confirm binary data fields for attachments are correctly set in previous nodes.

Links and References

Discussion