Postalytics

Put physical mail into automated workflows through Postalytics. Agents create and list recipient contacts, review direct mail campaigns, and fire triggered drops that mail a postcard or letter to a single address in real time.

5 actions API key available

Postalytics website ↗ Platform Documentation ↗ Capability data verified 2026-07-28

A customer's renewal date crosses the 60-day mark without a signed renewal

List Campaigns confirms the renewal letter campaign is active and current

The agent verifies the mailing address is complete: name, street, city, state, ZIP

Create Contact writes the recipient into Postalytics for tracking and future targeting

The account owner reviews the queued mail piece, because a renewal letter with stale pricing or the wrong entity name cannot be pulled back from the mail stream

Trigger Drop mails the letter through the approved campaign

List Drops feeds the fulfilment tracker as the piece moves from queued to printed to mailed to delivered

What This Integration Enables

Physical mail is the channel spam filters cannot touch, and it mostly goes unused because it never fit inside automation. The inbox is a war zone; the mailbox is nearly empty, and the piece that lands there gets held, read, and kept in a way no email does. Postalytics changes the unit of direct mail from "campaign to a list" to "one piece to one address, now," and this connector puts that unit in FlowRunner agents' hands. Mail becomes a step in the same workflows that run your digital channels, fired by the same events, gated by the same oversight. - Mail a postcard or letter to a single address in real time when an event fires anywhere in your stack - Sync recipients from CRMs, forms, and spreadsheets into Postalytics as deliverable contacts - Pick the right campaign programmatically and review campaign status before sending through it - Track every triggered piece through queued, printed, mailed, and delivered, per campaign Address quality is the quiet variable in all of it. A triggered drop is only as good as the address it carries, and the connector's guidance is blunt: provide first name, address line 1, city, state, and ZIP or the piece may never arrive. FlowRunner agents make that a checked precondition rather than a hope, holding incomplete addresses for enrichment instead of paying to mail them. Unlike email, a mailed piece has no unsend and no edit window, which makes this connector a natural home for FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gates.

Without FlowRunner

Physical mail as a quarterly project Direct mail means a list export, a vendor, a proof cycle, and a six-week lead time

Digital and physical never meet The email sequence knows the customer's behavior; the mailbox campaign knows nothing

No idea what got delivered Pieces go out and the feedback loop is silence until response rates arrive

With FlowRunner

Mail fires from events A signup, a renewal date, a churn signal mails a single piece in real time

One orchestration, every channel The same FlowRunner flow that sends the email and the SMS drops the postcard

Fulfilment tracked per piece Every drop reports queued, printed, mailed, delivered, and the tracker updates itself

Use Case Scenarios

The welcome postcard that arrives with the package

A new customer appears in [Shopify](/integrations/shopify). The agent validates the shipping address, creates the contact, and calls Trigger Drop through the welcome campaign the same hour the order confirms. The postcard lands within days of the first package, while the brand is still on the kitchen counter. First orders run autonomously under a per-day cap; the day the cap is exceeded, the batch waits for a person, which is how a viral sales day stays a good day.

Win-back letters for the segment email cannot reach

The lifecycle team builds a re-engagement segment in [HubSpot](/integrations/hubspot): customers who stopped opening email entirely. The agent pulls the segment, checks each mailing address for completeness, and stages the win-back drops with a count and per-piece cost summary. Marketing approves the batch, Trigger Drop runs per recipient, and List Drops writes delivery status back to each CRM record, so the next touch knows the letter arrived. The segment that was unreachable by email gets a physical touch with full attribution, and the cost per piece was reviewed before a single one printed.

The fulfilment tracker that runs itself

Every morning the agent runs List Drops across active campaigns and updates the tracker in [Google Sheets](/integrations/google-sheets): pieces queued, printed, mailed, delivered, by campaign. Pieces stuck in queued beyond the expected window get flagged to [Slack](/integrations/slack) before a customer calls asking where their document is. Direct mail gets the same operational visibility as email, which it never had, and the ops team stops treating the postal stream as a black box between send and complaint.

Human-in-Loop Highlight

Trigger Drop puts ink on paper and paper in the postal stream, and from that moment there is no recall, no correction, and no unsend, just print and postage spent per piece. A loop that fires it twice mails the customer twice; a wrong campaign ID mails the win-back letter to the brand-new customer. So FlowRunner agents treat this action with graduated trust. Single event-driven pieces through a designated campaign run autonomously under a daily cap. Anything else pauses: a batch over the cap posts its recipient count, campaign, and total piece cost for approval, and any drop through a campaign the flow has not used before goes to the marketing owner with the campaign's List Campaigns status attached. The agent does the address hygiene, the segmenting, and the tracking. The decision to commit postage at scale stays human.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

5 actions

Contacts

Create Contact Creates a contact with a full mailing address, name, street, city, state, ZIP, country, and optional email, so recipients can be targeted by campaigns and triggered drops. Address completeness here is what makes the piece deliverable later.
List Contacts Retrieves contacts with page and per-page pagination and an optional name or email search. The lookup behind dedup checks and recipient audits.

Campaigns

List Campaigns Retrieves the account's direct-mail campaigns with IDs, names, type, and status. The pre-send check that confirms an agent is about to mail through the campaign it thinks it is.

Triggered Drops

Trigger Drop Mails a single piece to a supplied recipient address through a selected triggered campaign; Postalytics queues and prints it. The real-time, event-driven send, and the irreversible operation this page's gate exists for.
List Drops Retrieves previously triggered drops with status, queued, printed, mailed, delivered, and campaign, filterable by campaign and paginated. The fulfilment feedback loop for every piece the agents send.

Frequently Asked Questions

What can FlowRunner do with Postalytics?

FlowRunner agents can run Create Contact, List Contacts, and List Campaigns in Postalytics, plus 2 more actions.

Does connecting Postalytics to FlowRunner require OAuth?

No. Postalytics connects to FlowRunner with an API key, no OAuth flow required.

Can Postalytics trigger a FlowRunner workflow automatically?

Postalytics doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Postalytics

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us