Resources · Zapier integration

Papyrs Zapier integrationAutomate Papyrs with Zapier.

Papyrs Zapier integration: 3 triggers, 7 actions, no search step. Zapier watches your Papyrs intranet for new pages and newly invited people, then posts comments, adds headings and writes or rewrites textboxes on pages that already exist. It runs on the free plan.

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Papyrs Zapier integration actually does

The Papyrs Zapier integration hooks your Papyrs intranet up to Zapier, a service that runs small automations between apps for you. Papyrs can start the automation when a page appears or someone is invited, and it can receive the result: a comment, a heading, a block of text on a page you already built.

Three things people get out of it. First, a Feed that announces itself: New Page picks up a fresh page and Post Comment on Feed (Activity Stream) tells everyone it exists, without anyone writing the note by hand. Second, pages that fill up from outside: an event in another tool (a form answer, a closed deal, a new ticket) becomes a line of text through Create New Textbox (Text) on the page where your team already looks. Third, a status box that stays current: Update TextBox (Text) rewrites the same box on every run, so the page shows the latest state instead of a growing pile.

Now the limits, because they shape what you can build. None of the three triggers is instant: Zapier checks Papyrs on a timer. There is no search step, so a Zap cannot look up an existing page or person on its own. No action creates a page, invites a person, deletes anything or edits a comment once it is posted. And nothing fires on a new comment or an edited page. If your plan relies on any of those, it will not happen through this integration.

The same app is also covered on the other side: Papyrs Make integration.

Vocabulary

Zapier words you will meet on this page

Eight terms, each in one line. Once you have them, the rest of the page reads fast.

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 that starts the Zap, here a new Papyrs page or a new person. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, posts or changes something for you, like a comment on the Feed.
Task
The unit Zapier bills. One action your Zap completes successfully is one task, and your plan counts those.
Polling trigger
A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only what it has not seen.
Instant trigger
A trigger the app reports itself, the moment the event happens. Papyrs has none of these on Zapier today.
Filter
A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it there 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 a Papyrs Zap really costs

Papyrs is not reserved for paid plans on Zapier, so it works from the free plan. The trigger never costs a task, and neither do the checks Zapier runs on Papyrs.

  • Tasks on the free plan100 per month
  • Zaps on the free planUnlimited
  • Steps on the free plan1 trigger + 1 action
  • Cost of a trigger check0 tasks

You pay in tasks. Each action that succeeds counts once, and an action that fails is not counted against the plan. So a Zap with one Feed comment spends one task per new page, and a Zap that posts a comment and then adds a textbox spends two per run. The free plan also stops at two steps: one trigger, one action. Adding a filter to skip some pages, or a second action, turns the Zap into a multi-step Zap and moves you to a paid plan.

Connect

Connect your Papyrs account to Zapier

  1. 01

    Open your connections

    In your Zapier account, go to the Apps page and click + Add connection. A connection is your Papyrs account linked to Zapier once, then reused by every step that touches Papyrs.

  2. 02

    Pick Papyrs

    In the dialog that opens, type Papyrs in the search box, select it in the results, then click Add connection. Zapier then opens a new tab for the Papyrs sign-in.

  3. 03

    Sign in and grant access

    Sign in to Papyrs in that tab and allow Zapier to use the account. You need a Papyrs account, plus read or write rights on any page you do not own and want the Zap to touch.

First Zap

Your first Zap: welcome every new person on Papyrs

GoalEach time someone is invited to your Papyrs account, post a welcome on the Feed and add a line to your team page.

  1. 01

    Set the trigger

    In the Build step, pick Papyrs as the app and New People as the event, then choose the connection you just made. This is the event that starts every run.

  2. 02

    Test it on real data

    Run the trigger test. Zapier brings back the three most recent people invited to the account, and you pick one, so the fields you map next come from a real record.

  3. 03

    Post the welcome

    Add Post Comment on Feed (Activity Stream). In Message, mix fixed words with what the trigger brought back, so each newcomer gets a note built from their own record.

  4. 04

    Add the line on your team page

    Add Create New Textbox (Text). Pick the existing team page in Page, then write the Textbox. This second action makes the Zap multi-step, so it needs a paid plan.

  5. 05

    Test each step, then publish

    Run each action once and check the result in Papyrs. When both look right, click Publish to switch the Zap on, and count two tasks per run from then on. The Zapier training goes further.

