Resources · Make integration

PeerBoard Make integrationAutomate PeerBoard with Make.

Your PeerBoard community can handle its routine chores on its own. The PeerBoard Make integration gives you 24 modules: 1 scheduled trigger, 19 actions and 4 searches. This guide shows community managers how to connect an account, build a first scenario and pick the right module.

Try the PeerBoard integration on MakeSee the 24 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PeerBoard Make integration do for your community?

The PeerBoard Make integration links your PeerBoard community to Make, a no-code tool where you build scenarios: automations made of modules that pass data from one app to the next. With 24 modules, it watches for new posts, writes posts and comments, and manages spaces, members and groups without a single line of code.

Nobody posts into silence. Watch New Post spots a fresh introduction and Create a Comment replies under it, even when your moderators are offline.

New customers find the right doors open. After a purchase, Create a Member or Invite a Member brings the person in, then Add Members to a Space and Add Members to a Group give access to what they paid for.

Access ends as cleanly as it started. A cancelled subscription can lead to Remove Members from a Group or Delete a Member, and a finished project to Delete a Space.

Know the limits before you start. There is only one trigger, and it is scheduled: Make checks for new posts at intervals instead of reacting the second a post is written. A new member or a new comment has no trigger of its own. For what the listed modules skip, Make an API Call reaches the PeerBoard API directly.

Weighing tools? Read n8n vs Make, check the plans in Make pricing, and if you would rather learn step by step, Make training covers the editor from scratch.

Connect

How do you connect PeerBoard to Make?

  1. 01

    Copy your API Auth Token

    Log in to PeerBoard and copy the API Auth token shown under Dashboard > Hosting. Cannot reach that screen? Email support@peerboard.com and ask for it. Either way, you need a PeerBoard account.

  2. 02

    Add a connection in Make

    Insert any PeerBoard module in a scenario and click Add next to the Connection field. A connection is your PeerBoard account linked to Make once, then reused by every PeerBoard module.

  3. 03

    Paste the token and save

    Name the connection in Connection name if you like, paste the token into API Auth Token and click Save. If PeerBoard asks you to confirm access, accept it and you are ready.

First scenario

Your first scenario: greet every new introduction

GoalWhen a new post appears in your introductions space in PeerBoard, Make adds a welcome comment under it.

  1. 01

    Create the scenario

    Open the Scenarios page in Make and create a new scenario, the automation you are about to build. Click the large + in the middle of the editor to add the first module.

  2. 02

    Add Watch New Post

    Search for PeerBoard, pick Watch New Post and link your account with Create a connection or Add. Then choose the space where newcomers introduce themselves.

  3. 03

    Add Create a Comment

    Click the + on the right of the trigger and pick Create a Comment. Map the post coming from the first module so the reply lands in the right thread, then type your welcome text.

  4. 04

    Test with Run once

    Publish a test post in that space and click Run once. Each module shows the bundles it received, one bundle being one item such as a post, so you can check the comment really went out.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, and switch the scenario on. From then on, each new introduction gets its reply without anyone watching.

Triggers

What starts a PeerBoard scenario

1 module starts a scenario when something happens in PeerBoard. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by PeerBoard as soon as it happens.

PeerBoard1Watch New Post

Watch New Post

Scheduled trigger

In Make“Checks whether a new post for a given member or space was created.”

Every fresh post written by a member you pick, or published in a space you pick, reaches your scenario, so a new discussion never sits unnoticed for long.

How it fires
scheduled. Make checks PeerBoard on the scenario's schedule, every 15 minutes by default, and passes on the new posts it finds.
When to use it
new posts in an introductions or support space should reach your moderators, a spreadsheet or an automatic welcome reply.
Watch out
this is not real time. On the Free plan the shortest gap between two checks is 15 minutes, so a post can wait that long before Make sees it.
Modules

Every PeerBoard module, and when to pick it

PeerBoard gives you 23 modules in 5 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Content

4 modules
PeerBoard1

Create a Post

Action

In Make“Creates a new post.”

Announcements land where members already read, because this module publishes a new post in your community straight from a scenario.

When to use it
a blog article goes live, a webinar recording is ready, or a form answer deserves its own public thread.
Watch out
never post into the space that Watch New Post is watching in the same scenario, or each new post will start another run.
PeerBoard2

Create a Comment

Action

In Make“Creates a new comment.”

Threads stay alive while your team is busy: a reply appears under an existing post without anyone opening PeerBoard.

When to use it
thanking the author of a fresh introduction, or adding a follow-up once the support request behind a post has been handled.
Watch out
the comment has to know which post it belongs to, so an earlier module must hand that post over.
PeerBoard3

Search Posts/Comments

