Resources · Make integration

Thanks.io Make integrationAutomate Thanks.io with Make.

What if every new customer got a real card in the mail without anyone licking a stamp? The Thanks.io Make integration gives you 12 modules: 11 actions and 1 search to manage recipients and send mail. This guide connects your account and builds your first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Thanks.io Make integration do for you?

The Thanks.io Make integration lets a Make scenario, the automation you build in Make, keep your Thanks.io mailing lists up to date and send physical mail on its own. Something happens in another tool, and a postcard, a notecard or a letter leaves Thanks.io without a manual export or a copy and paste.

A welcome card for every new buyer. When your store or CRM records a new customer, Add a Recipient puts that person on a mailing list and Send a 4x6 Postcard mails the card. Prefer more room for the message? Send a 6x9 Postcard or Send a Notecard slot into the same place.

A clean list that follows your CRM. A contact moves house or unsubscribes: Update a Recipient fixes the record, Delete a Recipient removes it, and your next mailing reaches the right door. The Agile CRM Make integration or the Airtable Make integration are natural sources for those changes.

An order you can report on. After a send, Get Order Details brings the order back into the scenario so you can log it in a sheet or a CRM note.

Know the limits before you start. Make itself states that its Thanks.io documentation is incomplete, because little public information exists about the app. Thanks.io also has no trigger in Make, so a scenario starts from another app or from a schedule. For anything the 11 other modules skip, Make an API Call reaches the rest of the Thanks.io API. Weighing tools? The n8n vs Make comparison lays out the differences.

Connect

How do you connect Thanks.io to Make?

  1. 01

    Add a Thanks.io module

    In your scenario, click the + and search for Thanks.io. Pick any module, for example Add a Recipient, then click Create a connection. A connection is your Thanks.io account linked to Make once and reused by every Thanks.io module.

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, such as your company name, so it is easy to spot later. Then follow what Thanks.io asks for: either approve access on the Thanks.io page that opens, or paste the key Thanks.io gives you.

  3. 03

    Save and check the fields

    Click Save. Back in the module, Make can now read what your account holds, so the mailing lists appear in the fields instead of you typing an ID by hand. If nothing shows up, check the connection first.

First scenario

Your first scenario: a welcome postcard for each new customer

GoalWhen a new customer shows up in the app you already use, Make adds them to a Thanks.io mailing list and sends them a 4x6 postcard.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to place the first module. Thanks.io has no trigger, so this first module belongs to the app where new customers appear, like your store or CRM.

  2. 02

    Add the recipient

    Click the + to the right of that first module, search for Thanks.io and choose Add a Recipient. Pick your connection, select the mailing list, then map the name and address that the previous module passed along.

  3. 03

    Mail the postcard

    Add Send a 4x6 Postcard after it. Map the recipient data from the step before. Each module run counts as an operation, one execution on one bundle, and that is what Make counts on your plan.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundle each module received, a bundle being one item passed along, here one customer. Use your own address for this test.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and that interval is also the shortest one on the Free plan. Set it, then switch the scenario on.

Modules

What each Thanks.io module does in Make

Thanks.io gives you 12 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Thanks.io1

Add a Recipient

Action

In MakeAdds a recipient to a mailing list.

Puts a new person on one of your Thanks.io mailing lists, so every later send can reach them without retyping an address.

When to use it
right after a signup, a first purchase or a new deal in another app, as the first Thanks.io step of the scenario.
Watch out
pick the mailing list carefully in the module, because the recipient lands only in the list you select.
Thanks.io2

Delete a Recipient

Action

In MakeDeletes an existing recipient from the selected mailing list.

Removes someone from the mailing list you choose, which keeps future campaigns away from people who asked to stop receiving mail.

When to use it
a contact unsubscribes or is marked as lost in your CRM, and you want Thanks.io to follow that change.
Watch out
it removes a real contact from your list, so run it on one test contact first.
Thanks.io3

Get a Recipient

Action

In MakeReturns details about the selected recipient.

Fetches the full record of one recipient you already know, so the next module can reuse the stored name and address.

When to use it
before a send, to confirm the details Thanks.io holds match what your CRM says.
Watch out
it reads a single person; to browse a whole list, List Recipients is the right module.
Thanks.io4

Get Order Details

Action

In MakeReturns order details by ID.

Pulls back the details of one Thanks.io order from its ID, which gives you something concrete to log after a mailing goes out.

When to use it
at the end of a scenario that sends a card or letter, to write the order into a spreadsheet or a CRM note.
Watch out
the module needs the order ID, so map it from an earlier module that holds it.
Thanks.io5

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Opens the whole Thanks.io API to your scenario, reusing the same connection, for the cases the ready-made modules leave out.

