Bento icon

Bento

Native integration for Bento API actions

List Broadcasts

AI-generated

Overview

This node operation 'List Broadcasts' interacts with the Bento API to retrieve a list of broadcast campaigns. It supports filtering broadcasts by their status (e.g., any, archived, draft, scheduled, sending, sent), filtering by creation date (only broadcasts created after a specified date), and filtering by specific tag IDs linked to broadcasts. This operation is useful for users who want to manage or analyze their broadcast campaigns by retrieving relevant broadcasts based on these filters.

Use Case Examples

  1. A marketing team wants to list all scheduled broadcasts to review upcoming campaigns.
  2. A user wants to retrieve all broadcasts created after a certain date to analyze recent campaign performance.
  3. Filtering broadcasts linked to specific tags to segment campaigns by audience groups.

Properties

Name Meaning
Status Filter broadcasts by their status such as any, archived, draft, scheduled, sending, or sent.
Created After Return broadcasts created after this specified date.
Tag IDs Filter broadcasts linked to specific tag IDs. Multiple tag IDs can be specified.

Output

JSON

  • operation - The operation performed, here it will be 'listBroadcasts'.
  • success - Boolean indicating if the operation was successful.
  • filters
    • status - The status filter applied to the broadcast listing, if not 'any'.
    • createdAfter - The date filter applied to only include broadcasts created after this date.
    • tagIds - Array of tag IDs used to filter broadcasts.
  • total - Total number of broadcasts retrieved.
  • scheduledCount - Count of broadcasts with status 'scheduled'.
  • apiResponse - The raw API response from Bento containing broadcast data.
  • message - A message summarizing the result of the operation.

Dependencies

  • Bento API

Troubleshooting

  • Ensure the Bento API credentials (publishableKey, secretKey, siteUuid) are correctly configured and valid.
  • Verify that the 'Created After' date is in a valid date format to avoid validation errors.
  • Check that tag IDs are correctly formatted strings and do not exceed length limits.
  • Common error messages include authentication failures, invalid request parameters, and network errors. Verify credentials and input parameters accordingly.

Links

Discussion