Send a Workflow Event
Tells a workflow campaign that something happened for a contact (a payment, a signed form), for its Await (event) blocks. Every event is kept: one that arrives before the contact reaches the Await still counts when they get there (if it arrived after they entered the workflow). A contact already waiting for it moves on at once by the Await’s Received path; one that isn’t waiting takes Timed out when the Await’s time limit passes. The event’s data is what later Conditionals read as the event’s fields.
payment_received), and have your system send that event here with the contact’s phone number when it happens.
- Early events count. An event that arrives before the contact reaches the Await is kept, and counts the moment they get there (as long as it arrived after they entered the workflow).
- One event moves one contact on, once. Send a
client_event_idto make retries safe. - What it brings. Later Conditionals can check the event’s
datafields (for example, “amount is greater than 1000”). - Testing. In the workflow editor, an Await (event) block waiting in a test run has Send test event, and For your developer shows this request ready to copy.
Authorizations
16-character API token associated with your OSVI account. Find it in your dashboard under Settings → API.
Path Parameters
The workflow campaign's numeric id.
Body
The event's name, as the Await block names it.
100"payment_received"
The contact's phone number, as in their batch (10-digit Indian mobile numbers and +91 numbers are matched either way). Give this or run_ref.
32"+919876543210"
One run, as Logs shows it (R-1042), instead of a phone number. A test run is only reached this way.
"R-1042"
Your own id for the event. Sending the same id again changes nothing (safe retries).
200"pay_8XK2"
Anything about the event later blocks can check, up to 8 KB.