Triggers

Papyrs triggers on Zapier

3 events start a Zap when something happens in Papyrs. Zapier checks for them at the interval your plan allows.

1

New Page by This API User

Polling trigger

In Zapier“Triggers when a new page is created by this user (i.e. by the user with this API Auth Token).”

This one only reacts to pages created by the account you connected to Zapier, not by your colleagues. It is the narrow version of New Page, useful when one person or one shared account publishes the pages that matter.

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
you publish team updates or procedures from a dedicated account, and only those pages should be announced elsewhere.
Watch out
connect the account that actually writes the pages. Connect your own by mistake and the Zap stays silent while the real author keeps publishing.
2

New Page

Polling trigger

In Zapier“Triggered when a new page is created.”

Every new page that shows up on your Papyrs site starts the Zap. It is the wide net of the three triggers, and the natural start for anything that should follow the growth of the intranet as a whole.

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
you want each new page announced on the Feed, logged in a spreadsheet, or flagged to whoever keeps the intranet tidy.
Watch out
on the free plan a page can wait up to one interval before Zapier sees it, so do not promise an instant announcement to the people reading the Feed.
3

New People

Polling trigger

In Zapier“Triggers when new people are invited to your Papyrs account in the People Directory.”

When someone is invited to your Papyrs account in the People Directory, Zapier picks it up and starts the Zap with that person. The moment that counts is the invitation, not their first login.

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
onboarding, so the HR or office team hears about a new colleague and a welcome lands on the Feed without anyone remembering to post it.
Watch out
inviting a whole department in one go sends a large batch at once, and Zapier can hold an unusually big batch back as a flood.
Actions

Papyrs actions on Zapier

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

1

Post Comment on Feed (Activity Stream)

Action

In Zapier“Post new Comment to the Feed (Activity Stream)”

Publishes a message on the Feed, the activity stream everyone on your Papyrs site sees. It needs no page, only the message itself.

When to use it
company-wide announcements triggered elsewhere, like a new hire, a shipped release or a page worth reading.
Watch out
the Feed is shared by everyone, so a noisy trigger turns it into spam fast. A filter keeps it calm, on a paid plan.
2

Create New Heading

Action

In Zapier“Add a Heading to an existing Page.”

Drops a heading onto a page you already have, so the page gets a new section title written by the Zap.

When to use it
a log page that opens a new section each time a project starts in another tool.
Watch out
it only adds a title. Pair it with a textbox action if the section needs content underneath.
3

Post Comment on Page

Action

In Zapier“Post a new Comment to a Page.”

Leaves a comment under one specific page rather than on the Feed, so the note stays attached to the document it concerns.

When to use it
flagging on a procedure page that the related tool changed, or noting under a client page that a ticket was opened.
Watch out
once posted, the comment cannot be edited or removed by the Zap, so test the wording first.
4

Create New Textbox (Text)

Action

In Zapier“Add a Textbox to an existing Page.”

Adds a plain text block to an existing page. You choose the page, then write what goes in the box, mixing fixed words with values from earlier steps.

When to use it
appending each signed contract or each form answer to a running page your team reads.
Watch out
every run adds another box, so a busy trigger makes a long page quickly.
5

Create New Textbox (HTML)

Action

In Zapier“Add a Textbox with HTML content to an existing Page.”

Same gesture as the plain text version, but the box takes formatted content: bold words, links, lists. Handy when the text comes from a tool that already produces formatted content.

When to use it
publishing a newsletter extract or a formatted report straight onto an intranet page.
Watch out
if the source sends plain text, use the Text version instead and save yourself the cleanup.
6

Update TextBox (HTML)

Action

In Zapier“Updates an existing Text box on a Papyrs page.”

The formatted version of Update TextBox: it swaps the whole content of an existing box for new formatted content, links and emphasis included.

When to use it
a dashboard block on an intranet page that another tool regenerates as formatted text.
Watch out
the old content is replaced, not merged. Anything typed by hand in that box disappears on the next run.
7

Update TextBox (Text)

Action

In Zapier“Updates an existing Text box on a Papyrs page.”

