BizMail icon

BizMail

Interact with BizMail API

Actions5

Overview

This node integrates with the BizMail API to manage email marketing automations and subscribers. Specifically, for the Automation - Update Subscriber operation, it updates subscriber information within a specified automation based on given conditions and merge fields.

Typical use cases include:

  • Updating subscriber details in an existing email automation campaign.
  • Modifying subscriber attributes dynamically based on external data or workflow logic.
  • Automating subscriber management without manual intervention.

For example, you might update a subscriber's custom fields (like name, preferences, or status) when they perform certain actions tracked in your workflow, ensuring your automation sends personalized and relevant emails.

Properties

Name Meaning
Automation Name or ID Select the target automation by name or UUID where the subscriber will be updated. You can choose from a list or specify an ID via expression.
Update Conditions One or more conditions specifying which subscriber(s) to update. Each condition consists of a field name or ID and a value. These form the criteria to identify the subscriber(s) to update.
Merge Fields One or more fields to update for the matched subscriber(s). Each field includes a field name or ID and the new value to set. These represent the subscriber attributes that will be changed or added during the update.

Output

The node outputs JSON data representing the response from the BizMail API after attempting to update the subscriber(s). The structure typically contains success status and any returned data from the API call.

Example output JSON structure:

{
  "success": true,
  "data": {
    // API-specific response details about the updated subscriber(s)
  }
}

No binary data is produced by this operation.

Dependencies

  • Requires an API key credential for BizMail API authentication.
  • Needs network access to BizMail API endpoints.
  • The node uses HTTP POST requests to BizMail API URLs for updating subscribers.
  • The node expects the API credentials to provide base URL, app key, and project token.

Troubleshooting

  • Missing Email Field: If the subscriber's email is not provided in the merge fields when required, the node throws an error indicating that the email is mandatory.
  • Invalid Automation UUID: Providing an incorrect or non-existent automation ID will cause the API request to fail. Verify the automation exists and the ID is correct.
  • API Authentication Errors: Ensure the API key credential is valid and has necessary permissions.
  • Empty Conditions: If no update conditions are specified, the API may reject the request or update unintended subscribers. Always specify clear conditions.
  • Continue On Fail: If enabled, errors for individual items will be captured in the output instead of stopping execution.

Links and References

Discussion