Actions16
Send Broadcast
AI-generatedOverview
This node operation sends an email broadcast campaign using the Bento API. It allows users to define the campaign name, subject, content (plain text or HTML), sender email and name, and audience targeting through inclusive/exclusive tags or segment ID. Users can also set batch size limits and confirm sending. This is useful for marketing teams or communication managers who want to send bulk email campaigns to segmented audiences with control over content format and delivery settings.
Use Case Examples
- Sending a promotional email campaign to leads tagged with 'lead' and 'mql' but excluding 'customers'.
- Sending a newsletter with HTML content to a specific segment identified by segment ID.
- Sending a plain text broadcast with a custom batch size limit per hour.
Properties
| Name | Meaning |
|---|---|
| Campaign Name | Name to assign to the broadcast campaign, used to identify the campaign. |
| Subject | Email subject line that recipients will see. |
| Content | Email content, either plain text or HTML based on the Content Type property. |
| Content Type | Determines if the email content is rendered as plain text or HTML. |
| From Email | Email address shown as the sender to recipients. |
| From Name | Display name shown as the sender to recipients. |
| Approved | Whether to mark the broadcast as approved for sending immediately. |
| Inclusive Tags | Comma-separated tags to include in the audience for the broadcast. |
| Exclusive Tags | Comma-separated tags to exclude from the audience for the broadcast. |
| Segment ID | Optional segment identifier to restrict the broadcast audience. |
| Batch Size Per Hour | Optional limit on the number of emails sent per hour; 0 uses Bento defaults. |
| Confirm Send | Whether to confirm sending this broadcast campaign. |
Output
JSON
operation- The operation performed, here it is 'sendBroadcast'.success- Boolean indicating if the broadcast was successfully submitted.name- Name of the broadcast campaign.subject- Subject line of the broadcast email.approved- Boolean indicating if the broadcast is approved for sending.segmentId- Segment ID used to restrict the broadcast audience, if any.apiResponse- Raw API response from Bento after submitting the broadcast.createdBroadcasts- Array of created broadcast objects returned by the API.errors- Array of errors if any occurred during broadcast submission.message- Human-readable message about the result of the broadcast submission.
Dependencies
- Bento API
Troubleshooting
- Ensure 'Confirm Send' is enabled to queue the broadcast; otherwise, the node throws an error.
- Campaign Name, Subject, Content, From Email, and From Name are required fields; missing any will cause validation errors.
- From Email must be a valid email format; invalid formats will cause errors.
- Content length is validated against limits depending on content type (plain text or HTML); exceeding limits causes errors.
- If the API credentials (publishableKey, secretKey, siteUuid) are missing or invalid, the node will fail authentication.
- Network issues or API rate limiting may cause request failures; the node implements retries with exponential backoff.
- Partial errors in broadcast submission are returned in the 'errors' array; review these for details.
Links
- Bento API Broadcasts Documentation - Official Bento API documentation for managing and sending broadcasts.