Resources · Make integration

CloudApper Make integrationAutomate CloudApper with Make.

Can Make react when a record appears or disappears in CloudApper? Yes. The CloudApper Make integration offers 5 modules: 2 triggers and 3 actions. This guide shows how to link your account, build a first scenario and pick the right module.

Try the CloudApper integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the CloudApper Make integration automate?

The CloudApper Make integration links your CloudApper account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule. A module is one brick of that chain. Here, the modules can spot records that were created or deleted, add or remove records, and call the CloudApper API.

Push new records to the rest of your stack. Watch a Record Created picks up each record added in CloudApper and hands it to the next module, so another app can receive it without anyone copying it by hand.

Feed CloudApper from outside. Put the trigger of another app first, a form tool or a spreadsheet, then add Create Record: every new entry becomes a CloudApper record. Delete Record does the opposite job when something must go.

Keep a trace of deletions. Watch Record Deleted notices what was removed, which lets a scenario warn a colleague or update a list kept elsewhere.

Know the limits before you start. Make states that the documentation for this app is limited: the modules are listed without descriptions and no connection steps are given. Test each module with Run once before you rely on it, and keep Make troubleshooting close. If you are new to the editor, Make training covers the basics, and n8n vs Make helps if you are still choosing a tool.

Connect

How do you connect CloudApper to Make?

  1. 01

    Add a CloudApper module

    Open a scenario, click the + and search for CloudApper. Pick any of its modules, then click Create a connection. A connection is your CloudApper account linked to Make once and reused by every CloudApper module.

  2. 02

    Name the connection

    This step is optional, but a clear name helps when several accounts or workspaces end up in the same Make organization. Something like the team or the environment it belongs to is enough.

  3. 03

    Authorize and save

    Depending on what the screen asks, either approve Make on the CloudApper page that opens or paste the key CloudApper gives you. Then click Save. The module can now read your account.

First scenario

Your first scenario with CloudApper and Make

GoalWhen a new entry arrives in another app, Make creates a matching record in CloudApper.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the canvas. This first slot will hold the app where your data starts.

  2. 02

    Set the starting app

    Search for the app that holds the entries, a form tool or a sheet for example, pick its trigger and connect your account. Make then lists what it can read there.

  3. 03

    Add Create Record

    Click the + on the right of the first module, search for CloudApper and choose Create Record. Create the connection if this is your first CloudApper module.

  4. 04

    Map the data

    Fill the fields of Create Record with values from the first module. Each value you drop in comes from the bundle, the single item passed along, such as one form answer.

  5. 05

    Test with Run once

    Click Run once and add a test entry in the starting app. Open the bubbles above each module to read what they received, then check the new record in CloudApper.

  6. 06

    Schedule and switch on

    On the first module, open the clock and keep the default of every 15 minutes or choose another interval your plan allows. Then switch the scenario on.

Triggers

Which CloudApper triggers start a scenario?

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

CloudApper1Watch Record Deleted

Watch Record Deleted

triggerIn the docs only

This trigger reports the records that disappeared from CloudApper, so the rest of your tools learn about a removal instead of keeping stale copies. Each deleted record becomes one bundle that the next module can use.

How it fires
Make lists it as a trigger without a description; going by its name it is scheduled, meaning Make checks the app on the scenario's schedule rather than being called by CloudApper.
When to use it
a record removed in CloudApper should also be flagged or archived in another system.
Watch out
run it once on a test deletion to see what data comes back before mapping it.
CloudApper2Watch a Record Created

Watch a Record Created

triggerIn the docs only

Each record added in CloudApper starts your scenario and arrives as a bundle, ready to be sent to a CRM, a sheet or a chat channel. It is the natural first module when CloudApper is where your data is born.

How it fires
the type is deduced from the name, which points to a scheduled trigger: Make checks the app on the scenario's schedule, every 15 minutes by default.
When to use it
a new record should reach another team or tool without anyone copying it.
Watch out
each record handled counts as operations on your plan, so test with Run once first.
Modules

What can the CloudApper modules do in Make?

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

CloudApper1

Create Record

ActionIn the docs only

Create Record adds a new record in CloudApper from data that comes from earlier in the scenario, so information collected elsewhere lands in CloudApper without retyping.

When to use it
a form answer, a deal or a row in a sheet should become a CloudApper record.
Watch out
do not pair it with Watch a Record Created on the same data, or each new record would create another one.
CloudApper2

Delete Record

ActionIn the docs only

Delete Record removes a record from CloudApper, which keeps your data clean when something ends in another tool, such as a cancelled request or a closed account.

When to use it
another app tells you an item is gone and CloudApper should follow.
Watch out
a deletion cannot be undone from Make, so test it with Run once on a record you can afford to lose.
CloudApper3

Make an API Call

ActionIn the docs only

Make an API Call reaches any endpoint of the CloudApper API with the same connection, covering whatever the four other modules leave out.

When to use it
the action you need has no dedicated module in the list.
Watch out
you write the request yourself, so run it once and read the bundle it returns before mapping anything.
Need help

Need help automating CloudApper with Make?

A person reads every message.

FAQ

CloudApper and Make: common questions

01Is the CloudApper Make integration free?
Yes, it is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, up to 5 minutes per execution, 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, remove the cap on active scenarios and allow 40 minutes per execution. Usage is counted in operations, one per module run on one bundle. Any CloudApper subscription is a separate matter.
02What do you need to connect CloudApper to Make?
A CloudApper account and a Make account. The Make documentation lists no specific prerequisite for this app and gives no dedicated connection steps, so the generic flow applies: add a CloudApper module, click Create a connection, name it if you like, then either authorize Make on the CloudApper page or paste the key CloudApper provides, and click Save. The connection is stored once and every CloudApper module in your scenarios reuses it.
03Does the CloudApper trigger in Make fire instantly?
No, not as far as the documentation shows. Both triggers, Watch a Record Created and Watch Record Deleted, are listed without a description, and their names point to scheduled triggers. Make checks CloudApper on the schedule of the scenario, every 15 minutes by default. On the Free plan the shortest interval is 15 minutes; paid plans go down to 1 minute. A record created just after a check is picked up at the next one.
04What if a CloudApper module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the CloudApper API with the connection you already have, so an action without a dedicated module is still within reach. Keep in mind that Make describes the documentation for this app as limited, so you shape the request yourself and check the result. Test the call with Run once before switching the scenario on. Each call counts as one operation on your plan, like any other module.
05Should you use Make or n8n for CloudApper?
It depends on the tool you already run. In Make, CloudApper comes with 5 modules: 2 triggers, Create Record, Delete Record and Make an API Call for the rest. Many apps also have an n8n node, so check whether CloudApper is one of them before choosing. The decision then rests on which editor your team knows and where your other automations live, since keeping them in one place is easier to maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations