Resources · Zapier integration

Omniscope Cloud Zapier integrationAutomate Omniscope Cloud with Zapier.

The Omniscope Cloud Zapier integration gives you 0 triggers, 3 actions and 0 searches: run a project's workflow, change its parameters, or upload a file and run it on a temporary copy. Every automation starts in another app, and Omniscope does the data work.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Omniscope Cloud Zapier integration actually does

Omniscope Cloud is a data analytics platform where each project carries a workflow, the chain of steps that loads, cleans and reshapes your data. Zapier, the automation service, lets another app press the buttons for you: rerun that workflow, change the values it runs with, or feed it a new file, without opening Omniscope.

Three results that come straight out of the real operations.

Dashboards refreshed when the data lands. A new export arrives in a shared folder, and Execute Workflow reruns the project and rebuilds its outputs, so the numbers your team reads are current.

Each incoming file checked in isolation. Upload File and Execute runs a supplier's CSV through your workflow on a temporary copy, and the live project stays untouched whatever the file contains.

Reports switched to a new period from a sheet. Update Parameters changes the values a workflow uses, a region or a date range for instance, without running anything until you decide to.

What Zapier does not do here: nothing can start from Omniscope, since it has no trigger on Zapier, and there is no way to look up a project or read its results back as data. Building the workflow and its outputs stays a job for Omniscope itself.

If you are weighing other tools for the same job, see Make vs Zapier and n8n vs Zapier.

Vocabulary

The Zapier words you need, in plain English

Eight words cover everything on this page. After this list, each one is used exactly as defined.

Zap
The automation you build in Zapier: one trigger that starts it, then one or more actions that run every time that event happens.
Trigger
The event in an app that starts the Zap. Omniscope Cloud offers none on Zapier, so the trigger always comes from another app you connect.
Action
What the Zap does once it has started. Omniscope Cloud offers three: run a workflow, update parameters, or upload a file and run it.
Task
The unit Zapier bills: one action completed successfully. The monthly allowance on your plan is a count of those, nothing else.
Polling vs instant
Polling: Zapier checks the source app on a timer for new items. Instant: the app tells Zapier itself when the event happens, no waiting.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it otherwise. It needs a paid plan.
Connection
Your account of an app, linked to Zapier once and then reused by every step that uses that app, in every Zap you build.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it then requires a paid plan.
Cost

What running Omniscope from Zapier really costs

The trigger never costs anything, and neither does Zapier checking the source app for new items. What gets counted is each Omniscope action that goes through: one workflow run, one parameter update or one upload, one task each.

  • Billed per run1 task per Omniscope action that succeeds
  • Free plan100 tasks a month, two-step Zaps only
  • Reserved for paid plansNo, Omniscope Cloud works on Free
  • Integration version read<code>App235356CLIAPI@1.0.0</code>, October 2026

An action that fails is not counted. Omniscope Cloud is not reserved for paid plans, so it works on Free: 100 tasks a month, unlimited Zaps, and a check every 15 minutes on polling triggers. The catch is that Free stops at two steps. Updating parameters and then running the workflow means two actions, so the Zap becomes multi-step, needs a paid plan and costs two tasks per run. On a paid plan, a polling trigger in the starting app also checks more often, as the grid below shows.

Connect

Connect Omniscope Cloud to Zapier in three steps

  1. 01

    Open the connection dialog

    In your Zapier account, go to the Apps page and click + Add connection. You need an Omniscope Cloud account beforehand: Zapier links to an existing one, it does not create it.

  2. 02

    Find Omniscope Cloud and confirm

    Type Omniscope Cloud in the search box of the dialog, pick it from the results, then click Add connection. A new tab opens on the Omniscope side so you can sign in there.

  3. 03

    Sign in and grant access

    Log in to Omniscope Cloud in that tab and grant Zapier access to the account. The connection then sits on your Apps page, and every Zap that uses Omniscope reuses it.

First Zap

Your first Zap: every new file run through your workflow

GoalEach file dropped into a shared Google Drive folder is processed by your Omniscope workflow, and the team hears about the outcome in Slack.

  1. 01

    Pick the app that starts it

    Start building the Zap with Google Drive as the starting app, the new-file event and the folder to watch. Omniscope cannot fill this slot, since it offers no trigger on Zapier.

  2. 02

    Test the trigger

    Run the test on the trigger step. Zapier brings back the three most recent files from that folder, so you map the next steps on a real file.

  3. 03

    Add Upload File and Execute

    Choose Omniscope Cloud and this action. Paste the project URL, map the file from the trigger, and give a Filename with its extension, such as data.csv.

  4. 04

    Report the outcome

    Leave Wait for the workflow to finish on True, then add a message to your team chat with the result. Two actions make it multi-step and paid.

  5. 05

    Test, then publish

    Test each step and check that the run reports Completed. When it does, click Publish to switch the Zap on. Files added before that point are not processed.

Actions

The 3 Omniscope Cloud actions on Zapier

Omniscope Cloud gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Execute Workflow

Action

In Zapier“Runs a project's workflow on demand, refreshing its data and rebuilding outputs on your live project.”

Gets your live project to redo its work: fresh data in, outputs rebuilt, with no one clicking around in Omniscope. Set Refresh from source to True to reload everything from the original sources instead of reusing what is already loaded.

