Resources · Make integration

Papyrs Make integrationAutomate Papyrs with Make.

What if your intranet kept itself up to date? The Papyrs Make integration gives you 17 modules: 2 triggers, 13 actions and 2 searches. This guide is for Papyrs admins who want pages, text and people to move on their own, and it walks you from connection to a live scenario.

Try the Papyrs integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Papyrs Make integration do for you?

The Papyrs Make integration links your Papyrs site to the other tools you use, without writing code. In Make you build a scenario, the automation itself, from modules: each module is one brick, like a trigger that spots a new page or an action that edits a text box. Papyrs becomes a place your other apps can read from and write to.

Greet every newcomer in public. Watch People notices when someone joins your Papyrs site, and Post to a Discussion Stream on a Page drops a welcome message on the team page. Nobody has to remember to say hello.

Keep a status page honest. Update a Text Box and Update a Heading Widget rewrite the content of an existing page with data coming from another app, so a project page shows the latest figures instead of an outdated copy.

Announce new pages elsewhere. Watch Pages picks up each page created on the site; you can then send its title to a chat tool or a spreadsheet through that app's own module.

Know the edges before you start. Both Papyrs triggers are scheduled: Make checks the site on the scenario's schedule, it is never told instantly. The listed modules cover pages, text boxes, headings, discussions and people; for anything else in the Papyrs API, the Make an API Call module reuses the same connection. The same app often has an n8n node too, and our n8n vs Make comparison helps you pick the editor. New to the tool? Start with the Make training, or check Make pricing before you switch scenarios on.

Connect

How do you connect Papyrs to Make?

  1. 01

    Generate your API token in Papyrs

    Sign in to Papyrs as an administrator, open Site Settings, then Integrations and SSO and API. Click Generate Token and copy the token shown on screen. Keep it handy for the next step.

  2. 02

    Add a Papyrs module in Make

    In your scenario, add any Papyrs module and click Create a connection. A connection is your Papyrs account linked to Make once, then reused by every Papyrs module you add later.

  3. 03

    Name it and paste the token

    The Connection name field is optional, but a clear name helps when you run several sites. Paste the API token you copied, follow the on-screen instructions and save. Make can now read your pages and people.

First scenario

Your first scenario: welcome new people on a Papyrs page

GoalWhen someone new joins your Papyrs site, Make posts a welcome message to the discussion on your team page.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module. This first module decides when everything starts.

  2. 02

    Pick Watch People

    Search for Papyrs, choose Watch People and select your connection, or click Create a connection if this is your first Papyrs module. It will hand over one bundle per new person, a bundle being one item passed along the scenario.

  3. 03

    Add the welcome post

    Click the + on the right of the trigger, pick Post to a Discussion Stream on a Page and choose the team page. Write the message and map the person's name from the previous module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can read the posted comment before anyone else does.

  5. 05

    Schedule and switch on

    Open the clock on Watch People: a new scenario checks every 15 minutes by default. Keep that or change it within your plan, then switch the scenario on.

Triggers

What can start a Papyrs scenario?

2 modules start a scenario when something happens in Papyrs. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Papyrs as soon as it happens.

Papyrs1Watch Pages

Watch Pages

Scheduled trigger

In Make“Triggers when new pages are created.”

Watch Pages hands your scenario every page freshly created on your Papyrs site, one bundle per page, so the rest of the flow can react to new content without anyone copying links around.

How it fires
scheduled. Make checks the app on the scenario's schedule, which is every 15 minutes by default, and collects the pages created since the last check.
When to use it
a new policy or project page should be announced in your chat tool or logged in a spreadsheet the moment the run finds it.
Watch out
it reacts to creation only, so a page that someone edits later will not start the scenario again.
Papyrs2Watch People

Watch People

Scheduled trigger

In Make“Triggers when new people are joined.”

At each check, Watch People picks up the people who joined your Papyrs site, and passes each one along as a bundle you can map into the next modules.

