Resources · Zapier integration

Plugnotes Zapier integrationAutomate Plugnotes with Zapier.

The Plugnotes Zapier integration gives you 2 triggers and 2 actions. Start a Zap when a PlugForm sends a Plugnote, write back into that record or attach a PDF to it, all on the free plan. Here is what each step costs and what tends to break.

See the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Plugnotes Zapier integration actually does

The Plugnotes Zapier integration links your Plugnotes account to Zapier, the tool that runs automations between apps. Each automation is called a Zap: one event starts it, then it runs the steps you lined up. Plugnotes can start a Zap through 2 triggers and receive work through 2 actions, and none of it needs a paid plan.

Three results people build with it. A PlugForm entry that reaches your other tools: New Plugnote starts the Zap when a PlugForm you subscribed to sends a Plugnote to Zapier, and the next step pushes it wherever your team works. A record that completes itself: Update Plugnote writes into fields, or into one table cell, of the Plugnote that just came in. A document filed in the right place: Add Annexe to a PN attaches a PDF to an existing Plugnote, so the paperwork sits next to the data.

What Zapier does not do here. It cannot create a Plugnote from scratch: both actions work on a Plugnote that already exists and ask for its ID. It cannot look a Plugnote up either, because the app offers no search step. And the annexe action takes a PDF only, sent as encoded text (base64).

The single most useful thing to know before you choose a trigger: New Plugnote is the only instant one of the two. It reacts right away even on the free plan, while Get Models waits for the interval of your plan. Comparing platforms first? See n8n vs Zapier and Make vs Zapier.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line of this page. Here they are in plain terms, once.

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. Once the Zap is switched on, Zapier waits for that event and for nothing else.
Action
What the Zap does once it has started: the step that writes, sends or moves something in an app on your behalf.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts exactly those.
Polling vs instant trigger
Polling: Zapier checks the app on a timer and keeps only new items. Instant: the app reports the event to Zapier itself, no waiting.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it in every other case.
Connection
Your Plugnotes account linked to Zapier once, then reused by every step of every Zap that works with Plugnotes.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter turns a Zap into one, and it then needs a paid plan.
Cost

What a Plugnotes Zap really costs

Plugnotes is not reserved for paid plans: it works on the free one. The bill is counted in tasks, and the trigger never costs a single one.

  • Trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month
  • Steps allowed on the free plan2 (one trigger, one action)

Each action that goes through counts as one task; an action that fails is not counted. Looking for new data is free too, however often Zapier checks. The free plan gives 100 tasks a month, but only Zaps of two steps. Add a filter or a second action and the Zap turns multi-step, which needs a paid plan. The interval grid below only concerns Get Models, since New Plugnote is instant and never waits for a check, whatever plan you are on.

Connect

Connect your Plugnotes 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 Plugnotes account first, plus access to any record you do not own that the Zap should read or change.

  2. 02

    Pick Plugnotes in the dialog

    Type Plugnotes in the search box of the dialog, select it in the results, then click Add connection. Zapier now hands you over to Plugnotes so you can sign in there.

  3. 03

    Sign in and grant access

    Sign in to Plugnotes in the tab that opens and grant Zapier access to the account. The connection is stored once, then every Zap step that touches Plugnotes reuses it.

First Zap

Your first Zap: update every new Plugnote

GoalEach time a PlugForm sends a Plugnote to Zapier, check it against a condition and write a value back into it.

  1. 01

    Build: choose the trigger

    Start a new Zap, choose Plugnotes as the app that starts it and New Plugnote as the event, then select the connection you added earlier.

  2. 02

    Set the model and the output

    Choose the PlugForm model to follow, then the data output. Direct Data hands you each field and table column ready to map; CSV Files only gives you the older download links.

  3. 03

    Test the trigger

    Run the test. Zapier brings back the three most recent Plugnotes of the connected account; pick a real one so the next steps are mapped on actual data.

  4. 04

    Add the filter

    Click the plus icon, add a Filter step, then set the field to check, the rule and the value. Use a text rule on text and a number rule on numbers, or it never passes.

  5. 05

    Add Update Plugnote

    Add Update Plugnote, choose the same model, map the Plugnote ID that the trigger returned, then decide what to update: fields, or a single table cell.

  6. 06

    Test, then publish

    Test the action once and read what came back, then publish the Zap to switch it on. With its filter this is a multi-step Zap, so it runs on a paid plan.

Triggers

Plugnotes triggers on Zapier

2 events start a Zap when something happens in Plugnotes, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

Get Models

Polling trigger

In Zapier“Triggers when PlugForm models are available.”

Starts a Zap when PlugForm models become available in your account, so another tool can keep its own list of the forms your team works with.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
when a catalogue of your models lives in a spreadsheet or a project tool and has to follow what exists in Plugnotes.
Watch out
Zapier remembers the models it has already seen, so one model starts the Zap once, never at every check.
2

New Plugnote

Instant trigger

In Zapier“Triggers when a Plugnote is sent to Zapier from a subscribed PlugForm.”

