Automation platform integration

Twin Browser + n8n

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.

Get an API key Read the docs

Automation platform4-step setupBearer key auth

How Twin plugs into n8n

There is no Twin community node to install. Drop an HTTP Request node into the workflow, POST to `/api/v1/run` with your Bearer key in a header credential, and the structured result flows into the next node. That covers the case n8n cannot otherwise reach: the step in a workflow where the system on the other end has no API and somebody has been doing it by hand.

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

n8n → Twin

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

What you get through n8n

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 n8n.

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

HTTP Request node — POST /api/v1/runjson

// Method:  POST
// URL:     https://twin-browser.com/api/v1/run
// Auth:    Header Auth credential → Authorization: Bearer ab_live_…
// Body:    JSON

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

// A long run should not hold a workflow open. Use the async path instead:
//   POST /api/v1/jobs            -> { jobId }
//   GET  /api/v1/jobs/{jobId}    -> poll for the result
// or pass callbackUrl + callbackSecret and let n8n receive an HMAC-signed webhook.

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.

Create a credential
In n8n, add a Header Auth credential with name Authorization and value Bearer ab_live_… so the key is not typed into the node.
Add an HTTP Request node
Method POST, URL https://twin-browser.com/api/v1/run, and attach the credential.
Send the body
JSON body with url, prompt and success — success is required alongside url and prompt.
Use the result
Map the structured response into the next node in the workflow.

Read the n8n docs API reference

FAQ

n8n on Twin — common questions

Is there an n8n community node for Twin Browser?

No. The HTTP Request node is the supported path, and it needs no installation or approval in a self-hosted instance — which is usually an advantage rather than a compromise.

What if the browser task takes minutes?

Use the async endpoints. POST /api/v1/jobs returns a job id immediately; either poll GET /api/v1/jobs/{id} or supply callbackUrl and callbackSecret so Twin POSTs the completed result to an n8n webhook, HMAC-signed.

Go deeper

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.

Zapier

Automation platform

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.

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 n8n 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