Check Verification Token
messagebird.verify_token
ActionVoice & SMSconnection required
Calls the MessageBird API with the connection's credentials.
Check the token the recipient typed against a verification. The returned status is 'verified' on success and 'expired' or 'failed' when the code was late or wrong.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- MessageBird
- Secret shape
- the access key, or {"access_key": "…"}
- Config it needs
- originator, base_url
- 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 |
|---|---|---|---|---|---|
verify_id The id returned when the token was sent. | string | Yes | — | — | — |
token The code the recipient typed in. | string | Yes | — | — | — |
Output
One shape.
result
The provider's response object, as returned.
Extra keys beyond the ones listed can appear.
{}See Check Verification Token run in a workflow.
In a technical demo we add the MessageBird connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.