Fires when a PlugForm you subscribed to sends a Plugnote to Zapier. It is the natural entry point of a Plugnotes Zap, because the Plugnote ID it carries is what both actions ask for.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when each record from a field inspection or an intake form should reach a CRM, a sheet or a team chat without anyone retyping it.
Watch out
two settings are required, the model (Zapier mode enabled) and the data output, where Direct Data and the older CSV Files links give very different results.
Actions

Plugnotes actions on Zapier

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

1

Add Annexe to a PN

Action

In Zapier“Adds a base64-encoded PDF file as an annexe on an existing Plugnote.”

Attaches a PDF to a Plugnote that already exists, as an annexe, so a signed document or a generated report stays next to the record it belongs to.

When to use it
when a document tool produces one PDF per Plugnote and that file has to end up on the record.
Watch out
it asks for the Plugnote ID, a file name without extension and the PDF content encoded as base64 text.
2

Update Plugnote

Action

In Zapier“Updates fields or one table cell on an existing Plugnote owned by the connected user.”

Rewrites fields, or a single table cell, on a Plugnote that belongs to the account you linked. For a cell, you pick the table, the row and the column from menus.

When to use it
when an earlier step works out a status or a total and the Plugnote has to show it.
Watch out
the ID is the PN value from New Plugnote, written like PN1001 or 1-1001, and records owned by someone else stay out of reach.
When it breaks

When a Plugnotes Zap breaks

Zapier ties no help article to Plugnotes and lists no limit of its own for the app. What breaks is what breaks on any Zap, and four cases matter here.

  • No catch-up on older Plugnotes

    A Zap only reacts to what happens after you switch it on. Plugnotes sent before that are never picked up, and moving them is a separate job.

  • A Zap that keeps setting itself off

    A Zap that writes into the very place its own trigger watches fires again and again, and burns through your task count fast.

  • Flood protection after a bulk import

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

  • Get Models never sends an item twice

    On a polling trigger such as Get Models, Zapier keeps track of what it has seen, so the same model cannot start the Zap a second time.
Need help

Need help automating Plugnotes with Zapier?

A person reads every message.

FAQ

Plugnotes and Zapier: frequent questions

01Is the Plugnotes Zapier integration free?
Yes, it works on the free plan. Plugnotes is not reserved for paid plans, so both triggers and both actions are available without paying. The free plan gives 100 tasks a month and as many Zaps as you like, with one catch: each Zap is limited to two steps, one trigger and one action. New Plugnote followed by Update Plugnote fits inside that limit. Add a filter, or a second action such as Add Annexe to a PN after the update, and the Zap becomes multi-step, which requires a paid plan.
02How many tasks does a Plugnotes Zap use?
One per successful action, and nothing for the trigger. A Zap that starts on New Plugnote and runs Update Plugnote costs one task each time a Plugnote comes in. Put Add Annexe to a PN behind it and the same Plugnote costs two. An action that fails is not counted against the plan, and Zapier checking Get Models for new items costs nothing, however often it looks. With the 100 tasks a month of the free plan, a one-action Zap handles 100 Plugnotes.
03Is the Plugnotes integration real-time?
Only New Plugnote is. The app tells Zapier the moment a PlugForm sends a Plugnote, so the Zap starts right away on every plan, the free one included. Get Models works by polling instead: Zapier checks at a fixed interval set by your plan, every 15 minutes on Free, every 2 on Professional, every minute on Team and Enterprise. On paid plans that interval can be changed, and a check can also be run by hand from the editor. A Zap built on an instant trigger shows a lightning bolt in the editor.
04What does connecting Plugnotes to Zapier require?
A Plugnotes account, plus read or write access to anything you do not own that the Zap should touch. The link is made once, from the Apps page of Zapier with + Add connection: search Plugnotes, confirm, sign in to Plugnotes in the tab that opens and grant access. For New Plugnote, the model you pick has to be a PlugForm model with Zapier mode enabled. Update Plugnote only edits Plugnotes owned by the connected user, so connect the account that owns the records you plan to change.
05Which Plugnote ID does Update Plugnote expect?
The PN value returned by New Plugnote, written like PN1001 or 1-1001. Both actions depend on it: Update Plugnote to know which record to change, Add Annexe to a PN to know where to attach the PDF. Since Plugnotes offers no search step on Zapier, the ID cannot be found from a name or another value. In practice the Zap starts on New Plugnote, or receives the ID from an earlier step, and the record must belong to the connected user.
06What if the Plugnotes operation you need is missing?
Then this integration cannot do it, and that is worth knowing before building. On Zapier, Plugnotes offers four operations: Get Models and New Plugnote to start a Zap, Update Plugnote and Add Annexe to a PN to act on a Plugnote that already exists. There is no action that creates a Plugnote and no search step. If the missing piece belongs to the other side of the workflow, another app in the Zap may cover it; if it belongs to Plugnotes, the gap stays until the app adds that operation.
07Zapier, Make or n8n for Plugnotes?
It depends on the workflow, not on a ranking. On Zapier, Plugnotes brings an instant trigger that runs on the free plan, which suits a team that wants each new Plugnote sent to another tool with little setup. The limits are the criteria to weigh: no way to create a Plugnote, no search step, two-step Zaps on the free plan, and a bill counted per successful action. If one of those blocks your scenario, check what the other platforms offer for Plugnotes on those same criteria before choosing.
Same platform

Other docs you might need on this stack.

Browse all integrations