Set up live sync via Zapier

Zapier live sync is the long-tail integration path — it lets you stream closed-lost deals into Thawly from any CRM, spreadsheet, or sales tool that Zapier already speaks to, without waiting for a native OAuth integration.

What live sync does#

• Thawly receives closed-lost deals from your CRM the moment your Zap fires (most users trigger it on a "deal stage changed to Closed Lost" event in their source CRM).
• Lost deals you mark anywhere Zapier reaches appear in Thawly automatically.
• Re-engagement signals fire when one of your monitored companies' UK public-data triggers lines up with a closed-lost deal pushed in via your Zap.

What data Thawly reads#

Zapier is unusual — Thawly doesn't read from a CRM at all. You decide which fields the Zap sends. Thawly accepts exactly these fields per inbound webhook call:

• companyName (required, ≤ 200 chars)
• dealValue (number or numeric string, optional)
• lostDate (ISO date YYYY-MM-DD or full ISO timestamp, optional)
• lostReason (free text ≤ 500 chars, optional)
• productPitched (free text ≤ 500 chars, optional)
• contactRole (job title only, e.g. VP Sales, ≤ 200 chars, optional)
• notes (free text — call summaries, etc., optional)

There are no OAuth scopes because there is no OAuth — Zapier authenticates with a per-org bearer token you generate in Thawly and paste into the Zap's Authorization header.

Thawly never sees contact-level personal data — don't send us contact names, emails, or phone numbers via Zapier. The field list above is the contract; everything else is dropped.

What Thawly never does#

• Never reaches into your source CRM — Zapier is push-only, and you control what each Zap pushes.
• Never deletes records.
• Never stores the bearer token in plaintext — it's hashed with HMAC-SHA256 at rest.
• Never writes back to your source CRM (the Zapier path doesn't support write-back; use Zapier's two-way action if you need that).

Set up#

Click below to set up your Zapier connection. You'll be prompted to generate a bearer token, then walked through wiring the Zap.

Connect via Zapier →

Or follow these manual steps if you prefer:

1. In Thawly, open Settings → Integrations.
2. On the Zapier card, click Manage Zapier connection.
3. Click Generate token. The plaintext token is shown once — copy it immediately into your password manager or directly into the Zap.
4. In Zapier, create a new Zap. Trigger: "deal stage changed to Closed Lost" (or your CRM's equivalent). Action: Webhooks by Zapier → Custom Request.
5. Configure the action: POST to https://app.thawly.co.uk/api/integrations/zapier/webhook, Authorization header set to Bearer <your-token>, body set to a JSON object using the field list above.
6. Test the Zap with a sample deal — Thawly returns a 200 OK if everything's wired correctly.

For the full walkthrough including which Zapier triggers work best for each CRM, see Integrate via Zapier.

After setup#

• Sync is real-time — every Zap fire delivers a deal within seconds.
• See total deals delivered, last-delivery time, and any failed deliveries on the integrations page.
• Rotate the bearer token any time from Settings → Integrations → Manage Zapier connection. Generating a new token invalidates the old one immediately.
• Disconnect any time — clears the stored token hash and rejects all future Zap calls until you generate a new one.