Send Verification Code

mocean.send_verify_code
ActionVoice & SMSconnection required

Calls the Mocean API with the connection's credentials.

Text a freshly generated verification code to a number and return the request id needed to check it.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
Mocean
Secret shape
{"api_token": "…"} — a Mocean API token, or {"api_key": "…", "api_secret": "…"}
Config it needs
base_url, sender_id, brand
Resolved by
config.connection_id, else node.connection_id

Configuration

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

FieldTypeRequiredDefaultConstraintsExample
to
Recipient number in international format, country code first and no plus sign; separate several numbers with commas.
stringYes——60123456789
brand
Company or application name shown in the message; overrides the default brand on the connection.
stringNo——Acme
sender_id
Sender ID shown to the recipient; overrides the default on the connection.
stringNo——MOCEAN
code_length
How many digits the generated code has; Mocean supports four or six.
numberNo—4–6—
pin_validity
How long the code stays valid, in seconds; Mocean defaults to 300.
numberNo—60–3600—

Example configuration

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

{
  "brand": "Acme",
  "sender_id": "MOCEAN",
  "to": "60123456789"
}

Output

One shape.

result

FieldTypeExample
reqid
The verification request id; mocean.check_verify_code needs it.
string—
to
The number the code was sent to.
string—
is_number_reachable
Mocean's reachability verdict for the number, or 'unknown'.
string—
{
  "is_number_reachable": "",
  "reqid": "",
  "to": ""
}

See Send Verification Code run in a workflow.

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