Resources · Zapier integration

CloudApper Zapier integrationAutomate CloudApper with Zapier.

CloudApper Zapier integration: 2 triggers and 1 action, no search step. Zapier spots a record created or edited in one of your CloudApper forms and hands it to another app, or files a new record coming from elsewhere. It runs on the free plan, within limits.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the CloudApper Zapier integration does for you

It wires the forms of your CloudApper mobile app to the rest of your tools, with no code. When a record lands or changes in a form, Zapier can pass it on. When something happens in another app, Zapier can turn it into a CloudApper record your staff open on their phones.

Three results come up again and again. A field report filed in the app becomes a message for the office, through On Record Create. A record someone corrects later reaches a spreadsheet or a CRM in its fixed version, through On Record Update. And a request collected by a web form or a booking tool turns into a job card inside CloudApper, through Create New Record.

Now the part the app page leaves out. There is no search step, so a Zap can't look up an existing record before it writes. There is no action to edit or delete a record either: the only write available is a creation. And neither trigger is instant (Zapier checks on a timer), so a form submitted at the end of a shift won't show up elsewhere that very second.

That's a short list, three operations in total. It covers the classic loop of a field app (collect, notify, file) and not much beyond. If you're weighing other platforms, open the CloudApper Make integration page too, and read n8n vs Zapier before you commit.

Vocabulary

Zapier vocabulary in one minute

Eight words carry the whole page. Each one here, once, in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and nothing else.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you in another app.
Task
The unit Zapier bills. One action that completes successfully equals one task, and your plan counts those.
Polling vs instant
A polling trigger is checked on a timer for new items. An instant one is reported by the app itself, the moment it happens.
Filter
A step that lets the Zap carry on only when the incoming data meets a condition you set, and stops it otherwise.
Connection
Your CloudApper account linked to Zapier once, then reused by every step that talks to CloudApper.
Multi-step Zap
Any Zap with more than one trigger and one action. A filter or a second action makes one, and it needs a paid plan.
Cost

What a CloudApper Zap really costs

The trigger is free. Watching your forms costs nothing, however often Zapier checks. Only an action that goes through is billed, one task each.

  • Trigger check0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo

A failed action isn't counted. CloudApper is not a premium app, so the free plan works with it: 100 tasks a month, unlimited Zaps, a check every 15 minutes. The catch nobody mentions: the free plan stops at two steps, one trigger and one action. Add a filter to keep only urgent records, or a second action after the first, and the Zap turns multi-step, which means a paid plan. Keep that in mind before you sketch anything ambitious.

Connect

Connect CloudApper to Zapier in three steps

  1. 01

    Open Apps and start a connection

    In your Zapier account, go to the Apps page and click + Add connection. You do this once: every Zap you build later reuses the same CloudApper connection.

  2. 02

    Pick CloudApper

    Type CloudApper in the search box of the dialog, select it, then click Add connection. Zapier hands you over to CloudApper to prove the account is yours.

  3. 03

    Sign in and grant access

    Sign in to CloudApper in the tab that opens and allow Zapier to use the account. You need a CloudApper account, plus read or write access on any form you don't own yourself.

First Zap

Your first Zap: urgent inspections to Slack

GoalPost every new site inspection flagged as urgent to the safety team's Slack channel.

  1. 01

    Build the trigger

    Create a Zap, choose CloudApper as the app that starts it and On Record Create as the event. Fill in the user, company, app and the inspection form to watch.

  2. 02

    Test it on a real record

    Run the test. Zapier brings back the three most recent records of that form, so you pick a real inspection and see which answer marks it as urgent.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, then set the urgency answer, a text rule and the value you spotted in the test. Click Configure & test. This step makes the Zap multi-step.

  4. 04

    Add the Slack message

    Add the Slack action, pick the channel and map the inspection answers into the message. Test the step once and check what landed in Slack.

  5. 05

    Publish

    Click Publish to switch the Zap on. Only inspections filed after that moment get posted; the ones already in the form stay where they are.

Triggers

CloudApper triggers

2 events start a Zap when something happens in CloudApper. Zapier checks for them at the interval your plan allows.

1

On Record Create

Polling trigger

In Zapier“Triggers when a record is created on CloudApper.”

Starts the Zap each time someone files a new record in the CloudApper form you selected. Every answer in that record becomes material for the next steps: text for a message, a value for a filter, a line for a sheet.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a technician submits a checklist from the field and the office wants it somewhere visible without retyping a word.
Watch out
it won't run until User, Email, Company, App and Form are all filled, and each must point to something the connected account can see.
2

On Record Update

Polling trigger

In Zapier“Triggers when a record is update on CloudApper.”

