Resources · Make integration

Ryver Make integrationAutomate Ryver with Make.

What if your team chat in Ryver could post updates and manage teams on its own? The Ryver Make integration gives you 9 modules: 6 actions and 3 searches. This page is for ops leads who run Ryver daily, and it walks you from the first connection to a working scenario.

Try the Ryver integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Ryver Make integration do for you?

The Ryver Make integration links your Ryver account to Make so that other tools can write in Ryver for you. You build a scenario, the automation made of modules (one brick each: an action or a search), and it posts messages, opens topics or changes who belongs to which team without anyone typing.

Announcements that write themselves. When a deal closes in your CRM, Create a Post opens a topic in the sales team with the client name and amount, so the thread for questions starts in the right place.

Onboarding that follows the HR file. A new hire added to a spreadsheet can trigger Add a User to a Team, and the same person is taken out with Remove a User from a Team when they change department. For a new project, Create a Team sets up the space before the kickoff.

A quick alert in the right chat. Create a Chat Message drops a short line in a conversation when a form comes in or an order fails, which suits alerts better than a full post.

Ryver has no trigger module in Make: the app does not start a scenario by itself. The scenario starts from another app or from Make's schedule, and anything the listed modules skip goes through Make an API Call. Before you choose a plan, read the Make review and Make pricing. If you also weigh n8n, the n8n vs Make comparison lays out the criteria.

Connect

How do you connect Ryver to Make?

  1. 01

    Add a Ryver module

    In your scenario, click the +, search for Ryver and pick any of its modules, for example Create a Post. Then click Create a connection: a connection is your Ryver account linked to Make once, then reused by every Ryver module.

  2. 02

    Name and authorize

    Give the connection a name if you like, such as the workspace it points to. Then authorize Make on the Ryver page that opens, or paste the key Ryver gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. Back in the module, Make can now read your account and list the teams it finds, which is the simplest sign that the connection works before you fill anything else.

First scenario

Your first scenario with Ryver

GoalWhen a new deal is recorded in another app, Make opens a post in the right Ryver team.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the module of the app where the event happens, your CRM or your form tool, since Ryver has no trigger.

  2. 02

    Add Create a Post

    Click the + on the right of that first module, search for Ryver and choose Create a Post. Select your connection, or click Create a connection if this is your first Ryver module.

  3. 03

    Map the content

    Choose the team from the list Make shows, then map the deal name and amount from the first module into the post. Each bundle, one deal here, becomes one post.

  4. 04

    Test with Run once

    Click Run once and create a test deal. Open the bubble on each module to read the bundles it received, then check that the post appears in Ryver.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, and switch the scenario on. Each run uses operations, one per module per bundle, which is what Make counts on your plan.

Modules

What each Ryver module does

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

Ryver1

Add a User to a Team

Action

In Make“Adds an existing user to a team or several teams.”

Gives an existing Ryver user access to one team, or to several teams in one step, so a newcomer lands in the right spaces without an admin clicking through each one.

When to use it
right after a hire is confirmed in your HR tool or a contractor signs, to open the project and department teams together.
Watch out
the person must already have a Ryver account; this module adds a member, it does not invite someone new.
Ryver2

Create a Chat Message

Action

In Make“Creates a chat message.”

Sends a short message into a Ryver chat, the quick way to alert people without opening a whole discussion thread.

When to use it
a payment fails, a support ticket is escalated or a form is submitted, and someone needs to see it now in the conversation they already watch.
Watch out
for news that deserves replies and a lasting thread, pick Create a Post instead, since a chat line scrolls away fast.
Ryver3

Create a Post

Action

In Make“Creates a post.”

Publishes a post, the topic-style entry Ryver keeps in a team, so an update gets its own place where people can comment and find it later.

When to use it
a contract is signed, a release ships or a project report is ready in another tool, and the team should discuss it in one thread.
Watch out
map a clear title from the previous module; a vague one makes the topics list hard to scan.
Ryver4

Create a Team

Action

In Make“Creates a team.”

