​
Choose the right public run route

EESI exposes two public outbound agent run route families. They are not interchangeable, even though both path parameters look like UUIDs.
Do not pass a workflow UUID to /public/agent/{uuid} and do not pass a trigger UUID to /public/agent/workflow/{workflow_uuid}. EESI treats these as different identifier types and the request will fail if you mix them up.
Once EESI resolves the target agent, both route families behave the same:
  • They accept the same request body
  • They return the same response shape
  • They validate the same API-key organization boundary
  • They use the same telephony configuration selection rules
If you specifically need the API Trigger route, see Trigger an outbound agent run by API Trigger node. To execute by Agent UUID, see Trigger an outbound agent run by Agent UUID.

​
Using initial context

initial_context passes runtime data into the agent at run time. Values are available as template variables in your agent’s prompt using double-brace syntax.
Your agent prompt can then reference {{customer_name}} and {{appointment_date}} and they will be substituted when the run starts.

​
Run status values