Resources · Zapier integration

PIMMS Zapier integrationAutomate PIMMS with Zapier.

The PIMMS Zapier integration gives you 0 triggers, 2 actions and 0 searches. In plain terms: another app starts the automation, and PIMMS receives the result as a conversion or a sale, tied back to the link or QR code that brought the customer in.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the PIMMS Zapier integration actually does

PIMMS tracks links and QR codes and shows which ones turn into results. The Zapier integration feeds it those results from the rest of your tools: when something happens in a form, a checkout or a CRM, Zapier hands PIMMS a conversion or a sale, so the numbers in PIMMS reflect what really happened downstream.

Three outcomes cover most setups. First, a lead recorded against its link: a form carries the click identifier in a hidden field, and Create Conversion sends it to PIMMS along with the customer reference. Second, revenue attributed to a campaign: a payment lands in your billing tool and Create Sale logs the amount, the customer and the payment processor. Third, one journey across both: because both actions take the same External ID (a customer ID or an email), the lead and the later purchase line up on the same person.

Now the limits, because they shape everything. PIMMS has no trigger on Zapier, so nothing that happens inside PIMMS can start a Zap. It has no search either, so a Zap can't look up a link or read back a statistic. The integration only writes into PIMMS, and the starting event always comes from another app.

If your stack runs on Make instead, the same app has its own page: PIMMS Make integration. For a side-by-side of the two platforms, see Make vs Zapier.

Vocabulary

Zapier vocabulary, in plain words

Seven words come back on every Zapier page. Here they are once, so the rest reads easily.

Zap
The automation you build on Zapier: one starting event, then one or more steps that run every time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it. PIMMS offers none, so another app plays this role.
Action
What the Zap does once it has started: the step that writes or sends something for you. Both PIMMS operations are actions.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
Polling vs instant
A polling trigger is checked on a timer for new items. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap continue only when what arrived meets a condition you set, and stops it the rest of the time.
Connection
Your PIMMS account linked to Zapier once, then reused by every step in every Zap that writes to PIMMS.
Cost

What it really costs you

PIMMS is not reserved for paid plans: it works on the free plan. What you spend depends on how many actions succeed.

  • Free plan100 tasks per month, unlimited Zaps
  • Steps on the free plan2 (one trigger, one action)
  • PIMMS on the free planYes, not a paid-only app
  • BilledEach successful PIMMS action

The trigger never costs a task, and neither does Zapier checking for new data. Each successful Create Conversion or Create Sale counts as one task; an action that fails is not counted. The catch: the free plan only builds two-step Zaps, one trigger and one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The check interval below applies to the trigger of the app that starts the Zap, not to PIMMS.

Connect

Connect PIMMS to Zapier in three steps

  1. 01

    Open your connections

    Go to the Apps page of your Zapier account and click + Add connection. You need an existing PIMMS account before you start: the connection links an account, it doesn't create one.

  2. 02

    Pick PIMMS

    In the dialog, type PIMMS in the search box, select it, then click Add connection. A new tab opens on the PIMMS side, where the actual sign-in happens.

  3. 03

    Sign in and grant access

    Log in to PIMMS in that tab and give Zapier access to the account. From then on, every Zap step that writes to PIMMS reuses this connection; you won't be asked again for the next Zap.

First Zap

Your first Zap: form lead to PIMMS conversion

GoalEvery form entry that carries a click identifier becomes a conversion in PIMMS, linked to the customer.

  1. 01

    Build: choose the starting app

    Start a new Zap and pick your form tool as the trigger, with its new-entry event. Since PIMMS has no trigger of its own, the first card always belongs to another app.

  2. 02

    Test the trigger

    Connect the form account and run the test. Zapier brings back the three most recent entries, so you can pick a real one that includes the hidden click field.

  3. 03

    Add a filter

    Click the plus icon, choose Filter, and set it to continue only when the click field holds a value. This makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add Create Conversion

    Add PIMMS as the action, pick Create Conversion, then map the click field into Click ID and the customer email into External ID. Use Configure & test to send one test event.

  5. 05

    Publish

    Click Publish to switch the Zap on. From that point, each new entry that passes the filter costs one task, and only when PIMMS accepts it.

Actions

The 2 PIMMS actions

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

1

Create Conversion

Action

In Zapier“Sends a new conversion event to Pimms to track conversions and measure performance.”

Records a conversion in PIMMS and ties it to the click that produced it, so a signup or a demo request counts toward the right link or QR code.

