Exotel Create Call Campaign icon

Exotel Create Call Campaign

Create a new voice call campaign in Exotel

Exotel Create Call Campaign

AI-generated

Summary

Create a new voice call campaign in Exotel by specifying campaign details, call parameters, and optional retry and scheduling settings.

Inputs

  • Subdomain (required) — The Exotel API subdomain (e.g., api.exotel.com) for the request endpoint.
  • Account SID (required) — The Exotel account identifier used in the API URL.
  • Campaign Name (required) — Name of the campaign to be created.
  • Caller ID (required) — The phone number that appears as the caller ID for outbound calls.
  • Flow URL (required) — The URL to initiate the voice flow for the campaign calls.
  • List IDs (required) — A comma-separated string of list IDs containing the call recipients.
  • Number of Retries — How many times to retry calls on failure or specified statuses; default is 0.
  • Interval Minutes — Time interval in minutes between retry attempts; default is 2.
  • Retry Mechanism — Strategy for retry timing: 'Exponential' or 'Linear'; default is 'Exponential'.
  • On Status — Comma-separated call statuses (e.g., busy,no-answer,failed) triggering retries; default is 'busy,no-answer,failed'.
  • Status Callback URL — URL called by Exotel for campaign status updates.
  • Call Schedule Callback — URL called by Exotel to schedule calls.
  • Duplicate Numbers Allowed — Boolean flag whether duplicate numbers are allowed in the call list; default is true.
  • Enable Best Time to Call — Boolean flag to enable optimization of calling time based on past call data; default false.
  • Based on Data From — If 'Enable Best Time to Call' is true, choose the period (last 30 or 60 days) for data analysis; default is '30'.

Output shape

a single JSON object with Exotel API response data related to the created campaign

Returns an array with one item per input, each containing the full API response JSON in the 'json' field. Errors during the API call result in node execution failure with an error message.

Discussion