Automation platform integration

Twin Browser + Make

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.

Get an API key Read the docs

Automation platform4-step setupBearer key auth

How Twin plugs into Make

Add an HTTP “Make a request” module, POST to `/api/v1/run` with your Bearer key, and parse the JSON response into the rest of the scenario. There is no Twin app in the Make directory; the HTTP module is the supported route. It earns its place at exactly the step where a scenario currently stops — the supplier portal or internal tool with no connector and no API.

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

Make → Twin

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

What you get through Make

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

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

HTTP module — Make a requestjson

// Method:          POST
// URL:             https://twin-browser.com/api/v1/run
// Headers:         Authorization: Bearer ab_live_…
//                  Content-Type: application/json
// Body type:       Raw (JSON)
// Parse response:  Yes

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

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 an HTTP module
Choose HTTP → Make a request in the scenario.
Configure the call
Method POST, URL https://twin-browser.com/api/v1/run, header Authorization: Bearer ab_live_….
Send the body
Raw JSON with url, prompt and success, and enable “Parse response” so later modules can map fields.
Map the result
Use the parsed output in the modules that follow.

Read the Make docs API reference

FAQ

Make on Twin — common questions

Is there a Twin Browser app in the Make directory?

No. The HTTP module is the supported path today, and it exposes the full API rather than a curated subset of it.

How do I avoid a scenario timing out on a long run?

Use POST /api/v1/jobs for the async path and either poll GET /api/v1/jobs/{id} in a later module, or pass callbackUrl and callbackSecret and receive the result on a Make webhook.

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.

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