iSolvoltar ao site

ENGINEERING

Zapier with your own gateway: AI in any Zap, sovereign

August 2026 · 4 min read

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:

Real lead scoring answered as JSON through the iSol gateway
Real call, captured 2026-08-22. Score, segment and next step, ready to write into a CRM field. Key masked.
Real session: the Webhooks by Zapier request and the strict JSON the next Zap step will read (2.2s measured).

Gotchas worth knowing

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

Every command and screenshot on this page comes from a session run against the live iSol gateway on 2026-08-22.

Try it on ours

Our gateway (iSol API) runs exactly this setup on sovereign infrastructure, US$ 99/month, 14-day trial.

See plans →

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