Writ fits your stack.
Every workflow you build is a REST endpoint, an MCP tool, and a signed webhook - so a site with no API drops straight into the tools you already run.
Build once. Reach it four ways.
The same workflow answers over whichever door your stack prefers. No new SDK, no glue service - just the interface you already speak.
The browser step your automation platform is missing
n8n, Zapier, and Make can call an HTTP endpoint - so they can call Writ. Drop a login-gated, 2FA-protected site into a flow as one callable step, and get JSON back to route onward.
- n8nAdd an HTTP Request node that calls a Writ workflow, then branch on the JSON it returns.
- ZapierUse Webhooks by Zapier to run a Writ workflow mid-Zap and hand the result to the next step.
- MakeCall Writ from an HTTP module in a scenario and map its output into anything downstream.
one workflow, two front doors
# REST: call any workflow, get JSON back
curl https://api.usewrit.app/v1/acme-portal/orders \
-H "Authorization: Bearer wt_…"
# MCP — the same workflow, as a tool in your agent
{ "url": "https://api.usewrit.app/mcp",
"headers": { "Authorization": "Bearer wt_…" } } The connector is the easy part - it's what moves through it
Extract from a site with no API and push it to a sheet; watch a page and trigger a scenario; hand your agent a login-gated workflow over MCP.
OAuth, done right
Writ implements the OAuth 2.0 Authorization Code flow with PKCE. Register an application, define redirect URIs and scopes, and Writ issues short-lived authorization codes and Argon2-hashed access and refresh tokens, prefixed wto_. Tokens are scoped, revocable, and isolated - connect third-party tools without ever sharing yourwt_ API keys.
- Register app Define redirect URIs and scopes.
- User authorizes They approve access on the consent screen.
- Exchange code Trade a single-use, 10-minute code for tokens.
- Call with token Use the wto_ token - scoped and revocable.
Looking for a specific tool?
The integrations directory lists every platform and AI tool Writ connects to, each with its own setup guide.
Don't see your tool? Every workflow is also a plain REST endpoint and a signed webhook - so you can wire it into anything, even without a dedicated connector. Read the API docs
Put any site inside the tools you already run.
Build a workflow once, then reach it over REST, MCP, a signed webhook, or OAuth.