How it fires
scheduled. Make checks the app on the scenario's schedule and picks up everyone who joined since the previous run; nothing reaches Make instantly.
When to use it
onboarding, when each newcomer should get a welcome post, a row in your HR tracker or a task for their manager.
Watch out
pair it with List People rather than with this trigger when you need the whole directory, since Watch People only reports people who arrive after the scenario is on.
Modules

What can Make do in Papyrs?

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

Papyrs1

Create a Heading Widget

Action

In Make“Creates a heading widget on a page.”

Adds a new heading to a Papyrs page, which gives structure to content your scenario is about to write, such as a dated section title above a fresh text box.

When to use it
a report page where each new entry should open with its own clear heading.
Watch out
place it before Create a Text Box in the flow so the heading sits above the text it introduces.
Papyrs2

Create a Text Box

Action

In Make“Creates a new text box on a page.”

Writes a brand new text box onto a page, turning data from another app, like a form answer or a meeting summary, into readable content on your intranet.

When to use it
each new entry deserves its own block, rather than replacing what the page already says.
Watch out
every run adds one more box; if the page should show only the latest version, use Update a Text Box instead.
Papyrs3

Delete a Heading Widget

Action

In Make“Deletes an existing heading widget on a page.”

Removes an existing heading from a page, which keeps automated pages tidy once a section no longer applies.

When to use it
a project closes and its section title should disappear from the shared dashboard page.
Watch out
you need the exact heading widget to target, so fetch or map it from an earlier module first, and remember the deletion is not undone by Make.
Papyrs4

Delete a Page

Action

In Make“Deletes a page by its ID.”

Deletes a whole Papyrs page by its ID, useful when pages are created automatically and need to be cleared at the end of their life.

When to use it
an event or temporary project page that another app marks as finished.
Watch out
the page goes with all its content. Test on a throwaway page with Run once, and add a filter before this module so only the right ID ever reaches it.
Papyrs5

Delete a Text Box

Action

In Make“Deletes an existing text box on a page.”

Takes one text box off a page while leaving the rest of the page untouched, so a scenario can retract content it posted earlier.

When to use it
an announcement text box should vanish once the matching record is closed in your other tool.
Watch out
store the text box reference when you create it; without it, the scenario cannot tell which box to remove.
Papyrs6

Delete a User

Action

In Make“Permanently deletes a user from your account.”

Permanently removes a person from your Papyrs account, which lets offboarding in your HR or identity tool close intranet access as well.

When to use it
a departure is confirmed in another system and access must follow without a manual ticket.
Watch out
the deletion is permanent. Run once with a test user first, and never feed it straight from a search that can return several people.
Papyrs7

Get a Heading Widget

Action

In Make“Retrieves information about selected heading widget.”

Reads the details of one heading widget, so the scenario can check what a section is called before deciding to change or remove it.

When to use it
a flow that should update a heading only if its current wording differs from the new value.
Watch out
it returns a single widget; it does not scan a page for every heading it contains.
Papyrs8

Get a Page

Action

In Make“Retrieves information about selected page.”

Fetches the information of one selected page, giving later modules what they need to link to it, copy its title or act on it.

When to use it
right after Watch Pages, when the trigger bundle alone lacks a detail you want to pass along.
Watch out
it works on one page you already know; to browse all pages, List Pages is the right choice.
Papyrs9

Get a Text Box

Action

In Make“Retrieves information about selected text box.”

Retrieves the content of one text box, handy when a scenario must copy a block of intranet text into an email, a document or another app.

When to use it
a policy paragraph kept on Papyrs should feed an outgoing message so both always match.
Watch out
map the text box from a previous module; typing an identifier by hand breaks as soon as the page is rebuilt.
Papyrs10

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the Papyrs API with the connection you already set up, which covers what the listed modules do not.