Search

In Make“Searches for posts and comments.”

You get back the posts and comments that match your search, each one as its own bundle, ready for the next module.

When to use it
spotting discussions that mention a product before a release, or gathering feedback threads into a spreadsheet for your product team.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per result.
PeerBoard4

List Posts

Search

In Make“Returns a list of posts.”

Instead of matching keywords, this module hands over posts as a plain list, which suits scenarios that need the feed itself.

When to use it
copying posts to an archive, or reviewing which topics came up after an event or a launch.
Watch out
when you know the words you are after, Search Posts/Comments is the better pick, since a full list multiplies bundles and operations.

Spaces

6 modules
PeerBoard5

Create a Space

Action

In Make“Creates a new space.”

Each project, cohort or client gets its own corner of the community without manual setup, because a scenario opens the space for you.

When to use it
a deal is marked as won in your CRM and the customer deserves a private discussion area.
Watch out
a new space starts empty, so follow this module with Add Members to a Space in the same scenario.
PeerBoard6

Update a Space

Action

In Make“Updates an existing space.”

Space details stay in line with the rest of your tools, since this module edits a space that already exists rather than creating another.

When to use it
a project is renamed in your project tool and the matching PeerBoard space should follow the change.
Watch out
Make needs to know which space to edit, so place List Spaces or Get a Space before it when the scenario does not already have it.
PeerBoard7

Add Members to a Space

Action

In Make“Adds new members to a space.”

People appear in the right space automatically, which spares an admin from adding them one by one after every sale or sign-up.

When to use it
someone buys a course and should see the course space, or a client contact joins that client's area.
Watch out
the name sits very close to Add Members to a Group in the module list, so check which one you picked before testing.
PeerBoard8

Get a Space

Action

In Make“Returns an existing space.”

When a scenario only holds a reference to a space, this module fetches the space itself so the following modules can use its details.

When to use it
a message to your team about a new discussion area should show the real space, not just a reference.
Watch out
it reads one space you already identified; to browse all of them, List Spaces is the module to add.
PeerBoard9

List Spaces

Search

In Make“Returns a list of spaces.”

All your spaces arrive as separate bundles, one per space, which lets a scenario act on each of them in turn.

When to use it
auditing every space of the community, or posting the same notice in several spaces with Create a Post right after.
Watch out
every module placed after it runs once per space, so the operation count grows with the size of your community.
PeerBoard10

Delete a Space

Action

In Make“Deletes an existing space.”

Navigation stays clean once a project or a cohort is over, because this module removes the space from your community.

When to use it
a project is closed in your project tool and its discussion area should disappear with it.
Watch out
treat the deletion as final: nothing in the module list brings a space back, so try it with Run once on a spare space first.

Members

6 modules
PeerBoard11

Create a Member

Action

In Make“Creates a new member.”

New people get a PeerBoard profile without anyone typing their details, which fits communities that grow from sign-ups in other tools.

When to use it
a customer completes a purchase or a form and should have community access right away.
Watch out
if the person should get an email and choose to join, Invite a Member is the module built for that.
PeerBoard12

Update a Member

Action

In Make“Updates an existing member.”

Profiles stay accurate when this module rewrites an existing member with data coming from the tool where it changed first.

When to use it
a contact's details change in your CRM and the community profile should say the same thing.
Watch out
the update needs a target, so find the right person first with Search Community Members or Get a Member.
PeerBoard13

Invite a Member

Action

In Make“Sends an invitation to a new member by email.”

An invitation email goes out from PeerBoard and the person decides when to join, which keeps the choice on the member's side.

When to use it
new hires joining an internal community, or event attendees you want to welcome once the event is over.
Watch out
this sends a real email to a real inbox, so run your first test with your own address.
PeerBoard14

Get a Member

Action

In Make“Returns an existing member.”

One member's profile comes back in full, so later modules can greet, route or tag that person with the right information.

When to use it
another module handed over a member reference and the scenario needs the rest of the profile before acting.
Watch out
it reads a member you can already identify; with only a name or an email in hand, start with Search Community Members.
PeerBoard15

Search Community Members

Search

In Make“Searches for community members.”

Finding people from what you already know about them is the job here, and each match arrives as its own bundle.

When to use it
checking whether a buyer already has a profile before creating one, so the community avoids duplicates.
Watch out
no match means no bundle, and the modules after it simply do not run; test that case with Run once too.
PeerBoard16

Delete a Member

Action

In Make“Deletes an existing member.”

Access ends at the same time as a contract or a subscription, since this module takes the person out of the community.

When to use it
a subscription is cancelled in your billing tool and the member should no longer see the community.
Watch out
no module brings a deleted member back, so confirm you target the right person with Search Community Members first.

