Resources · Zapier integration

PageProof Zapier integrationAutomate PageProof with Zapier.

The PageProof Zapier integration gives you 9 triggers, 0 actions and 0 searches. Every one of them is instant: an approval, a returned to-do list or a reviewer decision in PageProof starts your Zap right away, and the work happens in your other tools.

See the 9 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the PageProof Zapier integration actually does

It links PageProof, where your team reviews and signs off creative work, to Zapier, the tool that chains apps without code. You build a Zap (one starting event, then the steps after it) and PageProof plays one role only: it starts the Zap when something happens on a proof.

Three results people build first. A sign-off alert: New Proof Approved starts a Zap that posts a message in the channel where the account manager is waiting to ship the file. A rework queue: New To-Dos Requested opens a task in your project tool each time a gatekeeper or the approver sends a proof back with changes. A review log: Reviewer Decision Made writes each decision as a row in a sheet, so a project lead can see who decided what without opening every proof.

What Zapier does not do here. PageProof has no actions and no searches on Zapier: a Zap cannot create a proof, add a reviewer, approve a file or look one up. It only listens. Every step after the trigger runs in another app, which also means the free plan leaves room for exactly one of them. And a Zap never goes back in time: approvals given before you switch it on stay out of it.

If you are still choosing a platform, the Zapier review covers the tool as a whole, and Make vs Zapier puts it side by side with Make.

Vocabulary

Zapier words in one minute

Seven words come back on every line of this page. Here they are once, in ordinary language.

Zap
The automation you build on Zapier: one starting event, then one or more steps that run each time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Here, every trigger is a PageProof event.
Action
What the Zap does once it has started: the step that writes, sends or moves something. With PageProof, it lives in another app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Instant vs polling
An instant trigger is reported by the app itself, with no wait. A polling trigger is checked by Zapier on a timer.
Filter
A step that lets the Zap carry on only when what arrived meets a 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.
Cost

What it really costs to run

PageProof is not a premium app on Zapier, so it works from the free plan. What you pay for is the actions in your other tools.

  • Premium appNo, free plan works
  • Trigger0 tasks
  • Successful action1 task each
  • Free plan100 tasks a month, 2 steps

The trigger never costs a task, so a PageProof event on its own is free. Each action that succeeds counts as one task, and a failed one is not counted. The free plan gives you 100 tasks a month and builds two-step Zaps only: one trigger, one action. Add a filter or a second action and you need a paid plan. The interval grid below is the one for polling triggers; all nine PageProof triggers are instant, so it does not apply to them on any plan.

Connect

Connect PageProof to Zapier in 3 steps

  1. 01

    Open your Apps page

    In Zapier, go to the Apps page of your account. That is where every connection lives: your account of an app, linked once, then reused by every Zap that needs it.

  2. 02

    Add the connection

    Click + Add connection, type PageProof in the dialog, pick it, then click Add connection. You need a PageProof account, plus access to the proofs you want the Zap to follow if you do not own them.

  3. 03

    Sign in and grant access

    Sign in to PageProof in the tab that opens and let Zapier access the account. From then on, any Zap picks this connection from a list instead of asking for your login again.

First Zap

Your first Zap: log every approved proof and tell the team

GoalWhen a proof is approved in PageProof, add a row to the delivery sheet and post a message in the team channel.

  1. 01

    Build: pick the trigger

    Create a Zap, choose PageProof, then the New Proof Approved event, and select your PageProof connection. Testing comes next, so pick the account that actually receives client approvals.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items from your account, so you map the next steps on a real approval, not a blank example.

  3. 03

    Add the sheet row

    Add the spreadsheet step and map what PageProof sent into the columns of your delivery sheet. Choose one column per piece of information you want to keep for each delivery.

  4. 04

    Add the message

    Add a third step that posts in the team channel. With it, the Zap becomes multi-step and needs a paid plan. On the free plan, stop at the sheet row and skip this step.

  5. 05

    Test, then publish

    Test each step once and read what came back. When it looks right, click Publish to switch the Zap on. From then on, each approval starts it right away.

