- Published on
Direct mail software that actually works with Salesforce and HubSpot
- Authors
- Name
- Direct Mail Growth
For a team using both Salesforce and HubSpot, Sendoso has the broadest documented mix of rep sending, workflows, gifts, and mail. If the job is mostly automated postcards and letters, I would demo Postalytics first. Lob belongs on a different shortlist: it suits a team that wants an API and is prepared to own the integration.
That is the short answer. The useful answer starts with one send, because an integrations logo cannot tell you whether a rep gets a button, an admin gets a workflow action, or an engineer gets a pile of API documentation.
Which direct mail platform works best with Salesforce and HubSpot?
Sendoso is the best all-round fit when sellers work in both CRMs and the program includes gifts or swag. Postalytics is the cleaner first look for print-only automation, while Postal and Reachdesk make more sense when gifting and offline engagement carry more of the brief.
| If this is the job | Start with | Why |
|---|---|---|
| Reps send mail, gifts, and swag from Salesforce and HubSpot | Sendoso | Broad in-CRM sending and workflow coverage |
| Marketing automates postcards and letters | Postalytics | Specific Flow, workflow, delivery, and response documentation |
| The team wants personalized mail with account holdouts | Sincerely | CRM data, hosted response pages, and lift measurement |
| A global team sends gifts and event items | Reachdesk | Regional fulfillment plus Salesforce and HubSpot events |
| Salesforce is the main operating system | PFL | Native Sales Cloud and Marketing Cloud paths |
| HubSpot needs transactional print actions | PostGrid | Contact actions, workflows, and test API keys |
| Engineers want to build the workflow | Lob | API, webhooks, test mode, and address tools |
Picture the smallest version first. Maria has a Contact open in Salesforce and wants to mail one note. No copying the address. No second login. She picks an approved piece, sends it, and later sees a useful status on the same record. Sendoso and Postal are built for that sort of rep action. Postalytics leans more toward admin-built campaigns and automation.
Now change the job. Marketing needs 400 renewal letters to leave from a HubSpot workflow next Tuesday. Suddenly the unlovely details matter: suppression fields, owner changes, budget limits, bad addresses, and a retry that must not order another 400 letters. This is where Postalytics' workflow and mail-event documentation becomes attractive.
If the trigger itself is still unsettled, map that first. This CRM-triggered direct mail guide covers the audience rules, suppressions, and stop conditions that belong outside the vendor demo.
What does “integrates with Salesforce” actually mean?
It can mean four very different things: an in-record button, a Flow action, a managed package, or an API your team must wire up. Ask the vendor to show the exact path you would use. “Native” is not a sufficient answer either.
| Integration path | What the user sees | Who owns the work |
|---|---|---|
| Record button or CRM card | A rep sends without leaving the record | Revenue operations and the vendor |
| Flow or workflow action | An admin adds mail to existing automation | Revenue operations or marketing operations |
| Managed package | New components, fields, permissions, and objects | Salesforce administration |
| Webhook or middleware | One system calls another when an event occurs | Operations or engineering |
| Direct API | Your code creates orders and handles responses | Engineering |
A button solves a rep problem. A Flow action solves an automation problem. An API gives you control, then hands you retries, duplicate prevention, monitoring, and writeback design. Those are not three versions of the same purchase.
I would also ask where the connection lives. Reachdesk's HubSpot path uses a Marketplace app plus a webhook workflow. Lob can work through API calls, webhooks, or middleware. Both may be perfectly sensible. Neither should be described as a packaged HubSpot card if that is not what the team is buying.
What should direct mail software write back to the CRM?
At minimum, write back the order ID, current mail status, failure reason, cost, and response event on a record a workflow can read. A link to the vendor dashboard is not enough if reps and reports still need the actual status.
| Event | Why it belongs in the CRM | A useful field or record |
|---|---|---|
| Send requested | Shows who or what started the order | Campaign member, task, or mail activity |
| Address rejected | Stops silent failures and supports correction | Failure status plus reason |
| In production | Separates an accepted order from a mailed piece | Production status and date |
| Shipped or mailed | Starts the follow-up clock | Mail date and carrier event |
| Delivered | Helps a rep time outreach | Delivery date and status |
| QR or URL response | Records direct response without calling it revenue | Response event and timestamp |
| Cost | Lets the team calculate campaign economics | Piece cost and campaign total |
Watch the phrase “activity sync.” It might mean a Salesforce Task, a HubSpot timeline event, a mapped field, or a small card that only links elsewhere. Ask for the object and field names. Write them down. They decide whether the integration saves work or leaves RevOps another tab to check every morning.
Delivery is not a reply. A scan is a response, but it does not prove that mail caused the opportunity. Keep the raw events and apply the attribution rule later. Our direct mail ROI guide explains the difference between response, matchback, influenced pipeline, and lift.
How do the main platforms compare?
Sendoso and Postal offer the clearest rep-led experience across Salesforce and HubSpot. Postalytics is stronger for automated print campaigns. Reachdesk is a global gifting option, PFL is Salesforce-first, PostGrid gives HubSpot users transactional print actions, and Lob gives developers the most room to build.
| Tool | Salesforce path | HubSpot path | Practical caution |
|---|---|---|---|
| Sendoso | Buttons, campaigns, automation, mapped activity | App card, workflows, events, optional fields | Broad access and setup need an owner |
| Sincerely | CRM data and triggered sends | CRM data and triggered sends | Marketplace listings and in-record actions were not public |
| Postalytics | Lists, Campaigns, outbound messages, Flows | Certified app, lists, workflows, mail events | Salesforce integration sits on Pro |
| Postal | Managed package and record triggers | CRM card and workflow action | Direct mail and CRM features require its main paid plan |
| Reachdesk | OAuth, campaign triggers, browser extension | Marketplace app, webhook workflow, extension | Confirm event timing and retry handling |
| PFL | Sales Cloud components and Journey Builder | No current Marketplace app found | Best fit is Salesforce-first |
| PostGrid | Direct connector or API | Certified app, record actions, workflows | Confirm Salesforce writeback fields in the demo |
| Lob | External Services, third-party app, or API | API, webhooks, or middleware | Your team owns more of the plumbing |
Prices and packaging move. When I checked on August 28, 2026, Sincerely published a $199 pilot and monthly plans from $250 to $4,500. Reachdesk started at $20,000 a year. Lob published plans from $0 through $550 before Enterprise. Several others routed buyers to sales, so ask for the platform fee, piece price, storage, pick-and-pack, shipping, and unused-balance rules in one quote.
How should I test a CRM direct mail integration before signing?
Use one Contact, one Lead, and one Opportunity in a non-production path, then make the records misbehave. Change the owner after approval. Fail an address. Pause the connector. Deliver the same event twice. A clean happy-path demo proves very little.
Here is the test I would run:
- Have a rep send one approved piece from the CRM.
- Trigger a second piece from a Flow or workflow.
- Show every field, Task, event, or Campaign status that comes back.
- Remove the rep's permission and try again.
- Reassign the record between approval and fulfillment.
- Use a bad address, correct it, and replay the failed order.
- Send the same webhook twice and confirm that only one order exists.
- Export campaign cost and response data without opening the vendor dashboard.
One awkward record will teach you more than another catalog tour. If the failure only appears in the vendor's dashboard, somebody has to own that queue. Fine, perhaps, but count the work honestly.
Frequently asked questions
What direct mail software integrates with Salesforce?
Sendoso, Postalytics, Postal, Reachdesk, PFL, PostGrid, and Lob all publish a Salesforce path. The paths differ. Some give reps a button, some give admins a Flow action, and some give engineers an API. Make the vendor show your trigger and writeback on a real record.
Can HubSpot workflows trigger direct mail?
Yes. Postalytics, Sendoso, Postal, PostGrid, and Reachdesk document HubSpot workflow triggers. The useful follow-up question is what comes back after the send. Ask whether a workflow can read the return status or whether it only appears on a timeline card.
Does a Salesforce integration automatically respect territories and record ownership?
No. Your Flow, permissions, ownership fields, campaign membership, and vendor user mapping must enforce those rules. A customer anniversary mailer may follow Account owner. A gift for an open deal may need Opportunity owner plus an approval limit. Decide before the first order.
Should RevOps choose a native app or a direct mail API?
Choose the app when reps need an in-record action and admins want packaged fields and permissions. Choose the API when the process is unusual enough to justify engineering ownership. The API is not the quick route. It is the route where your team owns retries, duplicate prevention, monitoring, and writeback.