Inputs
PreviewInputs are the typed details sent with each run, such as order number, item, amount and the shopper's phone and language.
Inputs are what a call knows before it dials. Each flow declares the inputs it needs, with a type for each. Every run must send them, by hand in the app, from a CSV, or through the API.
An example
The Order verification flow needs:
| Input | Type | Example | Required |
|---|---|---|---|
customer_name | text | Asha | yes |
phone | phone | +919812345678 | yes |
order_id | text | 4821 | yes |
items | text | a pair of running shoes | yes |
order_total | money | 2499 | yes |
address | text | 12 MG Road, Pune | yes |
language | text | hi-IN | no |
The shopper's number and name come from the run's phone and name (or the contact), and a consent record is sent with the run rather than as an input. Every field a run takes is in the API reference: Start a run.
Rules
- Phone numbers are in international format, for example
+919800000000. RowCall calls Indian mobile and landline numbers. - Missing required inputs stop the run before it dials, with a clear error. The call is never placed with half the details.
- Money inputs are read as rupees in words, so send
2499, not₹2,499. - Inputs are a snapshot. If something may change after the run starts, such as a payment succeeding, give the flow a read action so the call can look it up at that moment. See Actions.
- Send only what the call needs. Inputs are stored with the call record. Don't send data the flow doesn't use.
Inputs and actions
Inputs are the first source of facts. When a call needs something that may have changed, or wasn't needed up front, it asks for it with a read action, such as "get order", at that moment. This keeps calls short and facts fresh.
Next stepAnswers and outcomesWhat a call captures and how it ends.