Pima Zapier integrationAutomate Pima with Zapier.
The Pima Zapier integration offers 7 triggers, 0 actions and 0 searches. All seven are instant: a new request, an agreement sent, viewed or signed, or a document opened tells your other tools straight away. Pima starts Zaps, and other apps do the work.
Verified Trustpilot reviews · AI, automation & growth agency
What the Pima Zapier integration does for you
Pima helps companies handle incoming requests for security documents, get NDAs signed by prospects and share watermarked reports when asked. Connected to Zapier, every step of that process becomes a signal: Pima tells Zapier what just happened, and your CRM, chat or spreadsheet reacts without anyone watching the Pima dashboard.
Three results you can build, each from a real trigger:
No security request left waiting. New Request fires when a request is created, and the next step posts it in the channel where your security or sales team already works.
Deals that move when the NDA is signed. Agreement Signed starts a Zap the moment a prospect signs, so the deal in your CRM can move forward without a rep checking Pima first.
A signal when a prospect opens your material. Document Viewed and Agreement Viewed tell the account owner that the report or the agreement has been opened, which is the right time for a follow-up.
What Zapier does not do here: Pima has no action and no search on Zapier, so a Zap (the word is explained below) cannot send an agreement, share a document or look anything up in Pima. It only listens. Everything the Zap does happens in other apps, and only events after you switch it on are picked up.
Still comparing platforms? The Make vs Zapier comparison is a good next read.
Zapier terms in plain English
A few Zapier words come back on every line below. Here they are, one line each.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap, like an NDA signed in Pima. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or updates something. With Pima, actions live in other apps.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan allowance is a count of those.
- Instant vs polling trigger
- Instant: the app tells Zapier the moment the event happens. Polling: Zapier checks on a timer. All seven Pima triggers are instant.
- Filter
- A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your Pima account linked to Zapier once, then reused by every Zap that starts from a Pima trigger.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes one, and it needs a paid plan.
What Pima on Zapier costs you
Pima is not a premium app, so its triggers work on the free plan. Since Pima only starts Zaps, the bill depends on what you do afterwards.
- Pima trigger firing0 tasks
- Each successful action elsewhere1 task
- Free plan100 tasks a month, unlimited Zaps, two steps per Zap
- Premium appNo, Pima works on the free plan
A Pima trigger firing never costs a task. What counts is each action in another app that completes, such as the chat message or the CRM update; a failed action is not charged. The free plan builds two-step Zaps only: a Pima trigger plus one action fits. Add a filter, for example to keep only some agreements, or a second action, and the Zap turns multi-step, which needs a paid plan. All seven triggers are instant, so the interval grid below never slows them on any plan.
Connect your Pima account to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need an existing Pima account; Zapier connects to it but never creates one for you.
- 02
Pick Pima
Search for Pima in the dialog, select it and click Add connection. A new tab opens on the Pima sign-in page, where you sign in with your usual Pima login.
- 03
Sign in and grant access
Sign in to Pima in that tab and give Zapier access to the account. Every Zap that starts from a Pima trigger then reuses this one connection, with nothing to set up again.
Build your first Pima Zap
GoalMove the deal forward in your CRM when a prospect signs an agreement, but only for the agreements you care about.
- 01
Pick the trigger
Create a Zap, choose Pima and the Agreement Signed event, then select your Pima connection. The trigger is instant, so no interval applies to it.
- 02
Test on a real agreement
Run the test. Zapier brings back the three most recent items from your Pima account, so you map the next steps on a real signed agreement, not an empty one.
- 03
Add a filter
Add a Filter step from the plus icon, then set the field, the rule and the value. A text rule only works on text. The filter makes the Zap multi-step, so it needs a paid plan.
- 04
Add the CRM step
Add your CRM and its update action, then map what the Pima trigger brought into the deal you want to move. Test the step once and check the deal.
- 05
Publish
When every step works, click Publish to switch the Zap on. Agreements signed before that moment are not sent; only new signatures start it.
Pima triggers on Zapier
7 events start a Zap when something happens in Pima, and 7 of them are instant: the app calls Zapier straight away, whatever your plan.
Agreement Sent
Instant triggerIn Zapier“Triggers when a new agreement is sent.”
A new agreement leaves Pima for a prospect, and the Zap starts with it. It marks the beginning of the NDA stage, before anyone has opened or signed anything, which makes it the right place to record that a deal has entered due diligence.
Agreement Signature Transferred
Instant triggerIn Zapier“Triggers when an agreement signature is transferred.”
This trigger reacts when the signature on an agreement is transferred in Pima. It covers an edge of the signing process the other triggers do not, so keep it for Zaps where that specific change has to be recorded.
Agreement Viewed
Instant triggerIn Zapier“Triggers when an agreement is viewed.”
Your prospect opens an agreement in Pima, and Zapier hears about it on the spot. It tells you the NDA has reached a real person, which is often the moment a nudge works best.
Document Sent
Instant triggerIn Zapier“Triggers when a new document is sent.”
Each time Pima sends a new document out, such as a watermarked security report, the Zap starts. It gives your team a record of what Pima shared, kept outside Pima where everyone can see it.
Document Viewed
Instant triggerIn Zapier“Triggers when a document is viewed.”
Someone opens a document shared through Pima, and the Zap starts right then. It is the clearest sign that your report is actually being read, not just sitting in an inbox.
New Request
Instant triggerIn Zapier“Triggers when a new request is created.”
A new request is created in Pima, typically a prospect asking for your security documents, and the Zap fires with it. This is where the whole Pima process starts, so it is the trigger to automate first.
Agreement Signed
Instant triggerIn Zapier“Triggers when an agreement has been signed.”
An agreement has been signed in Pima, and the Zap starts with that agreement in hand. This is the event most worth automating, since it unlocks the next stage of the deal.
When a Pima Zap breaks
Zapier attaches no help article and no documented limit to Pima. What goes wrong comes from Zapier's general rules, and from the fact that Pima only listens.
Four cases come back most often. None of them shows up as a red error, which is why it pays to know them before you publish. For everything else, the Zapier troubleshooting page is the place to go.
Past agreements are never sent
A Zap only reacts to what happens after it is switched on. Agreements and documents already in Pima are not picked up, and moving that history is a separate job.A loop through another app
If a later step writes into a place that also starts the Zap, it can set itself off again and again and burn through your task count fast.A big wave gets held back
When a huge batch of events arrives at once, after a mass send for example, Zapier's flood protection can hold the batch back instead of running everything.Expecting the Zap to act inside Pima
Pima has no action and no search on Zapier. A Zap that is meant to send the next document after a signature cannot do it: that step stays manual in Pima.
Need help automating Pima with Zapier?
A person reads every message.
