Direct mail software that actually works with Salesforce and HubSpot

The best direct mail software for Salesforce is the one that can start a send from a Salesforce record or Flow, write delivery and response events back to the right record, and let an admin test the whole path before reps touch it. For teams that also run HubSpot, Sendoso has the strongest documented coverage across both CRMs. Postalytics is the cleaner fit when the job is mainly automated postcards and letters rather than gifts.

Don't buy from an integrations logo page. A useful Salesforce or HubSpot connection should preserve the CRM as the operating system: reps send where they already work, workflows use real record data, statuses return to the record, and existing ownership rules decide who can act. Marketplace listings help, but the listing's shared-data and workflow sections matter more than the badge.

How I ranked direct mail software for Salesforce and HubSpot

This ranking favors RevOps control over catalog size. I weighted record or workflow triggers, useful writeback, in-CRM rep sends, permissions, and testing.

That last item gets ignored. It shouldn't. A direct mail action creates a real order, so a bad workflow isn't merely an annoying email. It spends money and puts an object in the mail.

I checked Salesforce AppExchange and the HubSpot App Marketplace, then compared the listings with vendor documentation. "Native" below means a first-party CRM app or connector. A webhook, Zapier recipe, browser extension, or API can work well, but your team owns more plumbing.

Ownership and territory deserve a similar caveat. None of these tools can repair vague routing. The safe pattern is to qualify the send in Salesforce Flow or a HubSpot workflow using owner, territory, lifecycle stage, suppression, and prior-send fields before the mail action fires. Our guide to CRM-triggered direct mail covers that campaign design in more depth.

The shortlist and what writes back to the CRM

"Not publicly documented" is deliberate. It means I couldn't find the behavior in the vendor's current listing or documentation, not that the feature is impossible.

The table exposes the thin spot in most search results: "integrates with Salesforce" might mean a rep button, a managed package, an OAuth data pull, or instructions for calling an API. Those aren't equivalent projects.

1. Sendoso: best overall for reps working in both CRMs

Sendoso is the strongest fit when sellers need gifts, branded items, handwritten notes, and direct mail inside a governed revenue workflow. Its current HubSpot Marketplace app supports automated workflows and sends events back to HubSpot. Sendoso's documentation also covers an app card, optional contact-field writeback, ROI reporting, and Salesforce buttons, activity mapping, campaigns, and automated sends.

That is broad coverage. It also creates admin work. Salesforce access touches Contacts, Leads, Accounts, Campaigns, Campaign Members, Tasks, and optionally Opportunities. HubSpot needs a super admin for the connection, and mapped writeback fields are optional. Decide who owns those fields before installation.

Sendoso publishes plan names and allowances, but not dollar prices. On August 28, 2026, its pricing page routed each plan to sales. The product is built for managed sending programs, so a small team wanting a few postcard workflows may find the operating model heavier than it needs.

2. Sincerely: best for CRM-personalized pieces with hosted response pages

Sincerely pulls Salesforce, HubSpot, or CSV fields into the piece itself, so a letter references the account rather than just the first name. Each piece leaves with its own QR code and short URL, resolving to hosted landing pages that can sit on your own link domain. Postcards, letters, handwritten notes, and gifts all run through the same workflow.

On the measurement side it uses account-level holdouts rather than treating every response as incremental, which is the question worth putting to every vendor on this list.

That measurement choice is the reason for the ranking. A QR scan is useful evidence, but it doesn't tell you whether the same person would have converted without mail. Teams buying around incrementality should ask every vendor how it creates control groups, keeps them out of downstream workflows, and reports the difference.

Pricing is published rather than quoted: a $199 one-time pilot, then monthly plans from $250 to $4,500 with 20 seats included at every tier. I could not confirm a Salesforce AppExchange or HubSpot Marketplace listing, sandbox instructions, or an in-record rep send action, so put those on your demo list.

3. Postalytics: best for automated postcards and letters

Postalytics has unusually specific integration documentation. In Salesforce it can import Contacts, Leads, Accounts, saved views, and Campaign members; Flows or outbound messages can trigger letters, postcards, and self-mailers. Delivery and online-response statuses return to Leads or Contacts.

Its HubSpot Certified App pulls lists with personalization fields, triggers mail from workflows, and posts mail events back to HubSpot. That's a real application, not a Zapier shortcut. Postalytics also documents a separate Zapier route for CRMs such as Pipedrive and Microsoft Dynamics, which is exactly the distinction buyers need.

There is a free account with per-piece charges. Full Salesforce integration sits on the Pro plan, while HubSpot support spans the product's listed plans. Postalytics didn't publish a current Pro subscription price on the pages I could verify on August 28, 2026, so get the platform fee and mail-piece schedule in writing.

4. Postal: best for an offline engagement program

Postal combines gifts, swag, direct mail, and event experiences. Salesforce sends can trigger from Opportunities, Tasks, or Events. Its managed package maps activity back to Leads, Contacts, Accounts, Opportunities, and Campaigns, with custom fields for cost and touch counts. Delivered and accepted events create Tasks.

The HubSpot Marketplace app supplies a CRM card for individual sends and an action for workflows. Postal's help center says activity syncs at the contact level and the connector runs on a schedule, so don't promise instant status to reps without testing the delay.

Postal's small-team plans aren't the relevant comparison because its help center says direct mail and CRM integrations require First Class. That plan was quote-only when checked on August 28, 2026. Good for a central offline program. Less so for print mail alone.

5. Reachdesk: best for global gifting with clear CRM events

Reachdesk is a global gifting and swag platform with mature Salesforce and HubSpot instructions. Salesforce users can launch manual sends through a browser extension, automate from campaign membership or record criteria, and map physical-gift statuses such as processed, shipped, returned, and delivered to Campaign Member statuses. Completed Tasks and optional cost fields provide writeback outside Campaigns.

