Paradym Zapier integrationAutomate Paradym with Zapier.
Paradym Zapier integration: 1 trigger, 3 actions, no search step. Zapier reacts the moment a person passes a verification in Paradym, the tool that issues digital identity documents and checks them, and can create offers, verification requests and read results. Free plan included.
Verified Trustpilot reviews · AI, automation & growth agency
What the Paradym Zapier integration actually does
The Paradym Zapier integration links Paradym, a service that issues digital identity documents and verifies the people who present them, to Zapier, a service that runs automations between apps. Paradym can start a Zap when someone is verified, and it can be told to issue a credential offer, ask for a verification, or read a result.
Three outcomes it is made for. An onboarding that unlocks itself: when New Verification Response reports a verified person, Get Verification Result reads what they presented, and the next step opens their account or updates their file in your CRM. Credentials handed out from your own tools: a completed course, an approved membership or a signed contract leads to Create Issuance Offer, so the person receives a digital credential without anyone in your team doing it by hand. Verification on demand: a new booking or a sensitive request triggers Create Verification Request, and the person is asked to prove who they are before anything moves.
What Zapier does not do here. The only trigger is a verified response: a refused or abandoned verification, or a newly issued credential, starts nothing. There is no search step. Nothing revokes a credential, edits a template or creates a project. And every operation works inside a Paradym project that has to exist first, with its templates already set up in Paradym itself.
Zapier words you will meet on this page
Seven terms, one line each. The rest of the page uses them without explaining again.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
- Trigger
- The event in an app that starts the Zap, here a verified response in Paradym. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once it has started: the step that writes, sends or fetches something for you, like a verification request.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Instant vs polling
- An instant trigger is reported by the app the moment it happens; a polling one is checked by Zapier on a timer. Paradym's is instant.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
What a Paradym Zap really costs
Paradym is not reserved for paid plans on Zapier, so it works from the free plan. The trigger never costs a task, and since it is instant, the plan's check interval does not slow it down.
- Tasks on the free plan100 per month
- Zaps on the free planUnlimited
- Steps on the free plan1 trigger + 1 action
- Delay on the Paradym triggerNone, it is instant
You pay in tasks: every action that succeeds counts once, and one that fails is not counted. Reading a result with Get Verification Result is an action, so it counts like the others. A Zap that reads the result and then updates your CRM spends two tasks per verified person. The free plan stops at two steps, one trigger and one action, so that kind of Zap needs a paid plan. The trigger itself stays free, however many people Paradym verifies.
Connect your Paradym account to Zapier
- 01
Open your connections
In your Zapier account, go to the Apps page and click + Add connection. A connection is your Paradym account linked to Zapier once, then reused by every step that uses Paradym.
- 02
Pick Paradym
In the dialog that opens, type Paradym in the search box and select it in the results. Then click Add connection, and Zapier opens a new tab for the sign-in.
- 03
Sign in and grant access
Sign in to Paradym in that tab and allow Zapier to use the account. You need a Paradym account, plus read or write rights on any project you do not own and want the Zap to touch.
Your first Zap: act on every verified person
GoalWhen someone is verified in Paradym, read what they presented and update their record in your CRM.
- 01
Set the trigger
In the Build step, pick Paradym and New Verification Response, choose your connection, then the Project to watch. This is the instant event that starts each run.
- 02
Test it on a real response
Run the trigger test. Zapier brings back the three most recent verified responses of the account, and you pick one so the mapping below uses real data.
- 03
Read the result
Add Get Verification Result. Pick the same Project and map the Verification Session from the trigger, so the step fetches what that person presented.
- 04
Update your CRM
Add the action of your CRM and map the values Paradym returned. With two actions, the Zap is multi-step, so it needs a paid plan and costs two tasks per run.
- 05
Test each step, then publish
Run each action once and read what came back. Then click Publish to switch the Zap on. The Zapier training covers mapping between steps.
The Paradym trigger on Zapier
1 event starts a Zap when something happens in Paradym, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Verification Response
Instant triggerIn Zapier“Triggered when a verification results in a verified response from the user.”
Starts the Zap each time a verification in one of your Paradym projects ends with a verified response from the person. Only successful checks count: the Zap hears about the people who proved what was asked of them.
Paradym actions on Zapier
Paradym gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Issuance Offer
ActionIn Zapier“Creates a OpenID4VC issuance offer for the selected credentials.”
Prepares an offer for a digital credential, built from one of your Credential Templates, so the person it is meant for can collect it.
Create Verification Request
ActionIn Zapier“Creates a OpenID4VC verification request for the selected presentation template.”
Opens a new verification request based on a Presentation Template, which sets what the person must show.
Get Verification Result
ActionIn Zapier“Retrieves presented data attributes from OpenID4VC verification session by its id.”
Fetches the details a person presented during a verification session, identified by that session, so later steps can use them.
When a Paradym Zap breaks
Zapier ties no help article to Paradym, so the traps below are the general ones, read through what this app can and cannot do.
An instant trigger removes the waiting, not the other surprises. Check these cases first, then Zapier troubleshooting if a run still fails.
Past verifications are not replayed
A Zap only reacts to what happens after you switch it on. People verified before that are not sent through, and handling that backlog is a separate job.A Zap that sets itself off
A Zap that writes into the very place its own trigger watches starts itself again and again, and burns through the task count fast.A burst of verifications
A trigger that suddenly sends a huge batch, after a campaign or a migration, can be held back by Zapier's flood protection.Wrong project, silent Zap
The trigger and every action are tied to one Project. A Zap set on a test project stays quiet while real verifications happen elsewhere.
Need help automating Paradym with Zapier?
A person reads every message.
