Resources · Make integration

Risk Cloud Make integrationAutomate Risk Cloud with Make.

Can Make read what sits in your Risk Cloud workflows? Yes. The Risk Cloud Make integration gives you 6 modules, 4 searches and 2 actions, to pull applications, steps and records into other tools. This guide connects your account and builds a first scenario with you.

Try the Risk Cloud integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Risk Cloud Make integration do?

The Risk Cloud Make integration links your Risk Cloud account to Make so a scenario, the automation you build in Make, can read your applications, their workflows, the steps inside them and the records waiting in each step. Every brick of that scenario is a module, and you never write code to chain them.

A queue you can see from anywhere. A compliance lead wants to know which records are sitting in a review step. List records in a step returns them as bundles, one bundle per record, so the next module can post them in a chat tool or copy them into a sheet.

A map of your setup. An admin inheriting a Risk Cloud instance chains List applications, List workflows in an application and List steps in a workflow to write the whole structure into a document the team can read.

One record, on demand. When another app hands Make a record ID, Get record fetches that record so its data can travel further in the scenario.

What Make does not do here: Risk Cloud has no trigger in Make, so a scenario starts on Make's schedule or on another app's trigger. There is no module to create or update a record either; Make an API call is the way to reach other parts of the Risk Cloud API. Make's page for this app also warns that it was generated with AI from Risk Cloud's documentation, so check any important detail with Risk Cloud.

If you are weighing the two tools, the n8n vs Make comparison lays out the criteria. To learn the editor properly, Make training starts from zero, and Make troubleshooting helps when a run fails.

Connect

How do you connect Risk Cloud to Make?

  1. 01

    Open the connection window

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

  2. 02

    Name it so you recognize it

    The Connection name field is optional, but a clear name such as the instance or the team helps when you run several Risk Cloud accounts side by side in the same Make organization.

  3. 03

    Paste your credentials

    Enter the credentials you copied from Risk Cloud, or follow the instructions shown on screen. You need an active Risk Cloud account with the right permissions and an API access token before you start.

First scenario

Your first scenario with Risk Cloud

GoalWhen records are waiting in a step of a Risk Cloud workflow, Make lists them on its schedule and fetches each record so the next module can use it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to place the first module. Nothing runs yet, so you can try things freely.

  2. 02

    Add List records in a step

    Search for Risk Cloud, pick List records in a step and link your account with Create a connection. Once connected, Make proposes what it can read, so you choose the step from a list.

  3. 03

    Chain Get record

    Click the + on the right of the first module, add Get record and map the record identifier coming from the previous module. Each bundle, one record here, is handled in turn.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time, then you read the bundles each module received and check that the right records came through.

  5. 05

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default. Adjust it, then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What the Risk Cloud modules do

Risk Cloud gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Risk Cloud1

Get record

ActionIn the docs only

Get record brings back a single Risk Cloud record you point it to, so its data can feed the rest of the scenario, whether that is an email, a sheet row or a ticket.

When to use it
another module or app already gives you the record identifier and you need that exact record.
Watch out
it works on one record per bundle, so place it after a search when you want to process many.
Risk Cloud2

List applications

SearchIn the docs only

Knowing which applications exist in your Risk Cloud instance is the starting point of most setups, and this search returns them, one bundle for each application found.

When to use it
you are building an inventory or you need an application reference before listing its workflows.
Watch out
a search can return zero, one or several bundles, and each following module then runs once per application.
Risk Cloud3

List records in a step

SearchIn the docs only

Here you get the records currently sitting in one step of a workflow, which is the closest thing to a live queue this app offers in Make.

When to use it
a review or approval step fills up and you want the waiting items sent somewhere your team already looks.
Watch out
run on a schedule, it returns what is in the step at that moment, so records already handled may come back if nothing filters them.
Risk Cloud4

List steps in a workflow

SearchIn the docs only

This search gives you the steps that make up a workflow, in bundles you can map, which lets a scenario find the right step instead of relying on a value you typed by hand.

When to use it
you document a process or you want to loop over each step before listing its records.
Watch out
it needs a workflow to look into, so it usually follows List workflows in an application.
Risk Cloud5

List workflows in an application

SearchIn the docs only

Once you know the application, this search returns the workflows it contains, which is the middle link between an application and its steps.

When to use it
an admin wants to see how an application is organized, or a scenario must reach one workflow among several without hard coding it.
Watch out
every workflow comes out as its own bundle, so later modules multiply the operations counted on your plan.
Risk Cloud6

Make an API call

ActionIn the docs only

When the five other modules stop short, Make an API call lets you reach any endpoint of the Risk Cloud API with the connection you already set up, no second login needed.

When to use it
the operation you need has no dedicated module among the five others, and the Risk Cloud API documentation shows an endpoint for it.
Watch out
you describe the request yourself, so keep the Risk Cloud API documentation open and test with Run once first.
Need help

Need help automating Risk Cloud with Make?

A person reads every message.

FAQ

Questions about the Risk Cloud Make integration

01Is the Risk Cloud Make integration free?
Yes, Risk Cloud is a standard app, so it works on Make's Free plan. That plan keeps 2 scenarios active, waits at least 15 minutes between two scheduled runs, allows 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 operations, one per module run on one bundle. Your Risk Cloud subscription is a separate matter.
02What does the Risk Cloud Make integration need to connect?
You need an active Risk Cloud account with the right permissions and an API access token. In Make, add a Risk Cloud module, click Create a connection, optionally name it, then enter the credentials copied from Risk Cloud. The keys, a Client key and a Secret key, are managed in the API area of Risk Cloud, such as Developer Settings. If the connection asks for a bearer token, generate it from those keys and use the value called access_token.
03Does the Risk Cloud Make integration react in real time?
No, because Risk Cloud has no trigger module in Make. A scenario therefore starts in one of two ways. The first is Make's own schedule, set on the first module, which is every 15 minutes by default and never faster than 15 minutes on the Free plan. The second is a trigger from another app placed at the start, with the Risk Cloud modules after it. In both cases, a List records in a step search picks up what is in the step at the moment the scenario runs.
04What if a Risk Cloud module is missing in Make?
Use Make an API call. It reaches any endpoint of the Risk Cloud API with the same connection, which covers what the 5 dedicated modules leave out. It is the route when an operation has no module of its own, and it counts like any other module run on your plan. Test the request with Run once before you switch the scenario on. You build the request from the Risk Cloud API documentation. Also keep in mind that Make's page for this app is generated with AI from Risk Cloud's documentation, so verify important details with Risk Cloud directly.
05Make or n8n for Risk Cloud: which one fits?
It depends on what you need to reach. In Make, Risk Cloud comes with 6 modules: 4 searches that walk from applications to workflows, steps and records, Get record for one record, and Make an API call for everything else, all on the Free plan. Many apps also have an n8n node, so check whether one exists for Risk Cloud and which operations it covers. Compare the operations each tool exposes against your use case rather than picking by habit.
Same platform

Other docs you might need on this stack.

Browse all integrations