ENGINEERING
Zapier with your own gateway: AI in any Zap, sovereign
Just activated iSol API? Your key lives in the customer portal, isollm.ai/account → API keys. The endpoint used in every step below is https://tokens.4clouders.com/v1, and per-key spend updates on the same page. That is all you need to follow along.
Why the Webhooks action beats the built-in AI step
Zapier's prebuilt AI actions are convenient and priced per task, on someone else's endpoint. The Webhooks by Zapier action costs you nothing extra, calls your own gateway, and gives you the full request body: the model, the system prompt, the temperature, everything. Your automation stops being a black box.
Step 1: The action, field by field
Action: Webhooks by Zapier → Custom Request
Method: POST
URL: https://tokens.4clouders.com/v1/chat/completions
Headers: Authorization | Bearer sk-your-gateway-key
Content-Type | application/json
Data: { "model": "isol-4.9",
"messages": [
{"role": "system", "content": "Reply as JSON only: score, segment, next_step"},
{"role": "user", "content": "{{lead_message}}"}
] }
Use Custom Request, not the plain POST action: POST form-encodes the payload and the API needs raw JSON.
Step 2: Read the answer in the next step
Zapier flattens the response, so the model's text arrives as choices__0__message__content. Drop that into a Slack message, a CRM field or a spreadsheet row, whatever comes next in the Zap.
Step 3: The call, run for real
This is the exact request above, executed against our gateway with a realistic lead. Note that it returns strict JSON, which is what makes the next Zap step reliable:

Gotchas worth knowing
- Ask for JSON in the system prompt and the following steps stop guessing where the value is.
- Set a per-key budget. A Zap on a busy trigger fans out fast; the cap turns a runaway into a stopped task instead of an invoice.
- Same recipe in Make, with the HTTP module: see the pattern.
Step 4: Verify at the gateway, not at the client
Whatever the tool's screen says, the source of truth is the key's ledger. Every request lands there with model and token counts, so if nothing shows up, the change did not take:
curl -s https://tokens.4clouders.com/key/info \
-H "Authorization: Bearer sk-your-gateway-key" | jq .info.spend
Try it on ours
Our gateway (iSol API) runs exactly this setup on sovereign infrastructure, US$ 99/month, 14-day trial.
Same gateway, rest of your stack: every guide with real sessions
The pattern: one gateway, every tool
WhatsApp
Telegram
GitHub Actions
Teams
Claude Code
Cursor
VS Code
aider
OpenCode
n8n
Power Automate
Power BI
Google Sheets
Website chatbot
Hermes Agent