Resources · Make integration

Handwrytten Make integrationAutomate Handwrytten with Make.

What if a real ink-on-paper card went out on its own when a client deserves one? The Handwrytten Make integration gives you 14 action modules to add contacts, design cards and send them. This page walks you through the connection and a first working scenario.

Try the Handwrytten integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Handwrytten Make integration let you automate?

The Handwrytten Make integration lets Make, a no-code automation tool, order physical cards in your Handwrytten account for you. You build a scenario (the automation itself, a chain of steps) that takes a name and an address from another app and hands them to Handwrytten, which mails the card.

A thank-you note for every new customer. Your store or CRM supplies the buyer, Create Contact saves them to your Handwrytten address book, and Send Card mails the note. Nobody retypes an address.

A batch of cards for an event list. When the guest list is final, Add Card To Basket or Bulk Add Cards to Basket collects every card, then Send Basket places the whole order at once instead of one order per card.

A follow-up sequence that runs by itself. A lead signs up on a form, and Add Contact to Multi-Step Campaign enrolls them in a campaign you already set up in Handwrytten.

Keep the limits in mind. Handwrytten has no trigger in Make, so something else has to start the scenario: another app or a schedule. There is also no generic API call module, so you only get the 14 modules listed below. If you are still weighing platforms, the n8n vs Make comparison and the Make review set the scene, and Make pricing explains how operations are counted.

Connect

How do you connect Handwrytten to Make?

  1. 01

    Create an API key in Handwrytten

    In Handwrytten, open your profile name at the top right, pick Integrations, then click Add API Key. Give the key a name and copy the value shown next to it. You need an active Handwrytten account for this.

  2. 02

    Add a Handwrytten module in Make

    In your scenario, add any Handwrytten module and click Create a connection. A connection is your Handwrytten account linked to Make once, then reused by every Handwrytten module. The Connection name field is optional.

  3. 03

    Paste the key and save

    Paste the API key you copied into the credentials field, or follow the instructions Make shows on screen, and save. The module now reads your Handwrytten account and you can fill its fields.

First scenario

Your first scenario: a card for each new contact

GoalWhen a new client shows up in another app, Make saves them in Handwrytten and sends them a card.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Handwrytten has no trigger, so the first module comes from the app that holds your clients, such as your CRM or your store.

  2. 02

    Add Create Contact

    Click the + to the right of that first module, search for Handwrytten and pick Create Contact. Create the connection, then map the name and address coming from the previous module.

  3. 03

    Add Send Card

    Add Send Card after it. Fill its fields with the data mapped from the earlier modules. Each client that flows through becomes one bundle, meaning one item passed from module to module.

  4. 04

    Test with Run once

    With Test Mode on in Handwrytten, click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check the address before a real card goes out.

  5. 05

    Schedule and switch it on

    Set the clock on the first module (every 15 minutes by default) and turn the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Modules

What can the Handwrytten modules do?

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

Handwrytten1

Add Card To Basket

Action

In Make“Adds A Card To Basket. After all cards have been added (via an array), call an aggregator to complete and then "Submit Basket"”

Puts one card in your Handwrytten basket without sending it yet, so you can group several cards into a single order. Think of it as the shopping cart step.

When to use it
your scenario loops over a list of recipients who each get a different card or message, and you want one order at the end.
Watch out
nothing ships until you add an aggregator after it and then Send Basket, as the doc explains.
Handwrytten2

Add Contact to Multi-Step Campaign

Action

In Make“Add a contact to a multi-step campaign.”

Signs a contact up for a multi-step campaign, so Handwrytten handles the whole sequence of mailings instead of you building each one in Make.

When to use it
a lead fills in a form or a deal reaches a new stage, and that person should enter a follow-up series you already designed in Handwrytten.
Watch out
the campaign has to exist on the Handwrytten side first; this module enrolls people, it does not create the campaign.
Handwrytten3

Bulk Add Cards to Basket

Action

In Make“Add many cards (of the same type) in an array”

Drops a whole list of cards (an array) into the basket in one module run, which keeps your scenario short and your operation count low.

When to use it
every recipient on the list gets the same card, for example the guests of a single event, and you already hold them as an array.
Watch out
all cards in the array must be of the same type; mixed cards belong in Add Card To Basket instead.
Handwrytten4

Create Contact

Action

In Make“Adds a contact to your Handwrytten Address Book.”

Saves a person in your Handwrytten address book, so their name and address are ready the next time you mail them a card, whether from Make or from Handwrytten itself.

When to use it
a new customer lands in your store or CRM and you want Handwrytten to know them before any card goes out.
Watch out
place it where each person passes once, such as a new customer event, rather than after every order, so the address book stays tidy.
Handwrytten5

Create Custom Card

Action

In Make“Creates a custom card based on a dimension.”

Builds your own card design from a chosen card dimension, so the card itself carries your branding and not a stock layout from the catalog.

