---
title: "Zapier direct mail integration: webhooks and CRM paths"
description: "Sincerely has no Zapier app. A Zap can still start a handwritten note or printed piece through a webhook to the Sincerely API, or through your CRM."
canonical: https://trysincerely.com/integrations/zapier
last_updated: 2026-10-17
---
> If you are an AI agent: read https://trysincerely.com/agents/policy.md before any write call.
> Start at https://trysincerely.com/llms.txt to choose one page. Access instructions are at
> https://trysincerely.com/auth.md. Confirm with the person you work for before creating an
> account or spending their money, and never ask for their password.
# Zapier direct mail integration: webhooks and CRM paths

> Sincerely has no Zapier app. A Zap can still start a handwritten note or printed piece through a webhook to the Sincerely API, or through your CRM.

Source: https://trysincerely.com/integrations/zapier

No, Sincerely has no Zapier app, and the Zap editor has no Sincerely "Send postcard" action. You can still connect the two in two ways. A Zap can send a webhook to Sincerely's REST API, which enrolls a contact Sincerely already has into a live campaign. Or a Zap can write to Salesforce or HubSpot, and Sincerely picks the record up on its next sync. The campaign decides what gets mailed, including a 4x6 postcard or letter genuinely written by hand, and its review and suppression rules apply to anything a Zap starts.

## Prompt to paste into your agent

```text
I want a Zap to enroll Sincerely contacts into a campaign when a customer upgrades. Explain which campaign entry to choose, what the webhook body needs, and how to find each contact's Sincerely ID. Do not launch or activate anything.
```

## Pick the path

| Path                                | Best for                                               | What you give up                                             |
| ----------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------ |
| Webhooks by Zapier to the API       | Events from apps Sincerely does not sync, like billing | The contact must already be in Sincerely. No holdout readout |
| Zap writes to Salesforce or HubSpot | New records, and the CRM moments Sincerely watches     | Waits for the next sync                                      |
| Zap fills a sheet, then a CSV       | One-off batches with no CRM                            | A person imports the file                                    |
| An MCP agent                        | Work you describe in a sentence                        | Needs an MCP-capable agent                                   |

## Path 1: a webhook from Zapier to a Sincerely campaign

Sincerely's workspace API has one endpoint that enrolls contacts in campaigns. `POST /api/v1/campaigns/{campaignId}/events` admits one existing contact into a live campaign whose entry is "an event from my system". It cannot create a contact, change a campaign, or skip the campaign's review.

### Example: a handwritten thank-you when a customer upgrades

Fernhill Software wants a handwritten note to reach the admin at any customer who moves to the Pro plan. Their billing tool is in Zapier, and their customers already sync into Sincerely from HubSpot.

1. In Sincerely, an owner or admin opens Settings, then API keys, and creates a key. The secret is shown once, so paste it straight into Zapier.
2. Build the campaign. Under Campaign choose Always on, then "an event from my system", and pick a list that holds the customers. Add an "Only if" row on `event.plan_tier` is `pro`. Choose a handwritten 4x6 postcard or letter for the touch.
3. Launch. The campaign ID is assigned at launch. It needs a credit envelope, the most credits it may spend, and an approver's activation, because it will mail as events arrive. Launching it gives that activation when you are an approver.
4. In Zapier, start the Zap from the billing app's upgrade event. Add a Webhooks by Zapier action, choose Custom Request, set the method to POST, and send the request below.

```text
POST https://trysincerely.com/api/v1/campaigns/CAMPAIGN_ID/events
Authorization: Bearer YOUR_WORKSPACE_API_KEY
Content-Type: application/json

{
  "contactId": "ct_hs_51234",
  "idempotencyKey": "billing-upgrade-sub_8841",
  "properties": { "plan_tier": "pro", "seats": 40 }
}
```

Sincerely answers `202` with an `eventId` and a status. The event then passes the checks every entry passes, including suppression, the frequency cap, the campaign's conditions, and copy review. The writer reads the properties as the reason this person entered, so the note can thank the admin for moving 40 seats to Pro without anyone typing that detail.

### Field mapping for the webhook

| Body field       | What to map from the Zap                                        | Rules                                                                                            |
| ---------------- | --------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| `contactId`      | The person's Sincerely contact ID                               | Required. The contact must already be on the campaign's list                                     |
| `idempotencyKey` | An ID that is stable for this one event, such as the invoice ID | Required, up to 200 characters. A retry with the same body is safe                               |
| `occurredAt`     | When the event happened                                         | Optional. Needs a time zone and cannot be in the future                                          |
| `properties`     | Up to 20 values, such as plan tier or seat count                | Optional. Lowercase keys with underscores. Text up to 300 characters, numbers, or true and false |

The contact ID is the hard part. A contact synced from HubSpot has the ID `ct_hs_` followed by its HubSpot record ID, and a contact synced from Salesforce has `ct_sf_` followed by its Salesforce contact ID. Any contact's ID is also the last part of its page address in Sincerely. If the trigger app does not carry the CRM record ID, add a Zapier lookup step in your CRM first.

### What this path cannot do