Groups

6 modules
PeerBoard17

Create a Group

Action

In Make“Creates a new group.”

Members get sorted into sets you can reuse, and this module creates such a group on demand from any event in your other apps.

When to use it
a new customer tier, region or class opens and needs its own group from day one.
Watch out
each run creates another group, so place it only where a new group is really expected, not on every incoming bundle.
PeerBoard18

Update a Group

Action

In Make“Updates an existing group.”

A group keeps matching reality when this module edits it, so you never have to delete it and rebuild it from scratch.

When to use it
a team is renamed or a program changes scope, and the group in PeerBoard should reflect it.
Watch out
the module needs the group from an earlier step, typically Create a Group or Get a Group.
PeerBoard19

Add Members to a Group

Action

In Make“Adds new members to a group.”

Segmentation runs by itself: people join a group as soon as something happens in another tool.

When to use it
a customer upgrades to a higher plan in your billing tool and should join the matching group in PeerBoard.
Watch out
if the person is not in the community yet, run Create a Member or Invite a Member earlier in the same scenario.
PeerBoard20

Remove Members from a Group

Action

In Make“Removes members from a group.”

Group membership shrinks automatically when a status ends, so nobody keeps a place they no longer have a reason to hold.

When to use it
a trial ends, a mentoring program closes, or someone leaves a team in your HR tool.
Watch out
taking someone out of a group leaves the member in the community; Delete a Member is a separate module.
PeerBoard21

Get a Group

Action

In Make“Returns an existing group.”

This returns one group with its details, which helps a scenario fill a message or decide which branch to follow next.

When to use it
before notifying your team about a change, so the message names the group correctly.
Watch out
it reads one group you already identified, and the app offers no module that lists every group.
PeerBoard22

Delete a Group

Action

In Make“Deletes an existing group.”

A group you no longer need disappears without a trip to the admin panel, which keeps member settings easy to read.

When to use it
a cohort finished its program and its group has no purpose anymore.
Watch out
no module brings a deleted group back, so test on a spare one and read the Run once results before activating.

Other

1 module
PeerBoard23

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Anything the ready-made modules leave out stays within reach: this one sends a request of your choice to the PeerBoard API, using the connection you already set up.

When to use it
PeerBoard's API offers an action that has no dedicated module in Make.
Watch out
it is the most technical module of the list, and you need PeerBoard's API documentation to know which endpoint to call.
Need help

Need help automating PeerBoard with Make?

A person reads every message.

FAQ

PeerBoard and Make: common questions

01Is the PeerBoard Make integration free?
Yes. PeerBoard is a standard app in Make, so it works on the Free plan. That plan allows 2 active scenarios, a minimum interval of 15 minutes between 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) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Each module run counts as one operation on your monthly credits. You still need your own PeerBoard account.
02What do you need to connect PeerBoard to Make?
A PeerBoard account and its API Auth Token. The token sits in PeerBoard under Dashboard > Hosting, and you can also request it from support@peerboard.com. In Make, open any PeerBoard module, click Add next to the Connection field, paste the token into API Auth Token and click Save. If PeerBoard asks you to confirm access, accept it. The connection is created once and every PeerBoard module in your scenarios reuses it, so the token never has to be pasted twice.
03Does the PeerBoard trigger in Make work in real time?
No. Watch New Post is a scheduled trigger: Make asks PeerBoard for new posts on the scenario's schedule, every 15 minutes by default. Paid plans can shorten the interval to 1 minute, while the Free plan keeps a minimum of 15 minutes. PeerBoard has no instant trigger in Make, which means no webhook-based module that fires the moment a post appears. For a welcome comment or a moderation alert, that gap rarely matters; for anything that must happen on the spot, plan the scenario around it.
04What if a PeerBoard module is missing in Make?
Use Make an API Call. This module sends any request to the PeerBoard API with the connection you already created, so an endpoint without a ready-made module is still within reach. You need to know which endpoint to call, which means opening PeerBoard's API documentation. The PeerBoard documentation in Make gives no numeric limit for the app, so none can be promised here. If a call fails, read what the module returned after Run once before changing anything else in the scenario.
05Should you pick Make or n8n for PeerBoard?
It depends on your criteria. In Make, PeerBoard comes with 24 ready modules for posts, comments, spaces, members and groups, plus Make an API Call, inside a visual editor where each step can be tested with Run once. On the n8n side, check whether a PeerBoard node exists and what it covers before comparing. Then list the events you need to catch and the actions you need to run, and see which tool handles them the way your team likes to build. Start from one concrete scenario and try it.
Same platform

Other docs you might need on this stack.

Browse all integrations