Resources · Make integration

PIMMS Make integrationAutomate PIMMS with Make.

Want new links, QR codes and sales in PIMMS without copying anything by hand? The PIMMS Make integration gives you 5 action modules. This guide is for marketers who know PIMMS and are new to Make: connect your account, then build a first scenario.

Try the PIMMS integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PIMMS Make integration do for you?

The PIMMS Make integration lets a scenario, the automation you build in Make, act on your PIMMS account with no code. It offers five modules, the bricks of a scenario, and all of them are actions: they create a link, get a QR code, record a conversion or a sale, or call the PIMMS API. None of them watches PIMMS, so the scenario starts from another app or from a schedule.

Links that appear on their own. A new product added to a spreadsheet or a store can go through Create a new link, then Get a QR code, so the tracked link and its code are ready before anyone opens PIMMS.

Sales counted where you read your results. When a payment tool confirms an order, Create a Sale sends that sale to PIMMS. Your campaign numbers stop depending on a manual export.

Leads logged as conversions. A demo booked in a calendar app or a form filled on your site can trigger Create a Conversion, so a lead that never buys still shows up.

Know the limits before you start. The Make documentation for PIMMS says it is incomplete because too little public information exists about the app, so field details are best checked with a test run. For anything the four named modules miss, Make an API Call reaches the PIMMS API with the same account link. If a scenario fails, the Make troubleshooting guide covers the usual errors; to learn the editor properly, see the Make training, and if you are still choosing a tool, read n8n vs Make.

Connect

How do you connect PIMMS to Make?

  1. 01

    Add a PIMMS module

    In a scenario, click the +, type PIMMS in the search box and pick any of its modules, for example Create a new link. Then click Create a connection: the connection is your PIMMS account linked to Make once.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later, such as the brand or workspace it serves. Then either approve Make on the PIMMS page that opens, or paste the key PIMMS gives you, depending on what the window asks for.

  3. 03

    Save and reuse it

    Click Save. Every PIMMS module of every scenario can now pick this same connection from its list, so you only authorize once per account and never type the credentials again.

First scenario

Your first scenario with PIMMS

GoalWhen a new product appears in another app, Make creates its PIMMS link and gets the matching QR code.

  1. 01

    Create the scenario

    Open the Scenarios page, click to create a new scenario, then click the + in the middle of the editor to place the first module.

  2. 02

    Start from another app

    PIMMS has no trigger, so pick the app where products live, like a spreadsheet or a store, and choose its module that watches new items. Each new product becomes one bundle, one item passed to the next module.

  3. 03

    Add Create a new link

    Click the + to the right of the first module, search PIMMS, choose Create a new link and select your connection. Map the product page address from the previous module into the link fields.

  4. 04

    Chain Get a QR code

    Add Get a QR code after it and map the link returned by Create a new link. The QR code now follows each new link without a second step on your side.

  5. 05

    Test with Run once

    Click Run once, add a test product in the first app, and open the bubble above each module to read the bundles it received. Check in PIMMS that the link exists.

  6. 06

    Schedule and switch on

    Click the clock on the first module: a new scenario checks every 15 minutes by default, and the Free plan cannot go below that. Then switch the scenario on.

Modules

What each PIMMS module does

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

PIMMS1

Create a Conversion

Action

In Make“Tracks conversions”

Create a Conversion records a conversion in PIMMS as soon as another step of your scenario confirms one, so a signup or a booked demo is counted without a manual entry.

When to use it
a form app sends a new qualified lead and the result is not a purchase, which makes Create a Sale the wrong choice.
Watch out
the PIMMS docs on Make are incomplete, so run the scenario once and read the returned bundle before trusting your mapping.
PIMMS2

Create a Sale

Action

In Make“Tracks a sale”

Create a Sale gives PIMMS the orders your shop or payment tool confirms, so revenue lands in the same place as your campaign links instead of a spreadsheet you update by hand.

When to use it
place it right after the module that detects a paid order, and keep Create a Conversion for events without money.
Watch out
each sale sent costs one operation, the unit Make counts on your plan, so filter out test orders first.
PIMMS3

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call sends a request of your choice to the PIMMS API, reusing the connection you already created, so you can reach an endpoint that none of the four other modules covers.

When to use it
you need a PIMMS action that is missing from the module list and you have the endpoint name at hand.
Watch out
Make's PIMMS docs say they are incomplete, so you need the endpoint and its parameters from PIMMS itself before you build the request.
PIMMS5

Get a QR code

ActionIn the docs only

Get a QR code fetches the QR code of a PIMMS link, ready to be passed to the next module for a flyer, a label or an email sent by another app.

When to use it
put it directly after Create a new link so every fresh link gets its code in the same run.
Watch out
the module has no official description, so read its bundle after Run once to see what it returns before you map it into a design or mail tool.
Need help

Need help automating PIMMS with Make?

A person reads every message.

FAQ

Questions about the PIMMS Make integration

01Is the PIMMS Make integration free?
Yes, on the Make side. PIMMS is a standard app, so its modules are available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Every module run is an operation, and Make counts operations as credits each month, so a scenario that creates a link and then a QR code uses two per product.
02What do you need to connect PIMMS to Make?
A PIMMS account and a Make account. The Make documentation lists no specific prerequisite for PIMMS and no dedicated setup steps, so the generic flow applies: add any PIMMS module, click Create a connection, give it a name, then either authorize Make on the PIMMS page or paste the key PIMMS provides, and save. That connection is then reused by all five PIMMS modules in every scenario, so you set it up only once per account. If it fails, create it again with the right account.
03Can the PIMMS Make integration react in real time?
Not on its own, because PIMMS has no trigger module in Make: all five modules are actions. A scenario that uses PIMMS therefore starts from something else. The usual choice is a trigger from another app, such as a new order in a shop or a new row in a sheet. The other option is the schedule on the first module, which runs every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans go down to 1 minute. Speed then depends on the trigger you choose in the other app.
04What if a PIMMS module you need is missing in Make?
Use Make an API Call. It sends any request to the PIMMS API through the connection you already have, so an endpoint missing from Create a Conversion, Create a Sale, Create a new link and Get a QR code is still reachable. The catch: Make says its PIMMS documentation is incomplete, because there is not enough public information on the app. You need the endpoint and its parameters from PIMMS before you build the call. Test it with Run once and read the returned bundle before switching the scenario on.
05Should you use Make or n8n for PIMMS?
It depends on the tool your team already works in. In Make, PIMMS comes with five modules, including Make an API Call, a connection set up once, and a visual editor where each step appears as a bubble. Many apps also have an n8n node, so check whether one exists for PIMMS and which actions it covers before deciding. Compare the actions each side offers for your exact case, like logging sales or creating links, rather than the tool names. The comparison page linked above sets out the general criteria for both tools.
Same platform

Other docs you might need on this stack.

Browse all integrations