Rewrites a textbox that already sits on a page, replacing its text with the new version. The page stays the same length however often the Zap runs.

When to use it
a status line like the current on-call person or the latest figure, refreshed by another tool.
Watch out
it asks for the Widget of the box to rewrite, so that box must exist before you build the Zap.
When it breaks

When a Papyrs Zap breaks

Zapier ties no help article to Papyrs, so the traps below are the general ones, read through what this app can and cannot do.

Two things explain a Zap that stays quiet: the timer, and what the Zap was never meant to see. Start here before you dig deeper, then use Zapier troubleshooting if a run still fails.

  • Old pages are never picked up

    A Zap only reacts to what happens after you switch it on. Pages and people that existed before are ignored, and moving that backlog is a separate job.
  • A Zap that feeds itself

    A Zap that writes where its own trigger watches sets itself off again and again. No Papyrs action creates a page or a person, but a second Zap could close that loop.
  • A big import gets held back

    Inviting many people at once, or a migration of pages, sends a huge batch to the trigger. Zapier's flood protection can hold that batch back.
  • The same page twice? No

    Zapier remembers what it has already seen on a polling trigger, so one page or one person never starts the Zap twice, even across many checks.
Need help

Need help automating Papyrs with Zapier?

A person reads every message.

FAQ

Papyrs Zapier integration: frequent questions

01Is the Papyrs Zapier integration free?
Yes, as long as your Zap stays at two steps. Papyrs is not reserved for paid plans on Zapier, so the free plan covers it: 100 tasks a month, as many Zaps as you like, and a check every 15 minutes. The catch is the shape of the Zap. The free plan allows one trigger and one action, nothing more. Add a second action, like a Feed comment plus a textbox, or a filter to skip some pages, and the Zap becomes multi-step, which needs a paid plan.
02How many tasks does a Papyrs Zap use?
One task for each action that succeeds, and nothing else. The trigger is free, and so are the checks Zapier runs on Papyrs, however often they happen. A Zap that posts one comment on the Feed spends one task per new page. A Zap that posts a comment and adds a textbox spends two per run. An action that fails is not counted. On a free plan with 100 tasks a month, a busy New Page trigger is the thing to watch, since every page it catches leads to a billed action.
03Does Papyrs trigger Zaps in real time?
No. All three Papyrs triggers are polling triggers: Zapier asks Papyrs for new items on a timer and keeps what it has not seen yet. How long you wait depends on your plan: 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On a paid plan you can also change that interval and run a check by hand from the editor. That type comes from Papyrs itself and cannot be switched to instant from the Zapier editor.
04What do you need to connect Papyrs to Zapier?
A Papyrs account, and rights on what the Zap will touch. If the Zap writes on a page you do not own, your account needs read or write access to it. The connection itself takes three moves: open the Apps page of your Zapier account and add a connection, pick Papyrs in the dialog, then sign in to Papyrs in the new tab and let Zapier use the account. The connection is then reused by every Papyrs step in every Zap you build.
05Why does Update TextBox ask for a Widget?
Because it rewrites one precise box, and the Widget is how Papyrs tells boxes apart. Both update actions, Text and HTML, require the page and the Widget of the textbox to change, on top of the new content. So the box has to exist before the Zap runs: create it by hand on the page, then the Zap can rewrite it on every run. The update replaces everything inside the box, which also means anything a colleague typed there by hand is gone after the next run.
06What if the Papyrs action you need is not on Zapier?
Then the editor will not offer it, and no setting brings it back. On Zapier, Papyrs has 3 triggers and 7 actions, all listed on this page: comments, headings, and creating or updating textboxes. There is no search step, no action that creates a page or invites a person, and nothing that deletes. If the job needs one of those, a person still does that part in Papyrs, or the whole flow moves to a tool that offers it. Check the app list in the editor before you plan around a missing step.
07Zapier, Make or n8n for Papyrs?
Decide on criteria, not on a ranking. On Zapier, Papyrs works on the free plan, the checks run every 15 minutes there, and a Zap stays free only at one trigger and one action. If your flow fits that shape and the 10 operations above, Zapier covers it with little setup. If you need several actions per run, a filter or a step Zapier does not offer for Papyrs, compare what each tool actually offers for this app and what your volume will cost on each before you commit.