When to use it
a feature you use in Thanks.io has no dedicated module in this list, and you still want Make to handle it.
Watch out
you describe the request yourself here, so keep the Thanks.io API reference open while you set it up.
Thanks.io6

Send a 4x6 Postcard

Action

In MakeSends a 4x6 postcard.

Mails the smaller of the two postcard formats Thanks.io offers in Make, a quick way to put a physical thank you in someone's hands.

When to use it
a short message is enough, such as a welcome after a first order or a reminder before an appointment.
Watch out
every run sends real mail, so test with Run once on your own address before switching the scenario on.
Thanks.io7

Send a 6x9 Postcard

Action

In MakeSends a 6x9 postcard.

Sends the larger postcard, which leaves more space for an image or a longer line of text than the 4x6 version.

When to use it
an offer or an announcement that needs room to be read, like a seasonal promotion for your best buyers.
Watch out
keep only one postcard module per path, or the same person receives two cards from a single run.
Thanks.io8

Send a Notecard

Action

In MakeSends a notecard.

Mails a notecard rather than a postcard, a more personal format for moments when a plain card would feel too light.

When to use it
thanking a client after a signed contract or a renewal, where the gesture matters as much as the words.
Watch out
map the recipient from Add a Recipient or Get a Recipient placed earlier, so the card never goes out without an address.
Thanks.io9

Send a Windowed Letter

Action

In MakeSends a letter.

Sends a letter in the windowed version, for content that deserves a full page instead of the few lines a card allows.

When to use it
a formal notice, a renewal proposal or a longer message to a customer you already hold in a mailing list.
Watch out
the module name is the only difference Make shows from the windowless one, so choose the format your campaign expects.
Thanks.io10

Send a Windowless Letter

Action

In MakeSends a windowless letter.

Mails a letter in the windowless version, the counterpart of Send a Windowed Letter when your campaign calls for that format.

When to use it
a mailing where you settled on windowless letters, such as a personal note from a manager to key accounts.
Watch out
since the documentation says little, send one test letter to yourself and check the result before a real batch.
Thanks.io11

Update a Recipient

Action

In MakeUpdates an existing recipient from the selected mailing list.

Changes the record of someone already on a mailing list, so the next card or letter goes to their current address.

When to use it
a customer edits their profile in your store or CRM and you want Thanks.io to hold the same data.
Watch out
it only works on an existing recipient; for a person who is not on the list yet, use Add a Recipient.
Thanks.io12

List Recipients

Search

In MakeLists all recipients in the selected mailing list.

Returns everyone on the selected mailing list, each person as a separate bundle that the following modules handle one by one.

When to use it
checking a list against your CRM, or copying its contents to a sheet before a campaign.
Watch out
a search can return zero, one or many bundles, and every later module runs once per bundle, which adds operations fast.
Need help

Need help automating Thanks.io with Make?

A person reads every message.

FAQ

Thanks.io and Make: common questions

01Is the Thanks.io Make integration free?
Yes, on the Make side. Thanks.io is a standard app, so it works from the Free plan onward. That plan allows 2 active scenarios, runs them 15 minutes apart at the shortest, stops each run after 5 minutes and caps transfer at 512 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations per month. What Thanks.io charges for the mail itself is a separate matter between you and Thanks.io.
02What do you need to connect Thanks.io to Make?
A Thanks.io account and a Make account are enough to begin. Make's documentation lists no specific prerequisite for this app. You add a Thanks.io module, click Create a connection, optionally name it, then either approve access on the Thanks.io page or paste the key Thanks.io provides, and click Save. Because Make describes its Thanks.io documentation as limited, test the connection with Run once on a single contact before relying on it for real mailings.
03Can the Thanks.io Make integration react in real time?
No, not on its own. Thanks.io has no trigger module in Make, so nothing in Thanks.io can start a scenario. There are two ways around it. The first is to open the scenario with a trigger from another app, such as your store or CRM, and place the Thanks.io modules after it. The second is to run the scenario on a schedule; a new scenario runs every 15 minutes by default, and paid plans can go down to 1 minute.
04What if a Thanks.io module is missing in Make?
Use the Make an API Call module. It sends any request to the Thanks.io API through the same connection, so you can reach a feature that none of the 11 other modules cover. You write the request yourself, which means keeping the Thanks.io API reference at hand. Also keep in mind that Make calls its own Thanks.io documentation incomplete, so field names and behavior are best checked with a Run once test before a scenario goes live.
05Should you use Make or n8n for Thanks.io?
It depends on where you want to build. In Make, Thanks.io comes with 12 modules: recipient management, postcards, notecards, letters, order details and a Make an API Call module for the rest. It is available from the Free plan. The same app often has an n8n node too, so check whether Thanks.io is covered there before you decide. The n8n vs Make comparison mentioned earlier on this page lays out how the two tools differ, without ranking one above the other.