Automation platform integration

Twin Browser + Zapier

Zapier is the largest no-code integration platform: a Zap triggers on an event in one app and runs actions in others. When no built-in action fits, Webhooks by Zapier makes a raw HTTP request to any API.

Get an API key Read the docs

Automation platform4-step setupBearer key auth

How Twin plugs into Zapier

Zapier and Twin solve opposite halves of the same problem. Zapier connects systems that expose APIs; Twin acts on systems that do not. Wire them together with a Webhooks by Zapier “Custom Request” action that POSTs to `/api/v1/run` — the Zap handles the trigger and the downstream apps, Twin handles the step where a person would otherwise have had to open a browser and sign in. There is no first-party Twin app in the Zapier directory; the webhook action is the supported path.

Twin is the browser execution layer your stack calls. The first run cold-compiles a skill via skill compilation; every similar request after that is matched from the cache and replayed deterministically, so your marginal cost per run trends toward zero rather than climbing with usage.

app.example.com

Zapier → Twin

Receive goal from Zapierdone
Compile DOM → token-efficient indexed statedone
Match the semantic dispatch cacherunning
Replay compiled skill — 0 LLM callsqueued

What you get through Zapier

Every integration is a thin wrapper over the same execution layer, so the cache, the replay, and the corpus apply no matter how you call in.

Semantic dispatch cache

A re-phrased goal fuzzy-matches an already-compiled skill, so most calls never touch the LLM.

Deterministic replay

A compiled skill replays the exact action path with zero LLM calls — fast, repeatable, cheap.

Cross-tenant skill corpus

A skill compiled once can be safely reused across tenants, so the hit rate climbs as the network runs.

One Bearer key

Auth, usage-based billing, and an audit log run on every call — the same key works from every integration.

Wire it up

Drop Twin into Zapier.

Copy, paste, and swap in your Bearer key. The first run compiles a skill; repeats match the semantic dispatch cache and replay deterministically.

Webhooks by Zapier — Custom Requestjson

// Action:   Webhooks by Zapier → Custom Request
// Method:   POST
// URL:      https://twin-browser.com/api/v1/run
// Headers:  Authorization | Bearer ab_live_…
//           Content-Type  | application/json
// Data:

{
  "url": "https://app.acme.com/billing",
  "prompt": "Sign in and download the latest invoice as CSV",
  "success": { "kind": "textVisible", "value": "Invoice" }
}

// Webhooks by Zapier is on the paid plans. Zapier's own step timeout is short
// relative to a browser task, so prefer the async path for anything slow:
//   POST /api/v1/jobs with callbackUrl -> Twin POSTs the result to a
//   "Catch Hook" trigger in a second Zap when the job finishes.

Base URL https://twin-browser.com/api/v1 · auth Authorization: Bearer ab_live_… · over MCP the same engine is run_goal, compile_skill and run_skill — the full tool table.

Add a webhook action
Add Webhooks by Zapier → Custom Request to the Zap.
Configure the request
Method POST, URL https://twin-browser.com/api/v1/run, Data Pass-Through off, JSON body.
Set the header
Add Authorization: Bearer ab_live_… under Headers.
Use the response
Zapier parses the JSON response, so later steps can map fields straight out of it.

Read the Zapier docs API reference

FAQ

Zapier on Twin — common questions

Is there a Twin Browser app in the Zapier directory?

No. Webhooks by Zapier is the supported path, which means the integration needs a Zapier plan that includes webhook actions.

Do Zapier and Twin compete?

Mostly they compose. Where an app has an API, a Zap beats a browser on every axis and Twin should stay out of the path. Where it does not, Twin is the step that signs in and does the work — and the honest comparison is on the Zapier comparison page.

Go deeper

n8n

Automation platform

n8n is a source-available workflow automation tool you can self-host or run in their cloud. Workflows are graphs of nodes, and the HTTP Request node calls any REST API — which is all a Twin integration needs.

Make

Automation platform

Make (formerly Integromat) is a visual automation platform where scenarios are built from modules on a canvas. Its HTTP module makes an arbitrary request, so any REST API becomes a step in a scenario.

REST API

API

Twin’s REST API is the universal integration path: HTTPS endpoints under `/api/v1/*`, authenticated with a Bearer key. Any language that can make an HTTP request can drive the browser execution layer — no SDK required, and none is published.

Wire up Zapier in minutes.

Free to start. Usage-based credits from $29/mo — each call billed the higher of its flat action price or its metered cost.

Get an API key See pricing