Resources · Zapier integration

Pascal Zapier integrationAutomate Pascal with Zapier.

The Pascal Zapier integration gives you 0 triggers, 6 actions and 1 search. Pascal cannot start an automation by itself, but any other app can hand it a person or a company to screen, then ask it to email a PDF case report.

See the 7 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Pascal Zapier integration actually does

Pascal is a KYC and KYB tool: it checks people and companies against sanctions lists, politically exposed persons and negative press. Plugged into Zapier, it becomes the place where names land for screening. Something happens in another tool, and Pascal opens a case, updates one, or sends you a report.

Three results come up again and again. First, a screening case opened by itself: a new contact shows up in your intake tool, and Create a Person Case files that name in Pascal without anyone copying it over. Second, the same thing for companies: a new supplier or customer account becomes a business case through Create a Business Case. Third, a paper trail on demand: Generate & Email a Case Report builds a PDF of one or more cases and sends it by email, which is handy when compliance wants a file rather than a dashboard.

Around those, Create a Client and Update a Client keep your client records in line with the rest of your stack, Update a Case changes the details or status of a case already open, and Find a Case fetches one by its ID.

Now what Zapier does not do here. Pascal has no trigger at all, so a new hit or a status change inside Pascal cannot set anything off in another app. Zapier cannot tell your CRM that a person was flagged. There is no delete operation either: closing out old records stays a job for the Pascal interface.

If you are weighing other platforms for the same job, the two comparisons sit here: n8n vs Zapier and Make vs Zapier.

Vocabulary

Zapier vocabulary in one minute

Eight words carry the rest of this page. Each one gets a plain definition here, then the page uses it without explaining it again.

Zap
The automation you build on Zapier: one trigger, followed by one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for that event to come up.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you, such as opening a case in Pascal.
Task
The unit Zapier bills. One task is one action that your Zap completes successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself, the moment the event happens.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it there otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can reuse what it found.
Connection
Your Pascal account linked to Zapier once, then reused by every step of every Zap that talks to Pascal.
Cost

What a Pascal Zap really costs

Pascal is not one of the apps Zapier keeps for paid plans: it works on the free plan. The catch sits elsewhere, in the number of steps.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan stepsOne trigger and one action, nothing more
  • Pascal on free planYes, it is not reserved for paid plans
  • BilledEach successful action, never the trigger

Only a successful action costs a task. The trigger never does, and neither does the checking Zapier performs to spot new data. An action that fails is not counted. Each action that succeeds counts on its own, so a Zap that opens a case and then emails a report burns two tasks per run. The free plan stops at two steps, one trigger and one action. Add a filter, a search such as Find a Case, or a second action, and you have a multi-step Zap, which needs a paid plan. Since Pascal has no trigger, the interval below applies to the trigger of the other app.

Connect

Connect your Pascal account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to the Apps page and click + Add connection. You need a Pascal account first, plus access to any case or client you did not create yourself and want the Zap to touch.

  2. 02

    Pick Pascal

    Type Pascal into the search box of the dialog, select it in the list, then confirm with Add connection. A new tab opens on the Pascal side so you can prove the account is yours.

  3. 03

    Sign in and grant access

    Sign in to Pascal in that tab and allow Zapier to use the account. The connection then shows up on the Apps page, and every Zap that uses Pascal picks it from a list instead of asking again.

First Zap

Your first Pascal Zap, step by step

GoalEvery new person submitted through your intake form gets a screening case in Pascal, but only when the submission meets your condition.

  1. 01

    Build the trigger

    Start a new Zap and pick the app that collects people, then its event for a new entry. Pascal cannot be the trigger here, since it has none, so the Zap always begins in another tool.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items from the connected account, so you build the rest on a real submission instead of an empty template.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, then set the field, the rule and the value. Pick a text rule for text and a number rule for numbers, or the filter never lets anything through.

  4. 04

    Add Create a Person Case

    Choose Pascal, then Create a Person Case. Map the name from the form into Case Name, and fill Case Type and Case Confidence, which are both mandatory.

  5. 05

    Test, then publish

    Test the Pascal step and open the case it created to check it. Then click Publish to switch the Zap on. With the filter, this is a multi-step Zap, so it runs on a paid plan.

Actions

The 6 Pascal actions

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

1

Create a Client

Action

In Zapier“Create a new client in Pascal.”

Adds a new client record to Pascal, so cases opened later have a home to hang on. Only the name is required.

When to use it
a deal moves to signed in your CRM and the client needs to exist in Pascal before any screening starts.
Watch out
the name is capped at 255 characters, so a long legal name pulled from another tool can fail the step.
2

Generate & Email a Case Report

Action

In Zapier“Generate a PDF case report and email the report to the API user's email address”

Builds a PDF covering one or more cases and emails it to the address of the user behind the connection. You choose which pages go in and whether the report is detailed.

When to use it
an auditor or a partner bank asks for proof of screening and you want the file without exporting by hand.
Watch out
it wants case UUIDs, so an earlier step has to carry them.
3

Create a Person Case

Action

In Zapier“Create a new person case in Pascal. If a matching case already exists, the system will automatically reuse the existing case instead of creating a duplicate.”

Opens a screening case for an individual. If a matching case is already there, Pascal reuses it rather than creating a duplicate.

When to use it
a new customer finishes onboarding in your signup tool and must be checked before the account goes live.
Watch out
Case Confidence set to Exact only finds hits when every filled field matches, while Relative accepts partial matches.
4

Create a Business Case

Action

In Zapier“Create a new business case in Pascal. If a matching case already exists, the system will automatically reuse the existing case instead of creating a duplicate.”

