Data in, data out.
Webhooks, SFTP, CRM, Stats API.
Four real integration surfaces: bidirectional webhook automation for data and lead events; SFTP file exchange for bulk list ingest and exports; native HubSpot/Salesforce sync for lead delivery and CRM-triggered campaigns; and a Stats API for pushing campaign analytics into your BI tools or data warehouse. The platform itself is operated in the UI — campaigns, creative, and audience configuration happen there, not via a programmatic API. SOC 2 Type II certified infrastructure throughout.
Five steps. Managed setup. Production-ready.
- 01
Push lists in via SFTP, webhook, or CRM sync
Customer lists, target audiences, suppression rules, and trigger events ingest through three real surfaces: SFTP file transfer (PGP-supported, bidirectional), inbound webhook automation (signed payloads, retry-on-failure), or live sync from HubSpot, Salesforce, and major CRMs. Set the schedule once; subsequent campaigns inherit the same data flow.
- 02
Run the campaign in the platform
Campaign creation, creative production, postal scheduling, and channel orchestration happen in the DirectMail.io platform UI — not via a programmatic platform API. Your team operates the platform; the data flows in and out of it automatically through the integration surfaces.
- 03
Responses captured across every channel
QR scans, landing-page submissions, IVR calls, SMS replies, and conversion events capture on every campaign with full source attribution. Each response carries the original campaign and recipient identifier — no manual stitching required.
- 04
Leads delivered out via CRM, webhook, or SFTP
Captured leads route out through three channels: native HubSpot/Salesforce contact + activity sync, outbound webhooks to any endpoint with signed payloads, or scheduled SFTP exports. New contacts route to the right owner; existing contacts update with the new touch.
- 05
Stats pushed into your BI / data warehouse
The Stats API pushes campaign statistics (sends, scans, responses, conversions, attribution) into Snowflake, BigQuery, Redshift, Looker, Tableau, or custom analytics systems. Outbound stats only; configure the destination during onboarding.
Why managed integration beats DIY integration for marketing teams.
Most direct mail vendors hand you an API and say "build the integration yourself." That works if you have an engineering team with capacity for the build, the testing, the maintenance, and the on-call when something breaks at 2 AM. For most marketing organizations, the engineering capacity isn’t there — and the integration sits half-built indefinitely, with manual list exports filling the gap.
DirectMail.io ships the integration during onboarding. The HubSpot and Salesforce paths are pre-built; your team confirms the field mappings and lead routing. Custom fields, custom owners, custom workflows configure inside the standard integration — no engineering cycles required on your side. The integration runs as managed infrastructure, monitored alongside the rest of the platform.
The SOC 2 Type II certification covers the full integration layer. Customer data exchanged with HubSpot, Salesforce, or via SFTP inherits the same access control, encryption, and audit logging posture as the rest of the platform. For enterprise procurement, the certification removes the integration-security-review block that typically delays vendor approval by months.
Where the CRM integration earns its keep.
-
HubSpot-triggered direct mail campaigns
Lifecycle stages in HubSpot (lead-stage changes, deal milestones, list membership) trigger direct mail launches automatically. Onboarding mail, re-engagement, win-back campaigns fire from the CRM without manual handoff.
-
Salesforce contact + opportunity sync
New mail responses create or update Salesforce contacts with full campaign attribution. Opportunity records receive activity history tied back to the originating mail drop, closing the attribution loop for the sales team.
-
Recurring data exchange via SFTP
For enterprise customers with legacy data systems, scheduled SFTP exchange handles list ingest and lead export. Standard format mappings handle most use cases; custom mappings configure during onboarding.
-
Multi-tool marketing automation
Marketo, Eloqua, or HubSpot Marketing Hub orchestrate multi-channel sequences where direct mail is one of several touches. The marketing automation tool drives audience selection; DirectMail.io handles production, send, and response capture; leads flow back through the same channel.
Questions teams ask before deploying.
Short answers. For implementation specifics on field mappings, custom workflows, or enterprise SOC 2 review documentation, book a demo.
-
Which CRMs does DirectMail.io integrate with?
HubSpot and Salesforce have native, supported integrations for lead delivery and contact sync. Other CRMs — Microsoft Dynamics, Zoho, custom systems — integrate via SFTP file exchange or standard webhook delivery to your endpoint. Most major CRMs are supported out of the box; less common systems handle through the SFTP path.
-
Do I need a developer to set this up?
No. The integration ships during managed onboarding — DirectMail.io handles the configuration, the field mapping, and the testing. Your team confirms the CRM fields and lead-routing rules. Engineering involvement on your side is typically zero.
-
How do response events get into my CRM?
Each direct mail recipient gets a tracked landing page, QR code, or response channel. When they respond — visit, submit, scan, call — the event captures with the original mail campaign attribution and writes the lead into your CRM. New leads create as contacts; existing contacts add an activity record with the campaign source.
-
Can I trigger campaigns from my CRM (e.g. when a Salesforce opportunity reaches a stage)?
Yes — for supported integrations. List membership changes in HubSpot or Salesforce can route into a campaign trigger so mail launches automatically when a contact enters or exits a segment. The campaign itself is configured in the DirectMail.io platform; CRM events drive the audience.
-
How does this compare to building your own integration against a direct mail API?
DirectMail.io is a managed platform, not an API-first developer tool like Lob or PostGrid. If you want to build your own integration layer in code, those vendors are designed for that. DirectMail.io is designed for marketing teams that want the integration to ship without engineering involvement — your team works in the platform UI; the data exchange runs in the background.
-
Is the platform SOC 2 Type II certified — and how does that affect CRM data flow?
Yes, SOC 2 Type II certified. The certification covers the full platform infrastructure including the CRM integration layer. Customer data exchanged with HubSpot, Salesforce, or via SFTP inherits the same access control, encryption, and audit logging posture. The certification report is available under standard NDA for vendor security review.
-
What if I just want to push lists in but pull leads out separately?
That works. The inbound and outbound paths are independent — you can push lists in via SFTP on a schedule and pull leads out via CRM sync, or any combination. Most programs run both directions; some run only one.
-
What is the Stats API?
A push-only integration that delivers campaign statistics — sends, scans, responses, conversions, attribution data — into your analytics systems (BI tools like Looker/Tableau, data warehouses like Snowflake/BigQuery/Redshift, or custom dashboards). The Stats API is scoped specifically to outbound analytics push. It is not a programmatic platform-control API — you cannot create campaigns, manage clients, or upload creative through it. Configure the destination during managed onboarding.
-
How do webhooks work in both directions?
Outbound webhooks fire from the platform on lead capture, response events, and lifecycle moments — payloads are signed for verification and retry on failure for 24-48 hours. Inbound webhooks let your systems trigger actions in the platform (list refresh, campaign launch, suppression updates) by posting to a per-account endpoint. Both directions log to the webhook delivery dashboard for audit and replay.
See your CRM integrated with a live campaign.
Bring a HubSpot or Salesforce instance and a list of fields you want mapped. We’ll walk through the integration setup, configure lead routing, and demo the round-trip — in 30 minutes.