Resend OTP
msg91.retry_otp
ActionVoice & SMSconnection required
Calls the MSG91 API with the connection's credentials.
Resend the code already generated for a number, by text message or by voice call; MSG91 allows two retries per number.
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
2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
mobile Recipient number in international format, country code first and no plus sign. | string | Yes | — | — | 919000000000 |
retry_type How to resend the code: as a text message, or as a voice call. | string | No | text | one of "text", "voice" | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"mobile": "919000000000",
"retry_type": "text"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
type MSG91's own result word, 'success' on a resend. | string | — |
message MSG91's explanation of the outcome. | string | — |
mobile The number the code was resent to. | string | — |
retry_type Whether the resend went by text or by voice. | string | — |
{
"message": "",
"mobile": "",
"retry_type": "",
"type": ""
}See Resend OTP 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.