Resources · Make integration

Postalytics Make integrationAutomate Postalytics with Make.

Direct mail that follows your data instead of your spreadsheets. The Postalytics Make integration gives you 19 modules, one instant trigger and 14 actions among them. This page shows how to link your account, build a first scenario and pick the right module.

Try the Postalytics integration on MakeSee the 19 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Postalytics Make integration automate?

The Postalytics Make integration links your Postalytics account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that triggers, acts or searches. Once linked, contacts, templates, campaigns and mailpieces can move without anyone copying data by hand.

Mail a postcard when a deal closes. A new customer lands in your CRM, Create a Contact adds them to Postalytics and Send a Mailpiece puts a physical piece in the mail. The sales rep never opens a second tool.

Keep an eye on campaign activity. Watch Campaign Events is an instant trigger: Postalytics calls Make through a webhook as soon as a campaign event occurs, and Get a Campaign fetches the full campaign so the next module can post a summary to your team.

Clean up without clicking. List Contacts and Delete a Contact remove people who asked to leave your list, and Toggle Campaign Mail Status moves a campaign from test to live once a manager approves it.

What Make does not cover out of the box you can reach with Make an API Call, which uses the same connection. The documentation is AI-generated from the Postalytics docs, so check any important detail with Postalytics. If the choice between tools is still open, read n8n vs Make; to learn the editor step by step, the Make training starts from zero, and the Make pricing page explains plans.

Connect

How do you connect Postalytics to Make?

  1. 01

    Copy your API key

    In Postalytics, open Account, click Connect, then API Key, and copy the key shown on screen. You need an active Postalytics account for this; the key is what lets Make act in your name.

  2. 02

    Add a Postalytics module

    In your Make scenario, add any Postalytics module and click Create a connection. A connection is your Postalytics account linked to Make once, then reused by every Postalytics module you add later.

  3. 03

    Paste the key and save

    Give the connection a clear label in Connection name if you like (it is optional), paste the API key, and confirm. The module is then ready to fill.

First scenario

Your first scenario with Postalytics

GoalWhen a new customer appears in another app, Make creates the contact in Postalytics and sends them a mailpiece.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module: the app where new customers show up, such as your CRM or form tool.

  2. 02

    Add Create a Contact

    Click the + on the right of that module, search Postalytics, pick Create a Contact and link your account with Create a connection. Map the customer details from the previous module.

  3. 03

    Add Send a Mailpiece

    Add a third module with the +, choose Send a Mailpiece, and map the contact returned by the step before. Make lists what it can read once the connection exists.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, a bundle being one item passed along, here one customer. Check the contact in Postalytics.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Triggers

What starts a Postalytics scenario

1 module starts a scenario when something happens in Postalytics. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Postalytics as soon as it happens.

Postalytics1Watch Campaign Events

Watch Campaign Events

Instant trigger

In Make“Triggers when a new campaign event occurs.”

Hear about campaign activity the moment it happens: this trigger starts your scenario each time a new event occurs on a Postalytics campaign, and hands that event to the next module as a bundle.

How it fires
instant. Postalytics calls Make through a webhook as soon as the event happens, so there is no polling interval to wait for.
When to use it
you want a team alert, a CRM note or a report row whenever a campaign moves, without anyone refreshing the dashboard.
Watch out
click Create a webhook before Create a connection when you add it, or no event reaches the scenario.
Modules

Every Postalytics module in Make

Postalytics gives you 18 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Postalytics1

Create a Contact

Action

In Make“Creates a contact.”

Adds a new person to Postalytics so they can receive mail, fed by whatever app first captured them. It is usually the first Postalytics step in a scenario that ends with a mailpiece.

When to use it
a lead fills a form or signs a contract elsewhere and should join your mailing audience right away.
Watch out
map each field from the previous module rather than typing values, or every contact gets the same data.
Postalytics2

Create an Account

Action

In Make“Creates an account.”

Opens a new account in Postalytics from inside a scenario, which saves someone from setting it up by hand each time a new client or brand comes on board.

