Resources · Zapier integration

Nightfall DLP Zapier integrationAutomate Nightfall DLP with Zapier.

Nightfall DLP Zapier integration: 0 triggers, 0 actions, 1 search. Zapier can hand Nightfall DLP a piece of text from another app and get it scanned and classified for sensitive data. Nothing else. How that works, why it needs a paid plan, and where it breaks.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Nightfall DLP Zapier integration does

Nightfall DLP spots and classifies sensitive data, to help with security and compliance. Zapier, an automation tool, can send it text from your other apps: a Zap (the automation you build) waits for an event elsewhere, then passes a piece of text to Nightfall DLP and uses the answer in the steps that follow.

Form entries checked on arrival. Scan for Sensitive Data takes the text of each new form entry and has it classified against the detection rule you pick, before a later step stores it anywhere.

A warning in your team chat. Followed by a filter and a chat message, the same scan can alert people when a result calls for it, based on a field you choose at the test.

Text from any app, one rule. Since the scan takes plain text, the trigger can be almost anything that carries some: a note, a message, a row. The rule stays the same Condition Set from your Nightfall Console.

What Zapier does not do here. Nightfall DLP has no trigger and no action on Zapier. Nothing in Nightfall DLP can start a Zap, and a Zap cannot write anything into it. Its one operation is a search step, which makes any Zap that uses it multi-step, so a paid plan is needed.

Weighing other tools for the same job? Open our n8n vs Zapier comparison.

Vocabulary

Zapier words in one minute

Eight words carry the rest of this page. Here they are in plain English.

Zap
The automation you build in Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts a Zap. With Nightfall DLP it always comes from another app, since Nightfall DLP has none.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan's count is a count of those.
Search step
A step that looks something up in an app and hands what it found to the next steps. Nightfall DLP's scan is one.
Polling vs instant
Polling: Zapier checks an app on a timer. Instant: the app calls Zapier itself. Here it depends on the trigger app you pick.
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, a filter or a search makes one, and it then needs a paid plan.
Cost

What a Nightfall DLP Zap costs

Nightfall DLP is not a premium app, yet a Zap that uses it needs a paid plan. The reason: its only operation is a search step, and a search makes the Zap multi-step.

  • Trigger cost0 tasks
  • Free plan100 tasks a month
  • Zap with a searchPaid plan
  • Premium appNo

The free plan gives 100 tasks a month and an unlimited number of Zaps, but each is limited to two steps: one trigger and one action, with no search. On a paid plan, every action that succeeds counts as a task, one that fails is not counted, and the trigger never costs anything. A few apps and actions take more than one task. The grid below applies when the trigger you pick is a polling one; Nightfall DLP has no trigger of its own.

Connect

Connect Nightfall DLP to Zapier in three steps

  1. 01

    Open the Apps page

    Sign in to Zapier and open the Apps page of your account. Click + Add connection, type Nightfall DLP in the search box of the dialog, and pick it from the results.

  2. 02

    Sign in to Nightfall DLP

    Click Add connection. A new tab opens on Nightfall DLP: sign in there with your Nightfall DLP account, then return to Zapier. You only sign in once: Zapier then keeps the account linked for your Zaps.

  3. 03

    Grant Zapier access

    Grant Zapier access to the account. What you need beforehand: an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection is then reused by every Nightfall DLP step.

First Zap

Your first Zap: scan form entries, warn the team

GoalScan the text of each new form entry with Nightfall DLP, then post a chat message when the result meets your condition.

  1. 01

    Start a new Zap

    In Zapier, start a new Zap. This is the build phase: you pick the app and event that start it, then the apps that follow, and map the fields between steps.

  2. 02

    Set the form trigger

    Pick your form tool and its new-entry event, then test it. Zapier brings back the three most recent items of the connected account, so you work from a real entry.

  3. 03

    Add Scan for Sensitive Data

    Add Nightfall DLP and pick Scan for Sensitive Data. Paste your Condition Set UUID, then map the entry text into Text Payload to Scan. A search step makes this Zap multi-step, on a paid plan.

  4. 04

    Add the filter

    Add a Filter step from the plus icon and fill its three boxes: the field to look at, the rule and the value. Pick the field from what the scan returned at the test. Like the search, a filter needs a paid plan.

  5. 05

    Add the chat message

    Add the action of your team chat and write the message, with the fields from the entry and the scan that help people act.

  6. 06

    Test, then publish

    Run each step once and read what came back. When the message looks right, click Publish to switch the Zap on. From then on, each new entry is scanned.

Searches

The Nightfall DLP search

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

