Custom API
Custom API + any website
Read a table, a price or a listing on the page you're on and send it to Custom API.
Automate Custom API from your browser
Call any REST API from an OpenAPI spec in workflows that start from the page you're on. Requests go from your browser to the API you choose, nothing in between.
What you can do
Each action, one node.
Each action is a node you drop on the canvas. Pair it with any of the 10 triggers — a schedule, a right-click, a page change.
This node has no fixed list of actions — the docs explain what it can do. Read the docs ↗
Popular pairings
Better together.
Custom API
Custom API + on-device AI
Classify, summarise or rewrite with a model that runs in your browser before it reaches Custom API.
Templates
Templates that use Custom API
No published templates use Custom API yet. Docs recipe ↗
How to connect
Three steps. No surprises.
Drop the node on the canvas
Custom API needs no saved credential to start. Add one only if the service you call asks for it.
Fill in the settings
Point it at the address or service you want — the node settings explain each field.
Run it once
Press Run in the editor to check the result before you put it on a trigger.
FAQ
Good questions.
Does my data go through AWFlow servers?
No. When a step runs, your browser sends the request to the API you point the node at. AWFlow's servers never relay the call.
Do I need an AWFlow account?
No. Local mode works without an account and keeps the Custom API credential in this browser. Signed in, you choose per credential: this browser or your account. Installing a template from the Marketplace needs sign-in.
Does it run when my browser is closed?
No. Workflows run while your browser is open. A Wait of a minute or more in the extension survives closing the tab and picks up where it left off, for up to 30 days.
Does it cost anything per run?
No. Workflows run in your browser, so there are no per-task fees. Custom API applies its own usual limits.
