See It in One Demo
Integrations

Managed integration.
Not an engineering project.

DirectMail.io is a managed platform — campaigns run in the UI, not via a public API. What is automated: the data exchange. Lead lists ingest from your CRM or via SFTP; mail-campaign responses (form submissions, QR scans, IVR calls) flow back into HubSpot or Salesforce as contacts with full source attribution. The integration ships during onboarding, not as a build for your engineering team. SOC 2 Type II certified infrastructure throughout.

CRM Integration feature page →
Integration surfaces

Four ways your systems connect.

CRM Integration

HubSpot, Salesforce — native.

Leads, responses, and campaign attribution flow into HubSpot or Salesforce with custom field mappings and lead routing. Trigger campaigns from CRM list membership changes. No code required on your side — the integration ships during managed onboarding.

SFTP Automation

Bidirectional. PGP supported.

Per-account SFTP credentials with key-pair authentication. Inbound: list ingest, suppression updates, data refresh. Outbound: scheduled response exports, attribution data, campaign reporting. CSV, TSV, JSON Lines, Parquet, and Excel formats supported.

Webhook Automation

Bidirectional. Signed payloads.

Webhooks IN: receive list-update triggers, campaign-launch signals, or suppression events from your systems. Webhooks OUT: lead capture, response events, and lifecycle data delivered to your endpoint with signed payloads. Retry-on-failure delivery and audit logging on every event.

Stats API

Outbound. BI / data warehouse push.

Push campaign statistics — sends, scans, responses, conversions, attribution — into separate analytics systems (Snowflake, BigQuery, Redshift, Looker, Tableau, or custom BI). Outbound stats only; this is not a platform-control API. Configure the destination during onboarding.

When we’re a fit — and when we’re not

Honest about what we are.

You’re a fit if: you have a marketing team that wants to run direct mail as a managed channel, with leads and responses flowing into your CRM automatically. You don’t want an engineering project to ship the integration; you want it operational on day one. You’re comfortable running campaigns in a platform UI.

You’re not a fit if: you want to programmatically create campaigns, push creative per channel, or manage clients and templates through an API. We don’t expose that. Vendors like Lob and PostGrid are designed for code-first integration — that’s a different product motion. We’re a managed platform with data integration, not a developer tool with an admin UI.

Integrations FAQ

Questions integrators ask first.

Short answers.

  • Does DirectMail.io have a public REST API for managing campaigns?

    No. DirectMail.io is a managed platform — campaigns, creative, and audience configuration happen in the platform UI, not via a public REST API. If you need an API-first developer tool to programmatically create direct mail at the per-record level, vendors like Lob and PostGrid are designed for that. DirectMail.io is designed for marketing teams that want the platform to be operated by a human, with the data exchange (lead inflow, lead delivery, CRM integration) handled automatically.

  • How do I get my CRM connected?

    CRM integration ships during managed onboarding. HubSpot and Salesforce have native, pre-built integration paths; configuration is field mapping, lead routing, and confirmation testing — typically a half-day of joint setup. Other CRMs route through SFTP or webhook delivery. See the CRM Integration feature page for the full setup flow.

  • Can I push lists into DirectMail.io from my own systems?

    Yes. List ingest runs via CRM sync (HubSpot, Salesforce) or SFTP file transfer. The platform ingests on the schedule you set; subsequent campaigns inherit the same data flow. PGP encryption supported for SFTP. The standard ingest formats handle most use cases; custom formats configure during onboarding.

  • How do I get response events out of the platform into my CRM or data warehouse?

    For CRM destinations (HubSpot, Salesforce): native integration writes leads and response events as contacts and activities with full source attribution. For data warehouse destinations (Snowflake, BigQuery, Redshift): SFTP scheduled exports, webhook delivery to your endpoint, or the Stats API for push-based analytics. The setup configures during onboarding alongside the inbound path.

  • What does the Stats API do?

    The Stats API is an outbound integration that pushes campaign statistics — sends, scans, responses, conversions, attribution data — into analytics systems on your side (BI tools like Looker or Tableau, data warehouses like Snowflake/BigQuery/Redshift, or custom dashboards). It is scoped specifically to stats and analytics push. It is not a platform-control API — you cannot create campaigns, clients, or upload creative through it. Configure the destination during onboarding.

  • Is the platform SOC 2 Type II certified?

    Yes. The full platform infrastructure including the CRM integration layer and SFTP exchange is covered by the SOC 2 Type II certification. The attestation report is available under NDA through security@directmail.io. Data exchanged with HubSpot, Salesforce, or via SFTP inherits the same access control, encryption, and audit logging posture as the rest of the platform.

  • What if I want to build a custom integration that is not HubSpot, Salesforce, or SFTP?

    Custom integration scoping happens during onboarding. Implementation engineering evaluates your source or destination system and use case — typical setup takes one to three weeks depending on complexity. The custom integration ships as managed infrastructure, monitored alongside the rest of the platform.

Scope your integration.

Integration setup is scoped during managed onboarding. Bring your CRM, source system, or destination, and implementation engineering confirms what’s standard, what’s custom, and when it ships.

Security and Trust →