When to use it
you need a format other than the flat 5x7, for instance a larger card for a product launch.
Watch out
it only builds the design; mailing it still takes Send Card, Schedule Card or the basket modules.
Handwrytten6

Create Custom Card (Flat 5x7)

Action

In Make“Creates a Custom Card.”

Creates a custom card in the flat 5x7 format, the quickest way to get a branded card ready without picking a dimension each time.

When to use it
your team sends the same flat card for thank-you notes and only the artwork changes between campaigns.
Watch out
if you later need another size, switch to Create Custom Card rather than trying to resize this one.
Handwrytten7

Delete Custom Card

Action

In Make“Delete a previously created custom card.”

Removes a custom card you created earlier, which keeps your card list clean once a campaign or a seasonal design is over.

When to use it
a promotion ends and its card should no longer be picked by anyone on the team or by another scenario.
Watch out
a deletion cannot be undone from Make, so check which card you map before you run it.
Handwrytten8

Delete Custom Image

Action

In Make“Delete a previously uploaded custom image.”

Erases an image you uploaded before, such as an old logo or a back-of-card visual, so it stops showing up among your assets.

When to use it
your branding changes and the previous logo must not end up on a new card by mistake.
Watch out
this is permanent; make sure no custom card you still send relies on that image.
Handwrytten9

Empty Basket

Action

In Make“Empties the User's Basket”

Clears every card waiting in your basket, giving the next batch a clean start with nothing left over from an earlier run.

When to use it
place it at the start of a batch scenario, before Add Card To Basket, when a failed test may have left cards behind.
Watch out
it empties the whole basket, not a single card, so keep it away from the end of the scenario.
Handwrytten10

Get Address Book

Action

In Make“Gets Members of Address Book”

Reads the members of your Handwrytten address book and passes them to the next modules, so you can reuse contacts you already saved.

When to use it
you want to send a card to people already stored in Handwrytten, or compare them with your CRM before creating anyone new.
Watch out
when it returns several members, every module placed after it runs for each one and uses operations accordingly.
Handwrytten11

Schedule Card

Action

In Make“Schedules a Single Card”

Books a single card for later instead of mailing it right away, handy when the date that matters is not today.

When to use it
a client signs a contract and you want the anniversary or renewal card lined up the moment the deal closes.
Watch out
it handles one card per run; for a group, go through the basket modules instead.
Handwrytten12

Send Basket

Action

In Make“Sends all orders in a basket. Use after an array aggregator.”

Everything waiting in the basket leaves as one order. This is the step that actually turns queued cards into mail.

When to use it
it closes any scenario that filled the basket with Add Card To Basket or Bulk Add Cards to Basket.
Watch out
the doc says to place it after an array aggregator, so that the basket is sent once for the whole batch.
Handwrytten13

Send Card

Action

In Make“Sends one card.”

Mails one card to one recipient straight away, the shortest path from an event in another app to a note in someone's mailbox.

When to use it
a single thing happens, like a first purchase or a signed quote, and exactly one person should get a card.
Watch out
while you test, keep Test Mode on in Handwrytten so the runs are not charged.
Need help

Need help automating Handwrytten with Make?

A person reads every message.

FAQ

Handwrytten and Make: common questions

01Is the Handwrytten Make integration free?
Yes on the Make side: Handwrytten is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) drop the interval to one minute and count usage in operations per month. The cards themselves are billed by Handwrytten under your own subscription, which Make does not cover.
02What does the Handwrytten Make integration need to connect?
An active Handwrytten account and an API key. In Handwrytten, open your profile name, go to Integrations, click Add API Key, name the key and copy it. In Make, add any Handwrytten module, click Create a connection, paste the key and save. Turning on Test Mode before you create the key lets you try the modules without being charged while you build and test the scenario. Once saved, that single connection serves all 14 Handwrytten modules in every scenario you build.
03Can Handwrytten start a Make scenario on its own?
No. Handwrytten has no trigger module in Make, so it never starts a scenario by itself. Something else has to: a trigger from another app, such as a new order in your store or a new deal in your CRM, or the scenario schedule set on the first module, which runs every 15 minutes by default. Handwrytten modules then come after that first module and act on the data it passes along.
04What if a Handwrytten module is missing in Make?
It depends on what you need. Handwrytten offers 14 action modules in Make and no generic API call module, so you cannot reach features outside that list from inside Make. Check first whether two existing modules cover the job, for example Get Address Book followed by Send Card. If not, another app may hold the data you need, or the team can look at your case and suggest a workaround.
05Make or n8n for the Handwrytten integration?
It depends on the tool your team already uses. On Make, Handwrytten comes with 14 ready action modules, a guided connection by API key and a visual editor where each step is a module you click together. The same app often has an n8n node as well. Pick the platform where your other automations already live, so your client data and your card sending sit in one place and one person can maintain them.
Same platform

Other docs you might need on this stack.

Browse all integrations