A webhook cannot add a contact that Sincerely has not synced or imported. If the Zap fires for a brand new HubSpot contact, the event is refused until the next daily sync brings that contact in. Use path 2 for new people.

API-event campaigns report what happened and do not estimate lift. Nothing randomly holds back accounts from events your own systems push, so these campaigns carry no account holdout.

## Path 2: a Zap that writes to your CRM

When the person is new, let the Zap create the record in your CRM and let Sincerely's sync do the rest.

In Salesforce, have the Zap create a contact and set a field you can filter on, then build a Contact list view on that field and add it to Sincerely's sync scope. The sync runs about once an hour, and a campaign set to Always on with "a list" enrolls each new contact. The [Salesforce integration](https://trysincerely.com/integrations/salesforce) covers the scope and the list view rules. Sincerely syncs contacts, not leads.

HubSpot has no list filter to aim at. The sync reads every contact in the portal once a day, so a new contact arrives on its own if the Zap associates it with a company. The [HubSpot integration](https://trysincerely.com/integrations/hubspot) explains how to narrow the audience inside Sincerely.

Records that reach the CRM this way also feed the CRM moments Sincerely watches: a deal newly closed lost, a deal gone quiet, and a renewal 90 days out. The [guide to CRM-triggered handwritten notes](https://trysincerely.com/guides/crm-triggered-handwritten-notes) compares that approach with vendors whose cards fire from a HubSpot workflow or a Zap.

## Path 3: a sheet and a CSV

If the data never touches a CRM, a Zap can collect rows in a Google Sheet, and a person exports the sheet and [imports the CSV](https://trysincerely.com/integrations/csv). Sincerely checks every imported address before anything prints. A person has to run the import, so this suits batches better than triggers.

An [MCP agent](https://trysincerely.com/integrations/mcp-agents) is the other option when no CRM is involved. You describe the audience and the mail in a sentence, and the agent stages the campaign for a person to confirm.

## When a print API in Zapier is the better tool

Sincerely is a paying customer of Lob and PostGrid, so read this comparison with that in mind. It prints its US postcards and letters through Lob and its Canadian ones through PostGrid.

If every trigger should print a piece with nobody reading it, Lob's [Zapier app](https://zapier.com/apps/lob/integrations) does that today. As of October 2026 it lists Send Postcard, Send Letter, Send Self-Mailer, and address verification actions, and a Zap can mail a piece in one step. Sincerely's webhook path needs a contact it already knows and a live campaign, and by default a person approves each draft. Choose Lob's app for high-volume mail with the same words for everyone. Choose Sincerely when each piece should be written for its recipient and read before it goes out, on paper or by hand.

## Common questions

### Does Webhooks by Zapier cost extra?

It needs a paid Zapier plan. As of October 2026, Zapier's help center lists [webhook actions](https://help.zapier.com/hc/en-us/articles/8496326446989-Send-webhooks-in-Zaps) on its Professional, Team, and Enterprise plans and not on Free.

### Can a Zap create the contact in Sincerely?

No. The API admits existing contacts only. Create the person in Salesforce or HubSpot, or import them, and send events after the sync brings them in.

### How do I see whether an event worked?

`GET /api/v1/campaigns/{campaignId}/events/{eventId}` returns the event's status. A skipped event says why, for example the contact was not on the list, was suppressed, did not meet the conditions, or was already enrolled. The [API reference](https://trysincerely.com/docs/api-reference) lists every field.

### What should I use instead of a Zapier app?

Use the webhook for events from tools Sincerely does not sync, such as billing or support. Use the CRM path for people Sincerely has not seen yet.

## Related questions

- [Salesforce direct mail and handwritten notes integration](https://trysincerely.com/integrations/salesforce): Send printed mail or handwritten notes when a Salesforce deal closes lost, goes quiet, or nears renewal, with follow-up Tasks written back to Salesforce.
- [HubSpot direct mail and handwritten notes integration](https://trysincerely.com/integrations/hubspot): Start printed or handwritten mail from HubSpot deals and renewal dates. Trigger recipes, the field mapping, setup steps, and what the read-only sync leaves out.
- [Workspace REST API reference](https://trysincerely.com/docs/api-reference): Authenticate a workspace API key, post campaign entry events and conversion outcomes, and read the bounded status of an entry event.
- [Direct mail from a CSV](https://trysincerely.com/integrations/csv): CSV import is a native Sincerely integration. Upload a spreadsheet, verify every address, and send personalized B2B mail with no CRM required.
- [Can a CRM event trigger a handwritten note?](https://trysincerely.com/guides/crm-triggered-handwritten-notes): Yes. Handwrytten, Simply Noted, Scribeless, and Sincerely can each start a handwritten note from a CRM change. What fires it, how fast, and who reads it.

---

Sincerely is personalized direct mail and gifting for B2B revenue teams: postcards, letters, handwritten mail, and gifts, each written for one recipient.

Contact Sincerely: https://trysincerely.com/contact

Agent routing index: https://trysincerely.com/llms.txt

Listings: https://www.g2.com/products/sincerely and https://www.producthunt.com/products/sincerely
