Verify OTP
msg91.verify_otp
ActionVoice & SMSconnection required
Calls the MSG91 API with the connection's credentials.
Check the one-time password a recipient typed back; a wrong or expired code is reported, not raised as a step failure.
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, 2 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 |
otp The code the recipient entered, exactly as they typed it. | string | Yes | — | — | 1234 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"mobile": "919000000000",
"otp": "1234"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
verified True only when MSG91 accepted the code. | boolean | — |
type MSG91's own result word, 'success' or 'error'. | string | — |
message MSG91's explanation, such as 'OTP not match' or 'OTP expired'. | string | — |
mobile The number the code was checked against. | string | — |
{
"message": "",
"mobile": "",
"type": "",
"verified": false
}See Verify 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.