When to use it
a lead form, a trial signup or a booking tool should credit the campaign that sent the visitor.
Watch out
both Click ID and External ID are required, and the Click ID has to come from an earlier step such as a hidden form field.
2

Create Sale

Action

In Zapier“Sends a new sale event to Pimms to track sales and measure performance.”

Logs a purchase in PIMMS with its amount, the customer reference and the payment processor that handled it, so revenue shows up next to the links that drove it.

When to use it
a payment in your billing or store tool should count as a sale for the matching customer.
Watch out
the Amount field expects cents, so a value typed in whole units ends up 100 times too small.
When it breaks

When it breaks

Zapier attaches no help article to PIMMS, so the failures below come from how Zapier itself behaves.

PIMMS only receives what the starting app hands over, so when a conversion is missing, check the trigger first. For a broader method, start from the Zapier troubleshooting page.

  • Past events are not sent

    A Zap only reacts to what happens after you publish it. Leads and sales recorded before that day never reach PIMMS; moving that history is a separate job.

  • Bulk imports get held back

    If the starting app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can pause it instead of sending everything to PIMMS.

  • No duplicates from a polling trigger

    On a polling trigger, Zapier remembers what it has already seen, so the same entry doesn't create a second conversion in PIMMS.

  • Missing Click ID

    Create Conversion needs a Click ID from an earlier step. A form that doesn't carry it leaves the field empty, and the action can't go through.
Need help

Need help automating PIMMS with Zapier?

A person reads every message.

FAQ

PIMMS and Zapier: common questions

01Is the PIMMS Zapier integration free?
Yes, as long as the Zap stays at two steps. PIMMS is not one of the apps Zapier reserves for paid plans, so it works on the free plan, which gives you 100 tasks per month and unlimited Zaps. The catch is the shape of the Zap: the free plan allows one trigger and one action, nothing more. A form entry sent straight to Create Conversion fits. Add a filter, or send both a conversion and a sale from the same Zap, and it becomes a multi-step Zap that needs a paid plan.
02How many tasks does a PIMMS Zap use?
One task per PIMMS action that succeeds. The trigger in the other app costs nothing, and Zapier checking for new items costs nothing either. If your Zap runs Create Conversion once per form entry, each entry costs one task. A Zap that runs both Create Conversion and Create Sale uses two tasks per run when both work. An action that fails, for example because a required field arrived empty, is not counted against your plan.
03Does PIMMS on Zapier work in real time?
That depends entirely on the app that starts the Zap, because PIMMS has no trigger of its own. If the starting app offers an instant trigger, it reports the event to Zapier itself and the PIMMS action follows straight away, whatever your plan. If it uses a polling trigger, Zapier checks for new items on a timer: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. The editor shows a lightning bolt on instant triggers.
04What does it take to connect a PIMMS account?
A PIMMS account, and a few clicks. Open the Apps page of your Zapier account, click + Add connection, search for PIMMS and pick it, then click Add connection. Sign in to PIMMS in the tab that opens and grant Zapier access. If the Zap will touch data you don't own yourself, make sure your PIMMS account has the access it needs. The connection is then reused by every Zap that writes to PIMMS.
05Why does a PIMMS sale show the wrong amount?
Most likely because the amount was sent in whole units instead of cents. The Amount field of Create Sale expects cents, so a value of 5 is read as 5 cents rather than 5 in your currency. Check what your payment tool sends: if it already gives cents, map it as is; if it gives a decimal amount, it needs converting before it reaches PIMMS. Payment Processor and External ID are required too, so leave none of them empty.
06What if the PIMMS operation you want is not there?
Then it isn't available through this integration on Zapier. The editor offers exactly two operations for PIMMS, Create Conversion and Create Sale, both actions. There is no trigger, so PIMMS can't start a Zap, and no search, so a Zap can't read a link or a statistic back from PIMMS. Anything beyond logging conversions and sales has to happen inside PIMMS itself, or in another tool that offers the step you're after.
07Zapier, Make or n8n for PIMMS?
Pick by criteria rather than by brand. On Zapier, PIMMS is a write-only destination: two actions, no trigger, no search, and it runs on the free plan as long as each Zap stays at one trigger and one action. So the questions are where your forms and payment tools already live, how many steps your scenario needs, and whether a filter is part of it. If the answer involves several steps, budget for a paid plan or compare with the platform your team already uses.
Same platform

Other docs you might need on this stack.

Browse all integrations