The company version of the person case: it files an organisation for screening, and again reuses an existing case instead of doubling it.

When to use it
procurement adds a new supplier to its list and the company needs a KYB check before the first purchase order.
Watch out
the case name must be between 2 and 255 characters, so empty or one-letter values coming from a form will fail.
5

Update a Case

Action

In Zapier“Edit the specifications or status of an existing case. Only fields provided will be updated, fields that are not provided will remain in the current state. Will return the updated case information.”

Edits the details or the status of a case already open. Fields you leave blank keep their current value, and the step returns the updated case.

When to use it
a customer corrects their details in your portal and the screening case should follow.
Watch out
no Case ID, no update. When no earlier step carries that ID, put Find a Case in front of it.
6

Update a Client

Action

In Zapier“Edit the specifications of an existing client.”

Changes the details of an existing Pascal client, so the record stays in step with the system where the client really lives.

When to use it
a company renames itself in your accounting tool and you want Pascal to show the same name.
Watch out
the Client ID is mandatory, and the step cannot look a client up by name on its own.
Searches

The Pascal search

1 search step looks for data that already exists in Pascal, so a later step can use it.

A search step fetches something that already exists so the next steps can use it. In the editor, searches sit at the bottom of the Action event list, under the SEARCH heading. Some action fields also offer + Add search step, which inserts one just before and wires the result in for you. Three settings decide what happens when the result is not clean.

1

Find a Case

Search

In Zapier“Find a case in Pascal using its ID or UUID.”

Looks up a single Pascal case from its ID or its UUID and hands its details to the steps that follow. The Case ID field is required.

When to use it
a ticket in your helpdesk carries a case reference, and you want to refresh that case or send its report.
Watch out
it only searches by identifier, so a name or an email address will not find anything.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap, and the steps that depended on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into find-or-create. Pascal exposes no find-or-create variant for its search, so a missing case is never created this way.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When a Pascal Zap breaks

Zapier attaches no help article to Pascal, and no limit specific to the app has been recorded. What breaks is the general Zapier behaviour, and it bites harder on a compliance tool.

Four cases are worth knowing before you switch the Zap on. When one of them shows up, the Zapier troubleshooting page is the place to start.

  • Old contacts are never screened

    A Zap only reacts to what happens after it is switched on. People already sitting in your form or CRM stay out of Pascal until you move that backlog separately.

  • The Zap feeds itself

    If a Zap writes into the very place its own trigger watches, it sets itself off again and again and drains the task count fast.

  • A bulk import gets held back

    When the trigger app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold the batch back.

  • No double start on a polling trigger

    Zapier remembers what it has already seen on a polling trigger, so the same record does not start the Zap twice and open a second run.
Need help

Need help automating Pascal with Zapier?

A person reads every message.

FAQ

Pascal Zapier integration: frequent questions

01Is the Pascal Zapier integration free?
Yes, on the Zapier side Pascal runs on the free plan, because Zapier does not reserve it for paid plans. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: one trigger and one action. That covers a Zap where a form opens a Pascal case. The moment you add a filter, a second action such as emailing a report, or the Find a Case search, the Zap becomes multi-step and needs a paid plan. Your Pascal subscription is a separate matter that this page does not cover.
02How many tasks does a Pascal Zap use?
One task per Pascal action that completes successfully, and nothing for the trigger. A Zap that opens a person case uses one task per run. A Zap that opens a case and then emails a case report uses two, because each successful action is counted on its own. An action that fails is not counted. Zapier checking the other app for new items costs nothing either, however often it looks. Keep in mind that a few apps and actions take more than one task when they complete, so the count on your plan is the one to watch.
03Does Pascal work in real time with Zapier?
It depends on the trigger of the other app, because Pascal has no trigger of its own. If that app reports its events instantly, the Pascal action runs straight away, whatever the plan. If its trigger is a polling one, Zapier checks 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 Zaps built on an instant trigger, so you can tell which case applies before you publish.
04What does it take to connect Pascal to Zapier?
A Pascal account, and access to any case or client you did not create yourself but want the Zap to change. The connection takes three moves: open the Apps page of Zapier and click + Add connection, search for Pascal and confirm with Add connection, then sign in to Pascal in the tab that opens and grant access. After that, every Zap reuses the same connection from a list, so you only do it once per account.
05Why does Create a Person Case not open a new case every time?
Because Pascal reuses a matching case when one already exists, instead of creating a duplicate. The same goes for Create a Business Case. So when the same person is submitted twice, Pascal keeps one case and the Zap still reports success. There is also a Case Deduplicate setting that skips cases already present in the organisation. If you expected a fresh case for every submission, check those two behaviours before assuming the Zap failed.
06What if the Pascal operation you want is not in Zapier?
Then it is not available through Zapier today. The editor offers exactly six actions and one search for Pascal, and no trigger. That rules out reacting to a new hit inside Pascal, and there is no delete. The workable path is to build around what exists: let another app start the Zap, use Find a Case to fetch a case by its ID, and Update a Case to change it. Anything outside those seven operations stays in the Pascal interface.
07Zapier, Make or n8n for Pascal?
Decide on criteria, not on reputation. On Zapier, Pascal offers six actions and one search, works on the free plan for two-step Zaps, and needs a paid plan as soon as you add a filter or a second step. So ask yourself three things: does your Zap need more than one step, which app will start it given that Pascal cannot, and do you need an operation outside those seven. Then check whether the other platform covers that same list before you choose.
Same platform

Other docs you might need on this stack.

Browse all integrations