Sets up a new team in Ryver from your scenario, which saves you from building the same workspace by hand for every new client or project.

When to use it
a project is created in your project tool or a client moves to won in the CRM, and the delivery crew needs a space.
Watch out
add a search with List Teams before it if the same event can arrive twice, or you may end up with duplicate teams.
Ryver5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Lets you call any endpoint of the Ryver API with the connection you already set up, so you are not stuck when the listed modules skip what you need.

When to use it
you want to update or delete something in Ryver, and none of the eight other modules does that job.
Watch out
you write the request yourself here, so keep the Ryver API documentation open and test with Run once before switching on.
Ryver6

Remove a User from a Team

Action

In Make“Removes a user from a team.”

Takes a person out of a Ryver team, keeping access in line with who actually works on what without waiting for an admin to notice.

When to use it
someone changes department, a contractor's mission ends or a client project closes in your records.
Watch out
run a test on a spare account first, because a wrong mapping removes the wrong colleague, and putting them back takes a separate Add a User to a Team run.
Ryver7

List Team Members

Search

In Make“Lists team members.”

Returns the members of a team as separate bundles, which gives your scenario the list of people to act on or to copy elsewhere.

When to use it
you audit who sits in a client team, or you want to send each member into a spreadsheet or another tool.
Watch out
a search returns zero, one or several bundles, so every module after it runs once per member and uses operations accordingly.
Ryver8

List Teams

Search

In Make“Lists all teams.”

Brings back all the teams of your Ryver account, one bundle per team, so a scenario can pick the right one or check that it exists.

When to use it
before Create a Team to avoid a duplicate, or to find the team that matches a client name coming from your CRM.
Watch out
if nothing matches, the search gives zero bundles and the modules after it simply do not run.
Ryver9

List Team Topics

Search

In Make“Lists a team's topics (posts).”

Reads the topics, meaning the posts, of one team so you can reuse what was already published instead of posting it again.

When to use it
you want to archive a team's announcements in a document, or check whether a topic about a deal already exists before creating one.
Watch out
each topic comes out as its own bundle; add a filter after it when only some of them matter.
Need help

Need help automating Ryver with Make?

A person reads every message.

FAQ

Ryver Make integration: frequently asked questions

01Is the Ryver Make integration free?
Yes, Ryver is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 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, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits, meaning operations, each month. The price of Ryver itself is a separate matter between you and Ryver.
02What do you need to connect Ryver to Make?
A Ryver account and a Make account are enough to start; the Ryver documentation in Make lists no extra prerequisite. You add any Ryver module, click Create a connection, optionally give it a name, then authorize Make on the Ryver page or paste the key Ryver provides, and click Save. The connection is then shared by all nine Ryver modules, so you do this once. Naming it after the workspace helps when you pick it again in the next Ryver module you add.
03Can a Ryver scenario in Make start on its own?
Not from Ryver: the app has no trigger module in Make, neither scheduled nor instant, so Ryver cannot tell Make that something happened. You start the scenario in one of two ways. Either another app triggers it, such as a new row, a form entry or a deal in your CRM, and the Ryver modules act afterward. Or you put a Ryver search such as List Teams first and let Make's schedule run it, every 15 minutes by default, down to 1 minute on paid plans.
04What if a Ryver module you need is missing in Make?
Use Make an API Call. It sends any request to the Ryver API with the connection you already have, which covers what the nine listed modules leave out, for example editing or deleting an item. You write the request yourself, so check the Ryver API documentation and test with Run once first. The Ryver documentation in Make gives no numeric limit, so there is no quota to plan around beyond the limits of your Make plan.
05Should you use Make or n8n for Ryver?
It depends on what you already run. In Make, Ryver comes with nine modules, six actions and three searches, plus Make an API Call for the rest, and the whole flow is built visually in the scenario editor. Many apps also have an n8n node, so check whether one exists for Ryver and which operations it covers before deciding. Compare both on the modules your scenario actually needs and on the tool your team already uses, rather than on the app alone.
Same platform

Other docs you might need on this stack.

Browse all integrations