Use Writ
inside Zapier.

Give a Zap the one thing it can't reach on its own: a site with no API, behind your login.

Zapier connects thousands of apps that already expose an API. When the app or site you need doesn't have one, or the action lives behind a login with 2FA, there's no connector to pick, and a Zap can't drive a real browser to do it.

Writ makes the no-API site behave like any other step in a Zap. Use a "Webhooks by Zapier" action (or a scheduled Zap) to POST to the Writ endpoint /v1/{slug}/{path} with your wt_ key; Writ runs the browser workflow on your account and returns JSON the next Zap step can use. Writ can also POST into a "Catch Hook" trigger to start a Zap when a watched page changes.

1. 1

   Publish the workflow in Writ

   Record the login-gated action in Writ and publish it as a managed endpoint with a wt_ key.

2. 2

   Add a Webhooks by Zapier step

   In your Zap, add a "Webhooks by Zapier → POST" action pointed at /v1/{slug}/{path}, with the wt_ key in the Authorization header.

3. 3

   Attach a persona for login/2FA

   In Writ, attach a persona so login, TOTP, and mailbox-OTP 2FA are handled on your own account.

4. 4

   Map the response forward

   Use Writ's JSON response in the following Zap steps, or start a Zap from Writ via a "Catch Hook" trigger on a page change.

# Webhooks by Zapier → POST
URL:     https://api.usewrit.app/v1/{slug}/{path}
Method:  POST
Headers:
  Authorization: Bearer wt_xxx
  Content-Type:  application/json
Data:
  input.query: {{trigger.search_term}}

An honest split of who does what. Writ never replaces your orchestrator; it reaches the part it can't reach alone.

Publish the browser step as an endpoint and call it from your flow. Get started free, or book a demo.