Kicks in when a record that already sits in a CloudApper form gets changed: a status moves, an answer is corrected, a manager completes a missing section. The Zap then carries that record on to whatever comes next.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a sales rep fixes a visit report on the road and the CRM should hold the corrected version, not the first draft.
Watch out
edits made before the Zap is published are never picked up, so switch it on before the team starts cleaning up old reports.
Actions

CloudApper action

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

1

Create New Record

Action

In Zapier“Create a new record.”

Writes a fresh record into the CloudApper form you choose, filled with values mapped from the earlier steps, so it appears in the mobile app your staff already use.

When to use it
a request typed into a website form should arrive as a job card the field team opens on their phones.
Watch out
never aim it at the form an On Record Create trigger of the same Zap watches, or every new record restarts the Zap.
When it breaks

When a CloudApper Zap breaks

Zapier links no help article to CloudApper and documents no limit specific to it. What goes wrong is general Zapier behaviour, and a records app runs into it fast.

Four cases cover most of the surprises. If something else shows up, the Zapier troubleshooting page is the next stop.

  • Old records never come through

    A Zap only reacts to what happens after it's switched on. Records already in your forms stay put, and moving that backlog is a separate job.

  • The Zap keeps setting itself off

    Create New Record aimed at the form your trigger watches means each record it writes starts the Zap again, and the task count drains quickly.

  • A bulk import gets held back

    Loading a big batch of records at once, after a migration for example, can trip Zapier's flood protection, which holds the batch back.

  • The same record never runs twice

    Zapier keeps track of what a polling trigger has already seen, so one record doesn't start the Zap a second time on a later check.
Need help

Need help automating CloudApper with Zapier?

A person reads every message.

FAQ

CloudApper and Zapier: frequent questions

01Is the CloudApper Zapier integration free?
Yes, as long as the Zap stays small. CloudApper is not a premium app, so it works on the free plan, which gives 100 tasks a month, unlimited Zaps and a check every 15 minutes. The limit is the shape of the Zap: the free plan builds two steps, one trigger and one action, nothing more. As soon as you add a filter or a second action, the Zap becomes multi-step and needs a paid plan. Prices change too often to be worth printing here, so check the Zapier plans page before you decide.
02How many tasks does a CloudApper Zap use?
One per successful action, per run. The trigger costs nothing, and neither do the checks Zapier makes on your forms, however frequent they are. So a Zap that sends a Slack message for every new record uses one task per record. Add a second action, say Create New Record in another form, and each run uses two. An action that fails isn't counted against the plan. Be careful with loops: a Zap writing into the form its own trigger watches can eat a monthly allowance in very little time.
03Does CloudApper send records to Zapier in real time?
No. Both CloudApper triggers are polling triggers: Zapier goes to check for new or edited records on a timer, and that type is set by the app, not something you can switch in the editor. On the free plan the check runs every 15 minutes. Professional brings it down to 2 minutes, Team and Enterprise to 1 minute. On paid plans you can also run a check by hand from the editor, which helps while testing. If a Zap must react the second a form is submitted, CloudApper on Zapier won't do that.
04What does it take to connect CloudApper to Zapier?
A CloudApper account, plus read or write access on any form you don't own and want the Zap to touch. On the Zapier side, open the Apps page, click + Add connection, search for CloudApper and confirm with Add connection. A tab opens where you sign in to CloudApper and grant Zapier access. After that, every Zap reuses the connection. The usual trap comes later, when the first step asks for user, company, app and form: the account you connected must be able to see all four.
05Why does every CloudApper step ask for User, Email, Company, App and Form?
Because those five fields are required on all three operations, the two triggers and the creation action alike. They tell Zapier exactly which form inside which app and company it should watch or write into. If one of them stays empty, the step can't be tested or published. The same five come back on Create New Record, so plan them for every step. A quick check: run the trigger test and look for the three most recent records of the form you expected.
06What if the CloudApper operation you're looking for doesn't exist?
Then it isn't available on Zapier today, and there's no hidden menu to unlock it. CloudApper offers two triggers and one action, nothing to edit, delete or search records. Sometimes a different design gets you there: create a new record in a follow-up form instead of editing the first one, for instance. Otherwise, compare the list of operations each automation platform offers for CloudApper, and keep an eye on the Zapier app page, where any new operation would appear first.
07Zapier, Make or n8n for CloudApper?
It depends on three criteria rather than on a winner. First, what you need to do with records: on Zapier, CloudApper can only create them and watch for new or edited ones, with no search step. Second, speed: both Zapier triggers are polling, so reactions follow the interval of your plan. Third, Zap size: the free plan stops at two steps. Write those needs down, then check each platform's CloudApper operation list against them before you build anything.
Same platform

Other docs you might need on this stack.

Browse all integrations