Triggers

The 9 PageProof triggers

9 events start a Zap when something happens in PageProof, and 9 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Proof Approval Withdrawn

Instant trigger

In Zapier“Triggers when an approval on a proof is withdrawn.”

Starts your Zap when an approval that had been given on a proof is taken back. It is the event that tells you a file you thought was cleared is no longer cleared.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
warning the print buyer or the media planner before a withdrawn banner goes out with the old sign-off.
Watch out
if another Zap already pushed the approved file somewhere, this one does not undo that step; it only gives you the alert.
2

New Proof Approved

Instant trigger

In Zapier“Triggers when a proof is approved.”

Runs each time a proof gets its approval in PageProof. It is the cleanest signal that a piece of artwork, video or page is ready to move on to the next stage.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
telling the account manager in their channel that the client has signed off, so delivery starts without anyone chasing.
Watch out
pair it with New Proof Approval Withdrawn if downstream steps act on the approval, or a reversal goes unnoticed.
3

New Proof Deleted

Instant trigger

In Zapier“Triggers when a proof is deleted from PageProof.”

Fires when someone removes a proof from PageProof. Use it to keep the rest of your stack in line with what still exists in the review tool.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
closing the matching card in your project board, so the team does not keep waiting on a review that no longer exists.
Watch out
the proof is already gone when the Zap runs, so build later steps on what the trigger hands over, not on reopening the proof.
4

New Proof Started

Instant trigger

In Zapier“Triggers when a proof's workflow is started.”

Kicks in when the review workflow of a proof begins. Uploading a file is one moment; this is the moment reviewers are actually set loose on it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
stamping a start date on the job in your traffic sheet, so the studio can see how long rounds of review take.
Watch out
proofs whose workflow began before the Zap was published will never come through, so the sheet starts from that day.
5

New To-Dos Requested

Instant trigger

In Zapier“Triggers when a proof's to-do list is returned by a gatekeeper or the approver.”

Goes off when a gatekeeper or the approver sends a proof back with its list of to-dos. In plain terms: the file needs changes before it can be approved.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
creating a rework task for the designer in your project tool, so the change request does not sit in an inbox.
Watch out
a proof sent back more than once starts the Zap each time, so expect one new task per round of changes.
6

New Proof To-Dos Reverted

Instant trigger

In Zapier“Triggers when to-dos are reverted for a proof.”

Reacts when the to-dos on a proof are reverted, meaning the change request is pulled back. It is the counterpart of New To-Dos Requested.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
notifying the designer that the rework they were handed is off, before they spend the afternoon on it.
Watch out
without a matching Zap on the request side, the rework task you opened earlier stays open in your project tool.
7

Reviewer Decision Made

Instant trigger

In Zapier“Triggers when a reviewer makes a decision”

Starts the Zap each time one reviewer makes a decision on a proof. Where New Proof Approved waits for the proof as a whole, this one follows each person.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keeping a decision log in a sheet for a regulated sign-off, where you need to show who decided and when.
Watch out
on a proof with many reviewers it runs once per person, so each action behind it costs a task each time.
8

Reviewer Nudged

Instant trigger

In Zapier“Triggers when a nudge is sent to a reviewer on a proof”

Fires when a reminder, a nudge, is sent to a reviewer on a proof. It tells you a review is late enough that someone had to chase it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
sending the same reminder by direct message, for a client contact who lives in chat rather than in email.
Watch out
a reviewer nudged several times starts the Zap each time, so a second channel can feel like spam fast.
9

Reviewer Can See the Proof

Instant trigger

In Zapier“Triggers when a reviewer can see the proof”

Triggers when a proof becomes visible to a given reviewer. It marks the point where that person can actually open the file and give feedback.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
letting a client know in their preferred tool that a new version is waiting for them, the moment it is theirs to review.
Watch out
it follows each reviewer, not the proof, so a large review panel starts the Zap many times.
When it breaks

