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.
Built in
Made to plug in.
A Clay column, a REST API and signed webhooks.
Enroll rows into an always-on campaign, or add them to a lead list.
Direct mail in Clay →REST APIOrganization API keysResearch, lead lists, enrollments, QR codes, scans and letter links.
API overview →WebhooksSigned with HMAC-SHA256Scan, address and enrollment events as they happen, with retries.
Webhook events →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.
Mark the Record ID column as a HubSpot record ID. It comes back with each scan.
HubSpot and CRMs →SalesforceReport exportExport leads or contacts with record IDs and pick Salesforce ID at import.
HubSpot and CRMs →Work emails, names and companies are enough. City and state help pick the closest office.
Standard linkedin.com/in/ URLs work, better with company name and domain.
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.
Catch webhooks or call the API from an HTTP step. There's no Mailyard Zapier app yet.
Receive events, verify the signature in a Code node and call the API.
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.
Related
Add direct mail as a step in a Clay table. Each row enrolls into an always-on campaign that finds, verifies and mails the lead.
HubSpot and CRMsExport a list from HubSpot or Salesforce, mail it with Mailyard, and keep each record ID attached to its QR scans.
API and webhooksA REST API for address research, lead lists, enrollments, QR codes and scans, with signed webhooks for every result.
Mail analyticsTrack each letter from printing to delivery, give each contact a QR code, and see who scanned, when and on what device.
Your next touchpoint fits in an envelope.
Upload a list and see how many addresses we can verify before you spend anything on postage.