In HubSpot, Reachdesk uses a Marketplace app plus a webhook workflow. It writes a new custom event to the Contact timeline when a send starts and as its status changes. The existing standard Contact properties remain untouched.

Reachdesk documents Salesforce sandbox OAuth. Its pricing page started at $20,000 per year on August 28, 2026, with final cost based on users, sends, regions, and logistics. Pick it when global fulfillment and recipient choice justify a program budget.

6. PFL: best for Salesforce-first direct mail operations

PFL owns print, fulfillment, and logistics as well as the software layer. It documents native components for Salesforce Sales Cloud and a Journey Builder activity for Marketing Cloud. Reps can send from Salesforce records, while campaigns can trigger from stages or field values and return delivery and attribution details.

I found current Salesforce product documentation and AppExchange-hosted PFL materials, but no current PFL app in HubSpot's Marketplace. For a company that runs Salesforce as CRM and HubSpot as the marketing layer, that gap can force a custom handoff or a different vendor. PFL didn't publish platform pricing when checked on August 28, 2026, so buyers need a quote.

This is a sensible enterprise choice when physical production is part of the buying decision, especially for dimensional pieces. If your program is account based, map the integration after you settle the ABM direct mail playbook, not before.

7. PostGrid: best for HubSpot plus transactional print mail

PostGrid prints letters, postcards, checks, and self-mailers through a dashboard and API. Its HubSpot Certified App offers Contact record buttons, workflow actions, bulk mail, merge fields, and mail status reporting. The Marketplace listing says the integration requires a Growth or Enterprise subscription.

PostGrid's own pricing page listed a $0 monthly Starter tier for up to 500 mailings per month on August 28, 2026, but native integrations sit in Enterprise, which is quote-only. Don't mistake API trial access for the price of the CRM deployment.

The Salesforce product page describes record sends and workflow automation, though I couldn't verify a current AppExchange listing or exact writeback fields. Test and live API keys give technical teams a trial path. Before launch, set address verification rules in the CRM.

8. Lob: best for teams that want to build the integration

Lob is a print-and-mail API for postcards, letters, self-mailers, and checks, with address verification and webhooks. For Salesforce, Lob documents dashboard authentication, External Services for advanced teams, and a third-party point-and-click app. Triggered mail is real, but this is closer to an integration toolkit than a rep-first managed package.

I found no first-party Lob app in HubSpot's Marketplace. HubSpot teams can call Lob through custom code, webhooks, middleware, or their own service. Then engineering owns matching, retries, idempotency, writeback, and the question everyone forgets: what happens when an Opportunity has three Contacts?

Lob's published monthly plans ran from $0 through $550 before custom Enterprise pricing when checked on August 28, 2026, and each mailpiece costs extra. Test mode creates digital proofs without mailing anything. For an engineering-led team, that control can be the point.

Alyce is now a legacy consideration

Alyce was a recipient-first gifting platform. Sendoso acquired it through an asset purchase agreement in 2024 and has since described customers moving from Alyce onto Sendoso. It shouldn't appear as a separate new-buy option in a 2026 shortlist, and there is no current standalone price to compare.

Existing customers still need a migration plan. Inventory old campaign IDs, statuses, custom fields, permissions, and attribution reports before replacing the connector. Preserve the raw history first. CRM cleanup can come later.

What to test before signing

Start with one Contact, one Lead, and one Opportunity in a non-production path. Then make the vendor prove the awkward cases. A rep shouldn't be able to mail a suppressed Contact. A reassigned account shouldn't debit the former owner's budget. A retry shouldn't create a second order.

I use these buying questions:

• Show the exact Salesforce objects or HubSpot properties you read and write.
• Trigger one send from a workflow, then show every status that returns.
• Have a rep send from the CRM while an admin restricts the catalog and budget.
• Change the record owner between approval and fulfillment. Which rule wins?
• Fail an address, pause the connector, and replay an event. What duplicates?
• Run the same proof in a sandbox or test account without producing mail.

Also settle attribution before launch. Delivery isn't revenue, and a QR scan isn't necessarily incremental. Use opportunity influence as a diagnostic, then apply holdouts or a careful direct mail ROI method when you need a causal answer.

Frequently asked questions

What direct mail software integrates with Salesforce?

Sendoso, Postalytics, Postal, Reachdesk, PFL, PostGrid, and Lob all publish Salesforce paths, but they don't offer the same kind of connection. Sendoso and PFL suit rep-led workflows. Postalytics is strong for mail automation, while Lob is the buildable API route. Ask to see the trigger and writeback live. Logos prove very little.

Can HubSpot workflows trigger direct mail?

Yes. Postalytics, Sendoso, Postal, PostGrid, and Reachdesk all document HubSpot workflow triggers. Reachdesk's path uses a webhook, which is still workable but deserves retry and error monitoring. I've stopped accepting "works with workflows" as a complete demo. Make the vendor show what comes back after the piece ships.

Does a Salesforce integration automatically respect territories and record ownership?

No. Your Salesforce Flow, permissions, campaign membership, and vendor user mapping have to enforce those rules. Depends on the motion, too. A customer anniversary mailer may key off Account owner, while an open deal gift should probably follow Opportunity owner and an approval limit.

Should RevOps choose a native app or a direct mail API?

Choose the app when reps need an in-record button and admins want packaged fields, permissions, and reports. Choose the API when your process is unusual enough to justify engineering ownership. The API isn't a shortcut. You inherit retries, duplicate prevention, monitoring, and writeback design, which is fine if that's what you meant to buy.