Connect Any API
Connects any tool with an HTTP API — a booking system, an ERP, your own backend — by naming its base URL, how it authenticates, and the endpoints you need.
Updated 2026-11-02
01What it does
- Rules: call any endpoint you define, with fields mapped from the event
02What you need
- Base URL. Everything before the endpoint path, e.g. https://api.yourtool.com/v1
- Auth header name (optional). Authorization, X-Api-Key, or whatever their docs say. Leave blank for no auth.
- Auth header value (optional) — kept encrypted, never shown again. The full value, including any prefix like 'Bearer '.
03Connect it
- From the other tool's API docs, note the base URL (e.g. https://api.yourtool.com/v1), the auth header name and its value (e.g. Authorization: Bearer …).
- In your site → Manage → Integrations, choose Any API and fill in the base URL and auth.
- Add each endpoint you need: method, path, and a JSON body using {{in.field}} slots for the values a rule will fill.
- Press Connect, then make a rule that uses one of your endpoints.
04Check it works
- Submit your own site's form once, then open the tool's run log (the clock icon on its card): a green row with a 2xx status means the other side accepted it.
05If it does not work
- Blocked as a private address — Only public HTTPS hosts can be called — not localhost or a private IP.
- Body arrives with a string where a number was expected — Make the slot the whole value ("{{in.amount}}") so it keeps its type.
- Asked to re-enter the secret after changing the base URL — Intended: a key is never sent to a new host without being entered again.