seed ▸ directory opened 0

Directories into clean lead records.

Build an extractor once, run it as an endpoint, and land structured leads in your CRM - from directories and profiles you have the right to access.

Build your lead pipeline See web data extraction
Writ runs on your own accounts, with your own credentials and data, on sites you are authorized to use.
Lead records → CRM
{ "company": "Acme", "name": "J. Lee", "role": "VP Ops" }
{ "company": "Globex", "name": "M. Sun", "role": "Head of RevOps" }
webhook → CRM · HMAC-signed
✓ login + 2FA✓ dynamic JS✓ wt_ API + MCP
flow ▸ pull · structure · route 1
01
How it flows

From a page to a CRM record.

A recorded workflow becomes a callable endpoint. It reads the pages you point it at, shapes each row into JSON, and delivers it where your CRM can ingest it.

Pull List, detail, and pagination on your own authorized accounts.
Structure Names, companies, roles, and public contact fields as clean JSON.
Route HMAC-signed webhook, your wt_ API, or an MCP tool call.
obs ▸ leads go stale 3
02
The problem

Good lead data is hard to keep fresh.

Lead lists go stale fast, manual copy-paste from directories doesn't scale, and the sources you trust rarely offer an export. RevOps ends up paying for thin data or burning analyst hours.

  • Lead lists go stale fast, and manual copy-paste does not scale.
  • The sources you trust rarely offer an export.
  • RevOps ends up paying for thin data or burning analyst hours.
act ▸ extract · enrich · route 10
03
How Writ solves it

Extract, enrich, and route to your CRM.

One recorded flow does the walking, the shaping, and the delivery - then runs again on demand or on a schedule.

Extract A recorded extract workflow walks list, detail, and pagination across directory pages.
Enrich Chain steps that open each profile and pull structured fields into one record.
Route Push records to your CRM via an HMAC-signed webhook or pull them from your wt_ API - or call the whole flow as an MCP tool from an AI agent.
gate ▸ login-only sources 24
04
The hard web

The sources without an export button.

The directories and portals worth pulling from are usually login-gated. Writ signs in on your own accounts and reads the pages plain HTTP can't reach.

  • ✓Sign in with your own credentials
  • ✓TOTP and mailbox OTP two-factor
  • ✓Dynamic JS pages
  • ✓Pagination and detail-page follow
api ▸ lead-pull called 42
05
Example

Directory to CRM.

POST https://api.usewrit.app/v1/lead-pull/run
Authorization: Bearer wt_…
Body: { "query": "…", "pages": 5 }
→ { "leads": [ { "company": "…", "name": "…", "role": "…", "url": "…" } ] }
# Automation: on finish → webhook → your CRM

One endpoint, one webhook - leads land in your CRM without copy-paste.

ok ▸ authorized data 60
06
Compliance

Keep it compliant.

Built for authorized lead data - public business information and sources you have the right to access. Respect each site's terms and rate limits, and the privacy laws that apply to your contacts. Your records stay in your tenant; you own them.

HMAC-signed webhooks Acceptable use
faq ▸ answered 86
08
FAQ

Lead generation questions.

Where does the data go?

Into your CRM via an HMAC-signed webhook or your own wt_ API - or to an AI agent as an MCP tool.

Is this allowed?

Built for authorized lead data - public business information and sources you have the right to access. You are responsible for respecting each site's terms and the privacy laws that apply to your contacts.

Can my AI agent run it?

Yes - every workflow is also an MCP tool your agent can call.

go ▸ pipeline live ∞

Stop copy-pasting leads.

Build an extractor once and let leads flow into your CRM automatically.

Get started See web data extraction