Getting started
Oxta runs chains of actions: something happens, a flow fires. The fastest way to understand it is to build the simplest flow by hand.
A flow in three minutes
- Flows → Create. Drag "HTTP Webhook" from the palette — that is the trigger everything starts from.
- Add "HTTP request" and connect the trigger to it. Put any public API in the URL, in quotes — ours works for a first try:
"https://app.oxta.io/api/health". - Add "Response" and connect it to the request. Body:
{"upstream": "{{outputs.http_1.response.data.status}}"}— replacehttp_1with the real id of your request node. - Save, press Run, and look at the node outputs.
- Now call the webhook address with
?wait=1and you get your body back as the answer.
If something is off, open the Diagnostics tab at the bottom of the editor. It names what is broken and links to the page that explains it. And when a run fails, the Runs tab shows each node's output along with an explanation of the error.
Where to go next
- Expressions — the main source of mistakes: moving data between nodes.
- Triggers and the response — when the caller waits and when it does not.
- Nodes — the full list with fields and outputs.
- Limits and plans — what a plan includes.
Things worth knowing up front
inputis the output of the previous node, not the request payload. Read the request by trigger name.- Node ids must be letters, digits and underscores, or expressions cannot read them.
- Your own AI key and your own database are connected in the profile, not in the node.