A search step sits among the action events of the editor, at the bottom of the list under its own heading, SEARCH. Three settings decide what happens when it does not return exactly one result.

1

Scan for Sensitive Data

Search

In Zapier“Scan and classify sensitive data.”

Scan for Sensitive Data sends a piece of text to Nightfall DLP and gets it classified with the detection rule you name. Both fields are required: Condition Set UUID, the rule from the Nightfall Console, and Text Payload to Scan, the text itself.

When to use it
when text from a form, a message or a note should be checked before a later step files or shares it.
Watch out
see at the test what the scan returns before you map it.

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 there, 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?
    On apps that offer it, this box turns a search into a find-or-create. Nightfall DLP offers no such variant, so this setting does not come into play here.
  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 hand all of them on at once.
When it breaks

When a Nightfall DLP Zap breaks

Zapier ties no help article to Nightfall DLP, so the cases below are the general limits of any Zap, applied to one built around a scan.

Each card names a limit and the move that avoids it. If a Zap still misbehaves, see our Zapier troubleshooting guide.

  • Old entries are never scanned

    A Zap only reacts to what happens after it is switched on. Text that already sat in the trigger app is not sent to Nightfall DLP; scanning it is a separate job.

  • When the search finds nothing

    With the default setting, a search that finds nothing stops the Zap and the steps after it are skipped. Switch on the first setting if the Zap should carry on.

  • A huge batch can be held back

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

  • A Zap that feeds itself

    A Zap that writes into the very place its own trigger watches can set itself off again and again, and burn through your task count fast.
Need help

Need help automating Nightfall DLP with Zapier?

A person reads every message.

FAQ

Nightfall DLP and Zapier: questions people ask

01Is the Nightfall DLP Zapier integration free?
No: every Zap that uses Nightfall DLP needs a paid plan. Nightfall DLP is not a premium app, but its only operation on Zapier, Scan for Sensitive Data, is a search step. A Zap with a search is a multi-step Zap, and multi-step Zaps need a paid plan. The free plan stops at two steps, one trigger and one action, with no search. It still gives 100 tasks a month and an unlimited number of Zaps for your other apps.
02How many tasks does a Nightfall DLP Zap use?
The trigger never costs a task, whatever app it comes from, and Zapier checking that app for new items costs nothing either. Each action that succeeds after the scan counts as one task, so in a Zap that scans text and then posts a chat message, each message sent counts as a task. An action that does not go through is not counted. A few apps and a few actions take more than one task, so check the steps you add.
03Can a Nightfall DLP Zap run in real time?
That depends on the app that starts it, because Nightfall DLP has no trigger on Zapier. If the trigger app reports its events itself, the trigger is instant and the Zap starts right away whatever the plan; the editor shows a lightning bolt on such a Zap. If it is a polling trigger, Zapier checks at the plan interval: 2 minutes on Professional, 1 on Team and Enterprise, 15 on Free. The app page on Zapier shows the interval on each polling trigger.
04What do you need to connect Nightfall DLP to Zapier?
An account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection starts from the Apps page of your Zapier account with + Add connection: you pick Nightfall DLP, sign in in the tab that opens and grant Zapier access. Every Nightfall DLP step then reuses that connection. For the scan itself, keep your Condition Set UUID from the Nightfall Console at hand.
05Why does every Nightfall DLP Zap need a paid plan?
Because Scan for Sensitive Data is a search step, and a search makes any Zap multi-step. Even the shortest possible Zap, a trigger from another app followed by the scan, goes beyond one trigger and one action in Zapier's sense. Add the step that uses the result, a message or a row, and it is clearer still. Nightfall DLP itself is not a premium app; the plan requirement comes from the type of step, not from the app.
06What if the Nightfall DLP operation you need is not there?
Then Zapier cannot do it with Nightfall DLP today. The Nightfall DLP page on Zapier shows the current set of operations; on the date of this page it holds one search, Scan for Sensitive Data, and no trigger or action. So a Zap cannot start from an event in Nightfall DLP, nor change anything there. What it can do is send text in and act on the answer in your other apps.
07Zapier, Make or n8n for Nightfall DLP?
There is no single winner, so decide on criteria. Start with the connection: check that the tool you are eyeing offers Nightfall DLP as a ready-made app in its catalog, and which operations it covers. Then cost: on Zapier, any Zap with the Nightfall DLP scan needs a paid plan, since the scan is a search step. Then timing: the trigger comes from another app, so its own type decides how fast the Zap reacts.
Same platform

Other docs you might need on this stack.

Browse all integrations