When to use it
rebuilding a dashboard as soon as the upstream export has landed.
Watch out
if the workflow is already running, the step returns an error unless Cancel any running workflow first is set to True.
2

Update Parameters

Action

In Zapier“Updates one or more workflow parameter values on a live project without running the workflow.”

Rewrites the values your workflow runs with, such as a period or a region, and stops there: nothing runs yet. Once you paste the project URL, its current values load as fields you can overwrite with data from earlier steps.

When to use it
switching a report to a new period or region, then running it in a separate step.
Watch out
nothing is recalculated here; pair it with Execute Workflow, which makes the Zap multi-step.
3

Upload File and Execute

Action

In Zapier“Uploads a file into a workflow and runs it on a temporary copy of your project, leaving the live project unchanged.”

Hands a file to your workflow and processes it on a throwaway copy of the project, so whatever the file contains, the version your team uses stays as it was. It accepts CSV, JSON, Excel, XML, Parquet and the other formats Omniscope reads.

When to use it
checking each partner's file, received by email or in a shared folder, with the same rules.
Watch out
the Filename must include its extension, because Omniscope reads the format from it.
When it breaks

When an Omniscope Cloud Zap breaks

Zapier attaches no help article and no rate limit to Omniscope Cloud, so the cases below come from the settings of the actions themselves and from limits every Zap shares. For deeper diagnosis there is Zapier troubleshooting.

Most of these show up the first time several files arrive close together, or when a setting is left on a value that does not suit the job.

  • The workflow is already running

    With Cancel any running workflow first on False, its default, a run started while another is in progress returns an error. Set it to True if your Zap can start several times in quick succession.

  • A filename without extension

    Upload File and Execute needs the extension in Filename, since Omniscope detects the format from it. Map the filename from the previous step, or type one like report.xlsx.

  • Not waiting hides failures

    With Wait for the workflow to finish on False, Zapier fires the run and moves on without the result. Keep it on True whenever a later step depends on the outcome.

  • Nothing from before the Zap

    A Zap only reacts to what happens after you switch it on. Files already sitting in the folder are not processed; running them through is a separate job.
Need help

Need help automating Omniscope Cloud with Zapier?

A person reads every message.

FAQ

Omniscope Cloud and Zapier: the questions people ask

01Is the Omniscope Cloud Zapier integration free?
Yes, on the Free plan. Omniscope Cloud is not one of the apps Zapier reserves for paid plans, so a two-step Zap, one trigger in another app followed by one Omniscope action, runs without paying. The Free plan gives you 100 tasks a month and unlimited Zaps. The limit appears the moment you want more than those two steps: updating parameters and then running the workflow, or reporting the result, means a second action, and multi-step Zaps need a paid plan. No price is quoted here, since Zapier changes its grids often.
02How many tasks does an Omniscope Cloud Zap use?
One per Omniscope action that succeeds. Running a workflow is one task, updating parameters is one task, uploading a file and running it is one task. The trigger in the other app costs nothing, and neither do the checks Zapier makes to look for new items. An action that fails is not counted. A Zap that updates parameters, runs the workflow and then posts the result in chat uses three tasks per run, so the 100 tasks of the Free plan go quickly.
03Does Omniscope Cloud react in real time with Zapier?
It depends on the app that starts the Zap. Omniscope Cloud has no trigger on Zapier, so the delay comes from that other app's trigger. If it is an instant trigger, the app reports the event itself and the plan interval does not apply. If it is a polling trigger, Zapier checks on a timer: every 15 minutes on Free, every 2 on Professional, every 1 on Team and Enterprise. Then, with Wait for the workflow to finish on True, the step waits until the run is done.
04What does connecting Omniscope Cloud to Zapier require?
An Omniscope Cloud account with at least one project, and a Zapier account. From the Apps page in Zapier, click + Add connection, search for Omniscope Cloud, then confirm with Add connection. A tab opens where you sign in and grant Zapier access. The connection is then saved and reused by every Zap that uses Omniscope. Each action also asks for a project URL, copied from your browser while the project is open, so the project must exist before you build.
05What happens if the Omniscope workflow is already running?
By default, the new run fails. Execute Workflow has a setting called Cancel any running workflow first, set to False out of the box, and in that state a second run on the same project returns an error. Switch it to True and the step stops the run in progress before starting a new one. That is the right choice when your Zap can fire several times in quick succession, for example when a batch of files lands in the watched folder together.
06What if the Omniscope Cloud operation you need is not there?
Then Zapier cannot do it today. On Zapier, Omniscope Cloud offers three actions, Execute Workflow, Update Parameters and Upload File and Execute, with no trigger and no search. Starting a Zap when a workflow finishes, creating a project or reading results back as data are out of reach. Check the Omniscope Cloud app page on Zapier before you build, since the list of operations can change. If the job depends on those moves, compare what other automation tools offer first.
07Zapier, Make or n8n for Omniscope Cloud?
It depends on the job, not on a ranking. On Zapier, the deciding facts are three actions that run, adjust or feed a workflow, no trigger, no search, and a Free plan with 100 tasks a month that stops at two steps. If your need is to launch Omniscope work from events in other tools, that covers it. If you need to react to Omniscope itself or chain many steps per run, check what other tools offer for Omniscope Cloud, and weigh what each one bills for.
Same platform

Other docs you might need on this stack.

Browse all integrations