When it breaks

Zapier attaches no help article to PageProof, so the known traps are the ones every Zap shares. On a review workflow, they show up in specific ways.

Read these before you publish. If a Zap is already misbehaving, the Zapier troubleshooting guide walks through the usual causes.

  • Past approvals are never picked up

    A Zap only reacts to what happens after you switch it on. Proofs approved or sent back earlier stay out of it, and filling that history in is a separate job.

  • A Zap that feeds its own trigger

    A Zap that writes into the very place its own trigger watches sets itself off again and again. PageProof offers no action today, but keep it in mind across tools.

  • A burst of events can be held back

    When a trigger sends a huge batch at once, for instance after a bulk import or a migration, Zapier's flood protection can hold the runs back.

  • Per-reviewer triggers multiply tasks

    Reviewer Decision Made, Reviewer Nudged and Reviewer Can See the Proof run once per reviewer. On a large panel, each action behind them is billed every time.
Need help

Need help automating PageProof with Zapier?

A person reads every message.

FAQ

PageProof Zapier integration: questions

01Is the PageProof Zapier integration free?
Yes, on the Zapier side it works on the free plan, because PageProof is not a premium app. The free plan gives 100 tasks a month. Its real limit is shape: a free Zap has one trigger and one action, nothing more. Since PageProof only offers triggers, that one action sits in another app. Add a second app, or a filter to keep only some proofs, and you need a paid Zapier plan.
02How many tasks does a PageProof Zap use?
None for the PageProof part. The trigger never costs a task, so an approval or a decision arriving in Zapier is free. What counts is each action that succeeds after it, one task each, in your other apps. A failed action is not counted. A Zap that logs every approval in a sheet and posts a message uses two tasks per approval. Watch the per-reviewer triggers: on a proof with many reviewers, they run once for each person.
03Is PageProof on Zapier real time?
Yes. All nine PageProof triggers are instant: PageProof tells Zapier the moment the event happens, and the Zap starts right away. The interval grid that applies to polling triggers, 15 minutes on the free plan, does not apply here, on any plan. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is a quick way to check. The type is set by PageProof itself and cannot be changed from the editor, so there is nothing to tune on your side.
04What does it take to connect PageProof to Zapier?
A PageProof account and a Zapier account. From the Apps page in Zapier, click + Add connection, search for PageProof, click Add connection, then sign in to PageProof and grant access. The connection is saved once and every Zap reuses it. If the Zap should follow proofs you do not own yourself, make sure the account you connect has access to them. Once connected, the nine triggers appear in the event list when you pick PageProof in a new Zap.
05Why does a PageProof Zap run several times for one proof?
Because some triggers follow people, not proofs. Reviewer Decision Made, Reviewer Nudged and Reviewer Can See the Proof each run once per reviewer, so a proof with several reviewers starts the Zap several times. That is expected, and each run bills the actions behind it. If you want one alert per proof, build on New Proof Approved or New To-Dos Requested instead, which follow the proof as a whole. Either way, the trigger itself never costs a task.
06What if the PageProof operation you need is not in Zapier?
Then it has to happen in PageProof itself. On Zapier, the app offers 9 triggers and nothing else: no action to create a proof or add a reviewer, and no search. A Zap can react to what happens in PageProof and push it into your other tools, but it cannot change anything in PageProof. If the gap is a blocker, list the exact step you are missing before looking at another tool.
07Zapier, Make or n8n for PageProof?
Decide on criteria rather than on a ranking. First, direction: on Zapier, PageProof only sends events out, so check whether you also need to act inside PageProof. Second, speed: all nine triggers are instant here, so timing is not the issue. Third, volume and shape: every successful action is a task, per-reviewer triggers multiply runs, and anything beyond one trigger and one action needs a paid plan. Put the same three questions to each tool.
Same platform

Other docs you might need on this stack.

Browse all integrations