When to use it
an agency signs a client and wants their Postalytics space created as part of the onboarding scenario.
Watch out
test it with Run once on sample data first, since every run creates a real account.
Postalytics3

Create a Template

Action

In Make“Creates a template.”

Builds a new template in Postalytics so later mailpieces can reuse the same design, without anyone recreating it in the Postalytics interface.

When to use it
a design approved in another tool should become a ready template the moment it is signed off.
Watch out
this page does not list the template fields, so open the module in Make to see what it asks for before planning the mapping.
Postalytics4

Delete a Campaign

Action

In Make“Deletes a campaign.”

Removes a campaign from Postalytics for good, which keeps the campaign list short once a test or an abandoned idea is no longer useful.

When to use it
after List Campaigns has found campaigns your team marked as obsolete in a tracking sheet.
Watch out
a deletion cannot be undone from Make, so add a filter before this module and run the scenario once on a single campaign.
Postalytics5

Delete a Contact

Action

In Make“Deletes a contact.”

Takes a person out of Postalytics so they stop receiving mail, which matters when someone asks to be forgotten or leaves your customer base.

When to use it
someone unsubscribes through your CRM or helpdesk, and that request has to reach Postalytics too.
Watch out
you need the right contact first, so place List Contacts before it and check that only one bundle comes out.
Postalytics6

Delete an Account

Action

In Make“Deletes an account.”

Closes an account in Postalytics from a scenario, the mirror of Create an Account, so offboarding a client leaves nothing behind.

When to use it
a client contract ends in your billing or CRM tool and the matching Postalytics account should go with it.
Watch out
this is the heaviest delete in the list; keep a manual approval step in front of it and test on a dummy account.
Postalytics7

Delete a Template

Action

In Make“Deletes a template.”

Removes a template you no longer mail, so nobody on the team picks an outdated design by mistake when a new campaign starts.

When to use it
a rebrand retires the old designs, and List Templates has returned the ones to drop.
Watch out
the delete is final. Before the module runs, check that no live campaign still relies on that template.
Postalytics8

Get a Campaign

Action

In Make“Returns information about a campaign.”

Fetches everything Postalytics knows about one campaign, so the following modules can use its details in a message, a report or a decision.

When to use it
right after Watch Campaign Events, to turn a short event into a readable campaign summary for your team.
Watch out
it needs one campaign to look up; when you only have a name, find it first with List Campaigns.
Postalytics9

Get an Account

Action

In Make“Returns information about an account.”

Reads the details of one Postalytics account and passes them down the scenario, handy when one scenario serves several client accounts.

When to use it
before an action that differs from one client account to another, so the scenario can branch on what it reads.
Watch out
it reads only; nothing changes in Postalytics, which also makes it a safe module to test first.
Postalytics10

Get a Template

Action

In Make“Returns information about a template.”

Returns the details of a single template, which lets a scenario confirm which design it is about to mail before sending anything.

When to use it
a scenario picks a template from a rule and you want its information logged in a sheet or sent to a reviewer.
Watch out
it targets one template; to browse all of them, use List Templates instead.
Postalytics11

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Postalytics API with the connection you already set up, for the cases the listed Postalytics modules do not handle.

When to use it
the Postalytics API documentation describes a feature you need and no listed module offers it.
Watch out
you write the request yourself here, so read the Postalytics API docs first and test with Run once before switching the scenario on.
Postalytics12

Send a Mailpiece

Action

In Make“Sends a mailpiece.”

Puts a physical mailpiece on its way from a scenario, the step where your scenario turns into real mail in a real mailbox.

When to use it
a customer event elsewhere, such as a first order or a renewal, deserves a card in their mailbox.
Watch out
each run sends real mail, so test with Run once on your own details before the scenario goes live.
Postalytics13

Toggle Campaign Mail Status

Action

In Make“Changes mail status in a campaign from test to live and vice versa.”

