--- title: "Using Outreach with Sincerely" description: "Sincerely has no native Outreach integration. Here is the honest way to add direct mail to your Outreach sequences through your shared CRM." canonical: https://trysincerely.com/integrations/outreach 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. # Using Outreach with Sincerely > Sincerely has no native Outreach integration. Here is the honest way to add direct mail to your Outreach sequences through your shared CRM. Source: https://trysincerely.com/integrations/outreach Sincerely has no native Outreach integration today. There is no connector, no app in the Outreach marketplace, and no direct API sync between the two tools. What works instead: both tools already read and write the same CRM, so you use Salesforce as the bridge. Outreach marks where a prospect is in the sequence, a Salesforce list view filters on that field, and Sincerely syncs the view and mails at the right stage. It takes about an hour to set up and it holds up in production. HubSpot is a weaker bridge, covered below. ## Prompt to paste into your agent ```text Add my Salesforce list view called Finished Enterprise outbound, which holds the contacts who finished my Outreach sequence without replying, to the Sincerely sync scope. Check mailability for those contacts, and stop before approving or launching mail. ``` ## Why the CRM bridge works Outreach syncs sequence state to your CRM. Sincerely syncs contacts from [Salesforce](https://trysincerely.com/integrations/salesforce), and its sync scope can be a Contact list view, including one filtered on a custom field. That shared record is the integration. You never export CSVs on a schedule or copy lists by hand. You pick a field, build a list view on it, and both tools do what they already do. [HubSpot](https://trysincerely.com/integrations/hubspot) works differently. The HubSpot sync reads every contact in the portal once a day and has no list or property filter, so a sequence field in HubSpot cannot narrow the audience. With HubSpot, export the contacts who finished the sequence and [import them as a CSV](https://trysincerely.com/integrations/csv) for each batch. The one thing you give up is real-time triggering. Outreach pushes to Salesforce on its own schedule, and Sincerely syncs Salesforce every 15 minutes. For mail this does not matter. A postcard takes 3 to 5 business days to arrive. A one-hour trigger delay is noise. ## The setup, step by step 1. Connect Sincerely to the same Salesforce org Outreach uses. This works on the free audit plan, before you pick a paid plan. Sincerely syncs contacts, not leads, so the sequence fields need to live on the contact. 2. In Outreach, confirm sequence state syncs to a CRM field. Outreach [pushes sequence engagement data](https://support.outreach.io/hc/en-us/articles/221395027-Syncing-Sequence-Engagement-Status-Data-to-a-CRM) to mapped contact or lead fields, including current sequence name, step number, and status. An admin has to create those CRM fields and map them with "update out" enabled, so check that before you build the audience. If a prospect sits in two sequences at once, Outreach reports only the most recent. 3. In Salesforce, create a Contact list view filtered on that field. For example: contacts where the sequence step equals 3, or where a custom "send mail" checkbox is true. Add the view to Sincerely's Salesforce sync scope. The view needs a real filter, because one limited to your own records cannot be synced. 4. Choose the review mode. Sincerely writes each piece for the specific recipient from CRM context. Review every draft, or let clean copy auto-approve after the first ten researched pieces pass review. 5. Launch a campaign that enrolls contacts as they join the synced audience. When a prospect hits the trigger stage, they enter the list view, reach Sincerely on the next sync, and the piece goes out after the campaign's chosen review. The checkbox variant in step 3 is the most flexible. Add a manual step to your Outreach sequence that says "flag for mail". The rep ticks the box in Salesforce, Sincerely picks it up. You trade automation for control, which is often the right trade on expensive accounts. ## Timing the call task to delivery The whole point of mail in a sequence is the follow-up call: "Did my note reach you?" is a real opener. Postcards and letters typically land in 3 to 5 business days after the print date. So structure the sequence like this: - Step N: mail triggers (the CRM field flips, Sincerely sends after the chosen review). - Step N + 1: a call task with a 5 to 7 business day delay. - Step N + 2: an email that references the piece, a day or two after the call. With Salesforce task writeback turned on, a confirmed delivery creates a follow-up task in Salesforce under the configured owner and campaign scope. Standard printed United States postcards and letters return automatic postal events. Gifts carry carrier tracking and can receive delivery confirmation from the fulfillment team, which also raises the task. Handwritten mail has no delivery confirmation, and Canadian printed mail reports an estimate. For a deeper pattern, read [direct mail in outbound sequences](https://trysincerely.com/guides/direct-mail-in-outbound-sequences). ## Where each tool should win Let Outreach keep the digital sequence. It already handles email steps, call tasks, LinkedIn touches, and sequence analytics. Rebuilding those jobs in Sincerely would make both tools harder to run. Move to Sincerely when the sequence reaches the mailbox. Sincerely researches the account, writes for one recipient, checks the business address against the destination country's postal data, and measures eligible randomized campaigns against an account-level holdout. Outreach decides when the step is due. Sincerely handles what gets printed and what can honestly be learned from it. For a tighter loop than watching a shared field, an MCP agent can build the Sincerely audience, draft pieces, and prepare the campaign. Preparation isn't permission to print. A person still confirms the exact send or launch. See [MCP agents](https://trysincerely.com/integrations/mcp-agents). There is no native connector hiding behind the diagram. Today, the practical bridge is one shared Salesforce field and a list view on it. ## 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. - [Salesforce direct mail: automate mail from your CRM](https://trysincerely.com/integrations/salesforce): Sync accounts and contacts from Salesforce, write each piece from CRM context, approve before anything prints, and time rep follow-up to confirmed delivery. - [HubSpot direct mail: automate mail from your CRM](https://trysincerely.com/integrations/hubspot): Sync contacts, companies, and properties from HubSpot, write each piece from CRM context, approve before anything prints, and time follow-up to delivery. --- 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