---
title: "Salesforce direct mail: automate mail from your CRM"
description: "Sync accounts and contacts from Salesforce, write each piece from CRM context, approve before anything prints, and time rep follow-up to confirmed delivery."
canonical: https://trysincerely.com/integrations/salesforce
last_updated: 2026-10-08
---
> 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.
# Salesforce direct mail: automate mail from your CRM

> Sync accounts and contacts from Salesforce, write each piece from CRM context, approve before anything prints, and time rep follow-up to confirmed delivery.

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

Keep the audience in Salesforce instead of letting a spreadsheet export decide who gets mail weeks later. Scope the contacts, keep their accounts and opportunity outcomes attached, and let Sincerely write one piece for each recipient. Eligible delivery events raise a follow-up task. A newly observed closed-lost opportunity can also start the closed-lost revival flow. There is no middleware or CSV shuffle in between.

## Prompt to paste into your agent

```text
Send a letter to the 40 accounts in my Salesforce list called Q4 Tier 1. First check sync health, mailability, the approved design, holdout, and credit need. Show me the exact launch confirmation and wait for my decision before anything prints.
```

Salesforce is one of four ways to bring an audience into Sincerely. The others are [HubSpot](https://trysincerely.com/integrations/hubspot), [CSV import](https://trysincerely.com/integrations/csv), and the [MCP server](https://trysincerely.com/integrations/mcp-agents).

## How to automate direct mail from Salesforce

The whole path runs in six steps, and a person stays in the loop at the two moments that matter: approving the copy and confirming the spend.

1. **The audience syncs from Salesforce.** Choose all eligible contacts or narrow them by compatible contact list views, owners, country, state, title, or the presence of a mailing address. Related accounts and opportunities sync with those contacts. Every address is resolved and checked for mailability before anything can print. Bad addresses are flagged for review, not mailed.
2. **Each piece is written for its recipient.** Sincerely drafts one message per person from the synced name, title, account context, and researched account facts. Two contacts at the same account do not receive the same postcard.
3. **A person approves.** Copy can wait for human review or auto-approve after the first ten researched pieces pass review. A draft that leans on a thin or unsourced claim always waits for a person, and a person confirms the campaign launch and the spend.
4. **The piece prints and mails.** Sincerely routes each piece by format and destination country to a professional print partner and records the fulfillment state, including postal delivery events where the partner returns them. Each contact gets each step exactly once, so a retried job can never double-mail anyone.
5. **Delivery confirmation raises a follow-up task.** A confirmed delivery creates a task due the next day. Standard printed United States postcards and letters return automatic postal events. Gifts carry carrier tracking and can receive delivery confirmation from the fulfillment team. Handwritten mail has no delivery confirmation, and Canadian printed mail reports an estimate. Optional Salesforce task writeback uses the owner and campaign scope an admin chose.
6. **Outcomes follow the campaign's measurement policy.** Eligible randomized campaigns lock their primary outcome, measurement window, and account-level holdout at launch, then report lift with confidence intervals. Hand-picked follow-ups and objectives observed only through a mailed piece report descriptively. The [measurement page](https://trysincerely.com/measurement) explains what each signal can honestly claim.

## What syncs in and what comes back out

The audience sync reads from Salesforce. The only optional writeback creates follow-up tasks after eligible delivery events; Sincerely does not edit accounts, contacts, or opportunities.

In:

- **Contacts and their accounts.** Sincerely reads names, titles, contact owners, email and mailing addresses, plus account name, website, and employee count. Leads do not sync; convert them first or bring them in by [CSV](https://trysincerely.com/integrations/csv).
- **Opportunity observations.** Stage, amount, close date, and closed or won status support outcome measurement and the newly observed closed-lost trigger. Other custom fields do not sync today. The exceptions are an account renewal date field you map for the renewal trigger and a user or text field you choose to sign a touch with.
- **Context for writing.** Synced contact and account fields feed each draft alongside researched account facts, so the piece can address the recipient's role and the account situation without inventing private context.
- **Suppression.** Suppress a contact once and it is suppressed immediately and globally, across every campaign. See the [suppression guide](https://trysincerely.com/guides/direct-mail-suppression).

Back out:

- **Follow-up tasks timed to confirmed delivery.** Every eligible delivery event can raise a task in Sincerely. A workspace admin can also enable Salesforce task writeback, choose the owner and campaign scope, and preview the task before saving the setting. The [delivery follow-up guide](https://trysincerely.com/guides/direct-mail-delivery-follow-up) covers the timing.
- **Readouts.** Measurement lives in Sincerely, reporting lift against account-level holdouts with confidence intervals. CRM matchback is labeled as inference, not proof.

## Motions the Salesforce connection supports

The connection supports fewer triggers than a general workflow builder, by design:

- **A contact enters the chosen sync scope.** A compatible Salesforce contact list view, selected owners, or the built-in title and geography filters can keep an audience current without another export.
- **An opportunity becomes closed lost.** The [closed-lost revival play](https://trysincerely.com/playbooks/closed-lost-revival) can enroll contacts only after Sincerely observes a new closed-lost transition, never from historical backfill. Activating that unattended flow requires its own approval and credit envelope.
- **An open opportunity goes quiet.** When stage, amount, and close date have not changed for a set number of days, 21 by default, the deal-quiet trigger can enroll its contacts. Emails and calls logged in Salesforce do not reset that clock. The [guide to mailing quiet and lost deals](https://trysincerely.com/guides/mail-a-deal-that-went-quiet-or-closed-lost) covers the setup.
- **A renewal enters its window.** Map an account renewal date field, and the renewal trigger fires 90 days before that date.
- **Opportunity outcomes change.** Synced stage, amount, and close status feed measurement and campaign exits. They do not act as an arbitrary workflow engine.
- **A signal lives outside the synced fields.** Bring other custom data by [CSV](https://trysincerely.com/integrations/csv), or let Sincerely source dated account signals for plays such as [new executive](https://trysincerely.com/playbooks/new-executive).

The full list of ready-to-run plays is on the [campaigns page](https://trysincerely.com/campaigns). A default frequency cap of three pieces per contact per 30 days applies across all of them, so overlapping triggers cannot bury one person in mail.

## Example: mail a stalled opportunity

Launch a deal-quiet campaign with the [dark-accounts revival play](https://trysincerely.com/playbooks/dark-accounts) in mind and set how many days without a change counts as stalled. When an open opportunity crosses that line, Sincerely enrolls its eligible contacts, writes one piece from the recipient and account context, and holds each draft for review before it prints.

When the vendor confirms delivery, Sincerely creates a follow-up task due the next day. If a meeting, reply, or new opportunity is recorded before a later scheduled touch, the configured exit stops the enrollment. If the contact is [suppressed](https://trysincerely.com/guides/direct-mail-suppression), that decision overrides the Salesforce view and stops queued mail that has not reached the vendor.

## Setup, honestly

1. Connect Salesforce from your Sincerely workspace. You authorize with OAuth; no API keys to paste, nothing to install in your org.
2. Scope the sync. Choose all eligible contacts, compatible contact list views, contact owners, or the built-in country, state, title, and mailing-address filters. Preview the count before saving it.
3. Run the mailability audit. Sincerely checks every address and shows you what percentage of your audience can actually receive mail. This runs on the free audit plan, before you pay anything.
4. Build a campaign. Choose the trigger field or stage, the [format](https://trysincerely.com/formats), and the experiment design: primary outcome, measurement window, holdout percentage.
5. Choose whether eligible delivery events should also create Salesforce tasks, and preview the task shape before enabling writeback.
6. Approve drafts and launch. Pieces print through Sincerely's vetted mail partners once you approve them and pick a [plan](https://trysincerely.com/pricing).

Steps 1 through 5 work on the free audit plan with no card. Nothing mails until you choose a plan and a person approves the pieces, so connecting Salesforce commits you to nothing.

## Frequently asked questions

### Does it need a managed package in Salesforce?

No. You connect from inside Sincerely by authorizing with OAuth. Nothing is installed in your org and no API keys are pasted.

### What permissions does the connection ask for?

When you connect, you authorize with OAuth and then scope the audience sync yourself: the list views or owner filters Sincerely may read. Sincerely does not edit accounts, contacts, or opportunities. If an admin explicitly enables task writeback, it can create follow-up tasks for the campaigns and owners that admin chose.

### Can reps get tasks timed to delivery?

Yes. When an eligible print vendor confirms a piece was delivered, Sincerely creates a follow-up task due the next day. The task lives in Sincerely, and an admin can optionally write it back to Salesforce with a chosen owner, subject shape, and campaign scope.

### Can it run without Salesforce?

Yes. A [CSV import](https://trysincerely.com/integrations/csv) is a complete starting point, with delivery and engagement reporting honestly labeled, and you can connect Salesforce later without rebuilding anything. CSV-only lists cannot use CRM matchback, so their reports stay descriptive.

### How is ROI measured?

Against an account-level holdout, not with last-touch credit. Each campaign locks a primary outcome and measurement window at launch, and readouts report lift with confidence intervals. The [ROI measurement guide](https://trysincerely.com/guides/measure-direct-mail-roi) walks through the math.

### What does it cost to try?

Nothing until you mail. Connecting Salesforce, running the mailability audit, building the brand kit, and reading drafts all happen on the free audit plan with no card. Mailing requires a plan from the [pricing page](https://trysincerely.com/pricing).

## What this replaces

Without the integration, direct mail from Salesforce means exporting a report, cleaning addresses in a spreadsheet, uploading to a mail vendor, and setting yourself a calendar reminder to tell reps a week later. Each step leaks accuracy and time. The native sync kills the export step, the address cleanup, and the guessed follow-up timing in one move.

One honest limit: if your workflow lives in [Outreach](https://trysincerely.com/integrations/outreach), [Salesloft](https://trysincerely.com/integrations/salesloft), or [Clay](https://trysincerely.com/integrations/clay) rather than Salesforce itself, there is no native connector for those tools today. The honest path is to sync through Salesforce as the bridge, or use an [MCP agent](https://trysincerely.com/integrations/mcp-agents).

If your team runs on HubSpot instead, the [HubSpot integration](https://trysincerely.com/integrations/hubspot) offers the same audience and personalization path without CRM task writeback, and the [integrations overview](https://trysincerely.com/integrations) compares all four ways in. Your CRM already knows who to mail and when. This integration just lets it act on that.

## Related questions

- [Using Salesloft with Sincerely](https://trysincerely.com/integrations/salesloft): Sincerely has no native Salesloft integration. Your CRM is the bridge. Here is the honest setup, step by step, and where it falls short.
- [Using Zapier with Sincerely](https://trysincerely.com/integrations/zapier): There is no Sincerely Zapier app today. Here is the honest path, route data through Salesforce, HubSpot, or a CSV, and let Sincerely take it from there.
- [When should sales follow up after direct mail arrives?](https://trysincerely.com/guides/direct-mail-delivery-follow-up): Follow up the day after confirmed delivery. Reference the piece naturally, and treat postal tracking as evidence of arrival, not of reading.
- [How to manage direct mail suppression across campaigns](https://trysincerely.com/guides/direct-mail-suppression): Keep one durable do-not-mail decision per contact, check it at dispatch time, and cancel every queued piece that has not reached the print vendor.

---

Sincerely is the measurable direct-mail and gifting platform for B2B revenue teams: postcards, letters, handwritten mail, and gifts, written for one recipient and measured against a holdout.

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

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