Private beta is open. Public beta opens December 1.Join the private beta →

Join private beta →Book a demo

Integrations

Bring the list you have. Send results where you work.

Import from Clay, HubSpot, Salesforce, Apollo or any CSV. Scans come back with your CRM's record ID.

Where this list came fromLeads
Clay · HTTP API column
Enrolling into Q4 always-on
Built in
hubspot-closed-lost.csv
Record ID → Contact ID
CSV
salesforce-open-opps.csv
Salesforce ID → Contact ID
CSV
n8n workflow
enrollment.updated → your CRM
Webhook

Bring a list from

Export from the tool you have.

Upload a CSV to Leads. Each record's ID rides along as the Contact ID.

HubSpotCSV export

Mark the Record ID column as a HubSpot record ID. It comes back with each scan.

HubSpot and CRMs →
SalesforceReport export

Export leads or contacts with record IDs and pick Salesforce ID at import.

HubSpot and CRMs →
ApolloCSV export

Work emails, names and companies are enough. City and state help pick the closest office.

Sales NavigatorProfile URLs

Standard linkedin.com/in/ URLs work, better with company name and domain.

Any CSVImporter

Columns are detected for you. Lists with addresses skip straight to the USPS check.

Connect with

Wire it into any workflow.

Automation tools use the same API and webhooks.

ZapierWebhooks and HTTP steps

Catch webhooks or call the API from an HTTP step. There's no Mailyard Zapier app yet.

n8nWebhook and HTTP Request nodes

Receive events, verify the signature in a Code node and call the API.

Your own codeAnything that speaks HTTP

Enroll leads, read results and react to scans.

Start with the API →

The thread that ties it together

Your record ID goes in. It comes back with every scan.

Mailyard calls it the Contact ID. It never prints. It reaches your landing page as mailyard_contact and shows up in Mail Analytics, CSV exports and webhooks.

  • HubSpot and Salesforce IDs recognized at import
  • Your own IDs kept as a plain reference
# a scan of Dana's letter lands on
https://offer.ledgerline.example/q4
  ?mailyard_ref=K7QM2XR9TD
  &mailyard_contact=48213

# and arrives at your endpoint
scan.recorded  contactId "48213"

CSV in, CSV and webhooks out.

Mailyard doesn't write fields into your CRM yet. Close the loop with a CSV export keyed by record ID, or a webhook into Zapier, n8n or your own code.

Not available today

  • Native HubSpot or Salesforce sync
  • Prebuilt Zapier or n8n apps

Questions

More in the full FAQ →

Does Mailyard connect to HubSpot or Salesforce?

Through CSV today. Upload an export with the record ID as the Contact ID, and export deliveries and scans as CSV to import back. Native CRM sync isn't available yet.

Is there a Clay integration?

Yes, through Clay's HTTP API column. A row can enroll a lead into an always-on campaign or add them to a lead list. See Direct mail in Clay.

Can I use Zapier or n8n?

Yes, through their webhook and HTTP steps. There's no prebuilt Mailyard app in either directory.

Where do I get an API key?

Workspace owners create keys under Settings → API keys. A key is shown once and stored only as a hash.

Your next touchpoint fits in an envelope.

Upload a list and see how many addresses we can verify before you spend anything on postage.

Let's see if Mailyard fits.

Three quick questions, then pick a time for a 30-minute demo.

How many people do you want to reach each month?
Do you already have a lead list?