When to use it
you need a Papyrs feature that has no ready-made module, and you have read the Papyrs API reference for the request to send.
Watch out
it gives you raw access, so check the response in Run once before mapping its data further down the scenario.
Papyrs11

Post to a Discussion Stream on a Page

Action

In Make“Posts a comment to any page with a discussion widget.”

Adds a comment to the discussion of a page, so updates from other tools show up where your team already talks.

When to use it
welcoming a newcomer, flagging a closed deal or relaying a support alert on the relevant team page.
Watch out
the target page needs a discussion widget; on a page without one, there is nowhere for the comment to land.
Papyrs12

Update a Heading Widget

Action

In Make“Updates an existing heading widget.”

Changes the wording of an existing heading, so a page can reflect a new status without being rebuilt.

When to use it
a heading such as a project phase or a current owner should follow the value stored in your project tool.
Watch out
it edits a heading that already exists; if the page has none yet, start with Create a Heading Widget.
Papyrs13

Update a Text Box

Action

In Make“Updates an existing text box.”

Rewrites the content of a text box already on a page, which keeps one living block current instead of piling up new ones.

When to use it
a status page, a contact list or a key-figures box that should always show the latest data from another app.
Watch out
the new content replaces the old. Need to keep part of it? Read it first with Get a Text Box.
Papyrs14

List Pages

Search

In Make“Lists all existing pages. Ordered by creation date (newest page first).”

Returns every existing page of your site, newest first, one bundle per page, which gives you an inventory to export or check.

When to use it
building a site map in a spreadsheet, or finding the page to act on when you only know its title.
Watch out
a search can return zero, one or many bundles; add a filter so later modules run only on the pages you mean.
Papyrs15

List People

Search

In Make“Lists all people. Ordered by join date (newest user first).”

Lists everyone on your Papyrs site, sorted by join date with the most recent arrival first, for syncing or auditing your directory.

When to use it
comparing Papyrs members with your HR tool to spot accounts that should no longer be there.
Watch out
each person is a separate bundle and every module after it runs once per person, which counts as operations on your plan.
Need help

Need help automating Papyrs with Make?

A person reads every message.

FAQ

Papyrs and Make: common questions

01Is the Papyrs Make integration free?
Yes, on the Make side. Papyrs is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and count usage in credits, one operation per module run. You still need your own Papyrs subscription.
02What do you need to connect Papyrs to Make?
An active Papyrs account with administrator access. The connection relies on an API token that only an admin can generate: open Site Settings, then Integrations and SSO, then API, click Generate Token and copy it. In Make, add a Papyrs module, click Create a connection, optionally give it a name, and paste the token. Every Papyrs module in your scenarios then reuses that same connection, so you only set it up once per Papyrs site.
03Do the Papyrs triggers in Make fire in real time?
No. Watch Pages and Watch People are both scheduled triggers, shown with the clock badge in the editor. Make asks Papyrs for new pages or new people on the scenario's schedule, every 15 minutes by default. On the Free plan, 15 minutes is also the shortest interval; paid plans can go down to 1 minute. Papyrs has no instant trigger in Make, so nothing is pushed to Make by webhook.
04What if a Papyrs module is missing in Make?
Use Make an API Call. It sends any request the Papyrs API accepts, with the connection you already created, so you are not limited to the 13 actions and 2 searches listed. Check the Papyrs API documentation for the request to send, test it with Run once and read the returned bundle before mapping it. The Make documentation for this app gives no specific limits, so verify important details directly with Papyrs.
05Should you use Make or n8n for Papyrs?
It depends on the editor you already work in. Make offers Papyrs as a ready app with 17 modules, including 2 scheduled triggers and Make an API Call for anything else, available from the Free plan. The same app often has an n8n node as well, so check whether it covers the pages, text boxes and people you plan to automate. If your team already runs scenarios in Make, staying there keeps every connection in one place.
Same platform

Other docs you might need on this stack.

Browse all integrations