No node to install. Three mechanisms that already work.

To be straight with you: there is no first-party Writ node for n8n, app for Zapier, or module for Make. Do not go looking in a directory. What exists is three generic mechanisms all three tools already speak — and each one is a five-minute setup.

framing ▸ what exists

Pick the direction you need.

The question is which way the call travels. Writ is either the thing your flow calls, or the thing that starts your flow — and OAuth is how a tool holds your credential without you pasting a key into it.

call ▸ http request

1 · Call Writ from the tool.

Publish a workflow as an endpoint, then point the tool’s HTTP Request node — or Webhooks by Zapier, or Make’s HTTP module — at it. That is the whole integration.

curl -X POST https://api.usewrit.app/v1/acme/price-check \
  -H "Authorization: Bearer $WRIT_CONSUMER_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com/product/42"}'

{
  "method": "POST",
  "url": "https://api.usewrit.app/v1/acme/price-check",
  "headers": {
    "Authorization": "Bearer csk_...",
    "Content-Type": "application/json"
  },
  "body": { "url": "https://example.com/product/42" }
}

When a run is longer than the tool will wait

Ask for a handle up front instead. Send Prefer: respond-async, or add ?async=true if the tool’s HTTP step cannot set a header — you get a 202 and a run handle to poll.

curl -X POST https://api.usewrit.app/v1/acme/price-check \
  -H "Authorization: Bearer $WRIT_CONSUMER_KEY" \
  -H "Prefer: respond-async" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com/product/42"}'

# Query-parameter form, for tools whose HTTP step cannot set a header:
curl -X POST "https://api.usewrit.app/v1/acme/price-check?async=true" \
  -H "Authorization: Bearer $WRIT_CONSUMER_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://example.com/product/42"}'

oauth ▸ self-configuring

2 · Connect with OAuth.

Writ runs an OAuth 2.0 authorization-code server with PKCE, and publishes a discovery document at /api/oauth/.well-known/oauth-authorization-server. Generic OAuth integrations read that document and configure themselves — endpoints, scopes and PKCE method, without you typing any of them.

curl https://api.usewrit.app/api/oauth/.well-known/oauth-authorization-server

events ▸ into the tool

3 · Have Writ start the flow.

Every one of these tools gives you a catch-hook URL — a Webhook trigger node in n8n, a Catch Hook in Zapier, a Custom Webhook in Make. Point a Writ monitor or automation at it and your flow starts when something actually happens.

1. 1 · Copy the catch-hook URL — From the trigger step in your tool.
2. 2 · Add it as a webhook recipient in Writ — On the monitor or automation that should start the flow.
3. 3 · Verify the signature — Deliveries are HMAC-signed. Check the signature before you trust the payload.

also ▸ two more doors

Two other ways in.

Not every tool needs an HTTP step. If yours already speaks one of these, use it directly:

reference ▸ next

Keep going

faq

Integration questions, answered.

end ▸ wire it

Publish an endpoint and point a step at it.

One HTTP request node is the whole integration, and it works in every tool on this page.