Check Verification Code
vonage.verify_check
ActionVoice & SMSconnection required
Calls the Vonage API with the connection's credentials.
Check the code the user typed against a verification started earlier. A wrong or expired code fails the step, so an error edge can route the retry.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Vonage
- Secret shape
- {"api_key": "…", "api_secret": "…"}
- Config it needs
- api_region, from_number
- 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 |
|---|---|---|---|---|---|
request_id The request id the verification request returned. | string | Yes | — | — | c11236f4-00bf-4b89-84ba-88b25df97315 |
code The code the user entered, 4 to 10 characters. | string | Yes | — | 4–10 characters | 1234 |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"code": "1234",
"request_id": "c11236f4-00bf-4b89-84ba-88b25df97315"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
request_id The verification the code was checked against. | string | — |
status The verification's status, such as completed. | string | — |
{
"request_id": "",
"status": ""
}See Check Verification Code run in a workflow.
In a technical demo we add the Vonage connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.