Get Delivery Analytics

msg91.get_analytics
ActionVoice & SMSconnection required

Calls the MSG91 API with the connection's credentials.

Retrieve daily sent, delivered, failed and credit totals for SMS or OTP traffic over a window of at most 31 days.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
MSG91
Secret shape
the MSG91 authkey, or {"authkey": "…"}
Config it needs
base_url, sms_template_id, otp_template_id
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
product
Which MSG91 channel the report covers.
stringNosmsone of "sms", "otp"—
start_date
First day of the reporting window, as a yyyy-mm-dd calendar date.
stringYes——2026-01-01
end_date
Last day of the reporting window, as a yyyy-mm-dd calendar date.
stringYes——2026-01-02

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "end_date": "2026-01-02",
  "product": "sms",
  "start_date": "2026-01-01"
}

Output

One shape.

result

FieldTypeExample
product
The channel the report was pulled for, 'sms' or 'otp'.
string—
data
One row per day (analytics) or per message (logs).
array—
count
How many rows the response carried.
number—
total
Window totals: delivered, failed, rejected, filtered and credits.
object—
{
  "count": 0,
  "data": [],
  "product": "",
  "total": {}
}

See Get Delivery Analytics run in a workflow.

In a technical demo we add the MSG91 connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.