PostKnock Integrations: How to Get Data In and Out

Most direct mail tools assume you'll plumb a complex integration to your CRM, your billing system, and your ad platform before you can ship a postcard. PostKnock takes a different approach: CSV in, CSV out. The systems your business already uses can produce CSV files in two clicks. PostKnock can ingest them in another two. This guide is the honest answer to "what does PostKnock integrate with today?" and "what's coming next?"

CSV Import Works with Any System

Practice management systems, CRMs, ESPs, accounting tools — if it can produce a list of customer names with mailing addresses, it can feed PostKnock. Every tool we've encountered (Dentrix, OpenDental, ServiceTitan, Housecall Pro, ChiroTouch, AVImark, Cornerstone, Mindbody, HubSpot, Salesforce, Zoho, Constant Contact, Mailchimp) can export to CSV in two or three clicks.

When you drag the CSV into PostKnock's import zone, the wizard auto-maps standard column headers, validates every address against USPS, and dedupes against contacts already in your account. You get a complete view of which contacts are mailable, which need address fixes, and which are duplicates — all before any campaign ships.

For step-by-step PMS export instructions and the exact column format PostKnock expects, see How to Import Contacts from a CSV File.

Automatic Contact Import with Zapier

If your contacts start out in another tool — a web form, a booking app, a spreadsheet, your CRM — you don't have to export a CSV every time. PostKnock's Zapier integration can add contacts to your account automatically, and it's included on the Free plan.

The integration ships with one action: Find or Create Contact. In a Zap, point any of Zapier's 6,000+ source apps at PostKnock and pass along a contact. PostKnock matches it to a contact you already have, or creates a new one:

• What it needs. A name or company, plus a complete mailing address. Email, phone, and your own ID are optional but worth passing — they make matching more accurate.
• Addresses are validated, just like an import. If the mailing address doesn't pass validation, the contact is not created — no half-finished records land in your account.
• Contacts you already have are never overwritten. On a match (by your ID, then email, then phone), PostKnock returns the existing contact and leaves every field exactly as it was.
• Optional list. You can drop each found-or-created contact onto an existing contact list.

You connect from the Zapier side: add PostKnock as an action in the Zap editor and authorize it there. There's nothing to install inside PostKnock — once connected, the link appears under Admin → Integrations, where you can check its status or disconnect it. Contacts flow one way, into PostKnock.

CSV Export of Your Contacts

Your data is never locked in. The Contacts page has an Export CSV button that downloads your entire contact list — one row per contact, generated on demand with no email link and no waiting on a queue.

The export columns include:

• Contact info — first/last name, company, email, phone.
• Mailing address — address lines, city, state, ZIP and ZIP+4, plus a flag for whether the address is complete enough to mail.
• Do-not-contact status — so DNC preferences travel with the list.
• Tags — any tags you've applied for segmenting.

A per-campaign results export (delivery status, QR scans, and call outcomes per wave in one file) isn't available yet — campaign results live in the in-app campaign dashboard for now, and a results export is planned as part of the Public API milestone below.

Use Cases for Exporting Data

• Keeping your own backup. Pull a copy of your list any time — it's your data.
• Carrying DNC preferences into other tools. The DNC column lets you filter who you contact from your email tool or CRM.
• Cleaning in a spreadsheet. Export, fix addresses or dedupe in Excel, and re-import — the import wizard matches the same columns.

QR Scan Data

QR scan activity — who scanned, on which wave, and when — is tracked automatically and shown in your campaign's tracking views in-app. A raw scan-log CSV export isn't available yet; it's part of the same Public API milestone below.

For more on what QR data looks like and how it's collected, see QR Code Tracking.

Native Integrations: On the Roadmap

Honest answer: apart from Zapier (above), PostKnock does not yet have direct, "click-to-connect" integrations with individual practice management systems or CRMs. We're a young product, and getting the core direct-mail experience right has been our focus. Building stable, deep integrations with two-dozen PMSes is a multi-year effort we'll take on as the basics get more solid.

The realistic roadmap, in priority order:

1. Public REST API. So technically-inclined customers can push contacts and pull campaign results programmatically. This is the foundation for everything that comes after.
2. Native PMS integrations. Starting with the most-requested systems — Dentrix, OpenDental, and ServiceTitan are at the top of the list.

If you have a specific integration request, send it to support@postknock.com and we'll add your vote. Customer demand is the single biggest input into prioritization.

Webhooks: Not Yet Available

PostKnock does not currently expose outbound webhooks. We know they're high on the wish list for customers who want real-time event delivery into their own systems (e.g., "fire when a contact scans" or "fire when a wave is delivered"). Webhooks are part of the same Public API milestone above.

In the meantime, the export pattern works for most use cases — pull the campaign results CSV daily or weekly, depending on how fresh the data needs to be.

Data Privacy and Ownership

Your contacts and campaign data are yours. You can export your full data set at any time, and you can request deletion when you cancel. We don't share contact data with third parties for advertising, and we don't use your customer data to train models. Full details are in our privacy policy.

A Note on Spreadsheets

Don't underestimate how much you can do with a regular spreadsheet plus PostKnock's CSV imports/exports. You can run your entire direct-mail program out of a single weekly export-import workflow:

1. Monday morning: export the latest customer list from your PMS to CSV.
2. Drop it into PostKnock; the importer dedupes against existing contacts.
3. Launch (or update) the recall campaign with the freshly added contacts.
4. End of week: export campaign results back into a sheet for your owner's report.

This workflow takes 15–20 minutes a week and beats most "fully integrated" setups in terms of operator clarity. For an end-to-end view of what running this on PostKnock looks like, see Getting Started with PostKnock.

Was this helpful?

If this guide answered your question, great. If not, we want to hear about it.

Need more help? Email support@postknock.com and we'll respond within one business day.

Related articles

• How to Import Contacts from a CSV File
• QR Code Tracking: Measuring Postcard Performance