--- title: "Using Salesloft with Sincerely" description: "Sincerely has no native Salesloft integration. Your CRM is the bridge. Here is the honest setup, step by step, and where it falls short." canonical: https://trysincerely.com/integrations/salesloft 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 Salesloft with Sincerely > Sincerely has no native Salesloft integration. Your CRM is the bridge. Here is the honest setup, step by step, and where it falls short. Source: https://trysincerely.com/integrations/salesloft There is no native Salesloft integration in Sincerely today. No connector, no Zapier app, no cadence step that fires a postcard. If a vendor page tells you otherwise, it is wrong. The honest path is the one Salesloft teams already run on: your CRM. Salesloft writes activity and field data to Salesforce or HubSpot, and Sincerely [syncs audiences from Salesforce](https://trysincerely.com/integrations/salesforce) and [HubSpot](https://trysincerely.com/integrations/hubspot) natively. The CRM is the bridge, and it works best with Salesforce, where a list view can carry the trigger. Both tools already treat the CRM as the source of truth. ## Prompt to paste into your agent ```text Add my Salesforce list view called Finished Enterprise outbound, which holds the contacts who finished my Salesloft cadence without replying, to the Sincerely sync scope. Check mailability for those contacts, and stop before approving or launching mail. ``` ## The working path 1. Confirm Salesloft syncs to your CRM. Salesloft syncs natively to both [Salesforce](https://salesloft.com/products/integrations-partnerships/salesforce/) and [HubSpot](https://marketplace.salesloft.com/partners/crm-sync-for-hubspot), carrying cadence activity, call dispositions, and person fields. That data is what Sincerely reads. One catch: fields like cadence name or step have no native CRM equivalent, so an admin has to create and map them first. 2. Define the trigger in the CRM, not in Salesloft. Pick a field that marks the moment mail should go out: a cadence completed with no reply, a stage change, a disposition like "no response after 6 touches". In Salesforce, build a Contact list view filtered on that field. The view needs a real filter, because one limited to your own records cannot be synced. 3. Add the list view to Sincerely's Salesforce sync scope. Sincerely syncs contacts, not leads, and resolves a mailing address for each account and checks its mailability before anything prints. Bad addresses drop out instead of bouncing back. With HubSpot, the sync reads every contact in the portal once a day and cannot filter on a cadence property, so export the finished-cadence contacts and [import them as a CSV](https://trysincerely.com/integrations/csv) instead. 4. Review and approve the pieces. Every piece is written for one recipient from CRM context and researched account facts, and a human approves before anything prints. 5. Read results in Sincerely. Eligible randomized campaigns lock an account-level holdout at launch and report lift with an interval; hand-picked follow-ups and objectives observed only through a mailed piece report descriptively. With Salesforce task writeback turned on, a confirmed delivery also creates a follow-up task 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. Handwritten mail has no delivery confirmation, and Canadian printed mail reports an estimate. No CRM in the middle? Export the people from Salesloft as a CSV and [import it directly](https://trysincerely.com/integrations/csv). You lose the automatic refresh, but a one-time send does not need one. There is a third path if your team uses AI agents: Sincerely is an MCP server, so a Claude Code or Cursor agent can build the audience and prepare the campaign from your instructions. Anything that prints still shows a human a confirmation card first. ## What this setup cannot do Be clear about the gaps, because they are real: - Mail is not a native cadence step. A rep cannot click "send postcard" inside Salesloft. The trigger lives in a Salesforce field and the list view built on it. - Timing is batch, not instant. Sincerely syncs Salesforce every 15 minutes, after Salesloft has written the field, not the second a Salesloft step completes. - HubSpot cannot carry the trigger. Its sync has no list or property filter, so a HubSpot team sends from CSV batches. - Send status does not appear on the Salesloft timeline unless your CRM activity sync carries it there. If you need mail as a literal in-cadence step with per-rep sending, a gifting platform is the better fit for that specific mechanic. Sendoso, Reachdesk, Alyce, and Postal all publish a direct Salesloft integration that adds sending as a cadence step. The tradeoff: those tools measure responses, not lift. Sincerely's whole point is the locked holdout and an honest answer on whether mail moved pipeline. ## Where mail fits in a Salesloft motion The highest-yield slot is the one email cannot fill: accounts that finished a cadence without a reply. Their inbox said no six times. A physical piece with a researched, account-specific message is a different channel with a different answer rate. The [outbound sequences guide](https://trysincerely.com/guides/direct-mail-in-outbound-sequences) covers sequencing in detail, including this exact play for accounts that went dark. Sincerely publishes the package and format terms active for the current deployment on the [pricing page](https://trysincerely.com/pricing). There may eventually be a native Salesloft integration, but there is not one now. Until that changes, the CRM connection is the supported route. It keeps one authoritative copy of the account and avoids a second sync whose only job would be to repeat fields Salesforce or HubSpot already carries. For most teams, that is enough: Salesloft records the activity, the CRM holds the account state, and Sincerely decides what is ready for the mailbox. ## Related questions - [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. - [Using Outreach with Sincerely](https://trysincerely.com/integrations/outreach): Sincerely has no native Outreach integration. Here is the honest way to add direct mail to your Outreach sequences through your shared CRM. --- 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