Switches a campaign between test and live, in either direction, so the go-live of a mailing becomes a step of your process instead of a click someone forgets.

When to use it
a manager approves the campaign in your project tool and that approval should flip it to live.
Watch out
since it switches in both directions, a second run would most likely undo the first; read the current status with Get a Campaign before it runs.
Postalytics14

Update a Contact

Action

In Make“Updates a contact. Module doesn't support partial updates. If the field is not set, the value will be updated to null.”

Changes a contact already stored in Postalytics, for example after a move, so the next mailpiece goes to the right place.

When to use it
a customer edits their profile in your store or CRM and Postalytics should follow.
Watch out
the module does not accept partial updates; any field left empty is set to null, so map every field you want to keep, not only the changed one.
Postalytics15

List Campaigns

Search

In Make“Lists campaigns.”

Brings back your Postalytics campaigns as separate bundles, one per campaign, so the following modules can act on each of them in turn.

When to use it
you want a sheet listing every campaign, or you need to find the campaigns a delete or a status change should touch.
Watch out
each bundle it returns runs the next modules once, and every run counts as operations on your plan.
Postalytics16

List Contacts

Search

In Make“Lists contacts.”

Returns contacts from Postalytics one bundle at a time, which is how a scenario finds the right person before updating or removing them.

When to use it
ahead of Update a Contact or Delete a Contact, when you only know who the person is in another tool.
Watch out
a search can return zero, one or many bundles; add a filter so the next module only gets the contact you expect.
Postalytics17

List Templates

Search

In Make“Lists templates.”

Lays out the templates stored in Postalytics, each as its own bundle, so a scenario can pick one or clean up the list.

When to use it
to feed a review sheet of your designs, or to find which templates Delete a Template should remove.
Watch out
if the list comes back empty, the next modules do not run at all, which can look like a silent failure while testing.
Postalytics18

Search Events

Search

In Make“Searches for events.”

Looks up past events in Postalytics on demand, a useful complement to the instant trigger when you need history rather than the latest event.

When to use it
a scenario started by another app, like a sales review, needs the events already recorded for a campaign.
Watch out
like every search, it may return several bundles, so plan an aggregator or a filter if you want a single summary.
Need help

Need help automating Postalytics with Make?

A person reads every message.

FAQ

Postalytics and Make: common questions

01Is the Postalytics Make integration free?
Yes, on the Make side. Postalytics is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs of up to 5 minutes, a minimum of 15 minutes between two scheduled runs and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Postalytics itself needs an active account on their side; its subscription is set by Postalytics, and this page gives no price for it.
02What do you need to connect Postalytics to Make?
An active Postalytics account and its API key. In Postalytics, go to Account, then Connect, then API Key, and copy the key. In Make, add a Postalytics module, click Create a connection, optionally name the connection and paste the key. For the instant trigger Watch Campaign Events, click Create a webhook first, then Create a connection. The same connection then serves every Postalytics module in your scenarios, so you only paste the key once, even when you add more modules later.
03Does the Postalytics trigger in Make fire in real time?
Yes. Watch Campaign Events is an instant trigger: Postalytics calls Make through a webhook as soon as a new campaign event occurs, and the scenario starts on that event. There is no polling interval to set for it. The webhook has to exist, so create it when you add the module. If you need older events rather than new ones, the Search Events module looks them up from any other scenario.
04What if a Postalytics module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Postalytics API with the connection you already have, so a feature without its own module is still within reach. You write the request yourself, based on the Postalytics API documentation. Keep in mind that the Make documentation for this app is AI-generated from the Postalytics docs and may contain mistakes, so confirm important behavior with Postalytics before relying on it.
05Should you use Make or n8n for Postalytics?
It depends on the tool your team already builds in. In Make, Postalytics comes with 19 modules, including an instant trigger on campaign events and Make an API Call for the rest. n8n often has a node for the same apps, so check whether it covers the Postalytics actions you need before choosing. Compare the modules each tool offers for your exact scenario, and pick the editor your team will actually maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations