Resources · Zapier integration

MFPInTheCloud Zapier integrationAutomate MFPInTheCloud with Zapier.

MFPInTheCloud Zapier integration: 1 trigger, 1 action and 0 searches. A new file in MFPInTheCloud can start a Zap, and a Zap can launch one of your MFPInTheCloud workflows. Here is what each step does, what it costs and where it breaks.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MFPInTheCloud Zapier integration does for you

The integration links your MFPInTheCloud account to the other apps you use, through Zapier. MFPInTheCloud lets you manage your MFPs from one app and design document flows, with OCR, conversions and PDF signing among its tools. Zapier sees one event there, a new file, and offers one move, starting a workflow. Everything on this page comes back to those two.

A file that leaves a trace elsewhere. With the Workflow trigger, each new file added in MFPInTheCloud can start a Zap that writes a line in your spreadsheet or posts a note in your team chat.

A workflow launched from a Zap. Start Workflow runs one of your MFPInTheCloud workflows. It asks for the workflow's id, found on your settings page, and the file's full name.

Two workflows in a row. Put both together: a new file starts the Zap, and Start Workflow hands that same file to a second workflow, with the name taken from the trigger step. That pair fits in one two-step Zap, so the free plan covers it.

What Zapier does not do here: there is no search step, so a Zap cannot look up a file or a workflow that already exists in MFPInTheCloud. There is no instant trigger either, so every new file waits for Zapier's next check. If you are still choosing a tool, open our n8n vs Zapier comparison, or see our Zapier review.

Vocabulary

Zapier words, in plain English

Eight terms come back on every line of this page. One sentence each.

Zap
Your automation on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event that starts the Zap. Here, a new file added in MFPInTheCloud. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something. Here, Start Workflow.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items and keeping only the ones it has not seen. Workflow is one.
Instant trigger
A trigger the app reports itself, calling Zapier when the event happens. MFPInTheCloud has none on Zapier.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
Cost

What an MFPInTheCloud Zap really costs

The trigger never costs a task, and neither do Zapier's checks for new files, however often they run. Only a completed action is billed: each successful Start Workflow counts one task, and a run that fails costs nothing.

  • Workflow triggerNever counted
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo, works on the free plan

MFPInTheCloud is not a premium app, so it works on the free plan: 100 tasks a month and unlimited Zaps, each limited to two steps. That covers Workflow followed by Start Workflow, and nothing more. Add a filter or a second action and the Zap turns multi-step, which needs a paid plan. Note that a few apps and a few actions take more than one task when they complete. The grid below sets how often Zapier checks the Workflow trigger, plan by plan.

Connect

Connect MFPInTheCloud to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to the Apps page and click + Add connection. A connection is your MFPInTheCloud account linked once, then reused by every step of every Zap that touches it.

  2. 02

    Pick MFPInTheCloud

    Type MFPInTheCloud in the search box of the dialog, pick it, then click Add connection. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.

  3. 03

    Sign in and grant access

    A new tab opens on MFPInTheCloud. Sign in there with the account the Zap should use, then grant Zapier access to it. Back in the editor, that connection is the one you pick for both the trigger and the action.

First Zap

Your first Zap: send selected files to a second workflow

GoalEach new file added in MFPInTheCloud starts the Zap, a filter keeps only the files that match your rule, and Start Workflow passes them to another workflow.

  1. 01

    Set the trigger

    Create a new Zap, pick MFPInTheCloud as the app that starts it and Workflow as the event. Choose the connection you added above.

  2. 02

    Test the trigger

    Run the trigger test. Zapier brings back the three most recent items of the connected account, so you map the next steps on a real file. Read what came back before going further.

  3. 03

    Add the filter

    Add a Filter step from the plus icon and fill its three boxes: the field to look at, the rule and the value. Pick a text rule for text. This step makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add Start Workflow

    Add MFPInTheCloud again, this time with Start Workflow. Paste the id from your settings page in Workflow, then map the file's full name from the trigger step into File Name.

  5. 05

    Test, then publish

    Test the action once and check what came back. Then click Publish to switch the Zap on. For more hands-on practice, see our Zapier training.

Triggers

The MFPInTheCloud trigger

1 event starts a Zap when something happens in MFPInTheCloud. Zapier checks for them at the interval your plan allows.

1

Workflow

Polling trigger

In Zapier“Trigger when a new file is added”

Each time a new file is added in MFPInTheCloud, this trigger hands it to your Zap, so the next steps can work with it. It is the only event in MFPInTheCloud that can start a Zap, and the one that feeds the File Name field of Start Workflow.

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 file added in MFPInTheCloud should set off something in another tool, or a second workflow.
Watch out
the operation is named Workflow, yet the event is a new file; check at the test which files it brings back.
Actions

The MFPInTheCloud action

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

1

Start Workflow

Action

In Zapier“Start a new workflow”

Launches one of your MFPInTheCloud workflows from the Zap, on the file you name. Two fields are required: Workflow, the workflow's id from your settings page, and File Name, the file's full name.

When to use it
a file came in through the Workflow trigger and should go through another set of processing steps.
Watch out
each successful run counts one task.
When it breaks

When an MFPInTheCloud Zap breaks

Zapier links no help article to MFPInTheCloud, so the limits below are Zapier's general ones. They still apply here.

These cases cover what the Zap does not see, or sees too much of. When a run fails and the cause is not obvious, see our Zapier troubleshooting guide.

  • Files from before the Zap are ignored

    A Zap reacts only to what happens after you switch it on. Files already in MFPInTheCloud never start it; moving that backlog is a separate job.

  • A Zap that sets itself off

    A general precaution: a Zap that writes into the place its own trigger watches can start itself again and again and burn through your tasks. Check at the test what a started workflow produces.

  • A sudden batch is held back

    After a bulk import or a migration, a trigger that returns a huge batch at once can be held back by Zapier's flood protection.

  • The same file is not sent twice

    Zapier keeps track of what it has already seen on a polling trigger, so a file that was picked up once does not start the Zap a second time.
Need help

Need help automating MFPInTheCloud with Zapier?

A person reads every message.

FAQ

MFPInTheCloud and Zapier: frequent questions

01Is the MFPInTheCloud Zapier integration free?
Yes, it works on Zapier's free plan, because MFPInTheCloud is not a premium app. The free plan gives you 100 tasks a month and an unlimited number of Zaps, each limited to two steps: one trigger and one action. That is exactly enough for Workflow followed by Start Workflow. A filter or a second action turns the Zap into a multi-step Zap, and that needs a paid plan. On the free plan, Zapier also checks the Workflow trigger every 15 minutes.
02How many tasks does an MFPInTheCloud Zap use?
One task per successful action, and nothing else. The Workflow trigger never costs a task, and Zapier's checks for new files are free however often they run. If Start Workflow fails, that run is not counted. So a Zap that launches a workflow for each new file uses one task per file that goes through. Add a second action and each file then costs two tasks, one per action that succeeds.
03Does a new MFPInTheCloud file start the Zap instantly?
No. Workflow is a polling trigger: Zapier goes and looks at regular intervals, and how often depends on your plan, every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. The type comes from the app itself and cannot be switched in the editor. On paid plans you can also run a check by hand from the editor while you build. Testing the trigger also brings back the three most recent items of the account, so you set things up on a real file.
04What does it take to connect an MFPInTheCloud account?
An account on MFPInTheCloud, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection starts from the Apps page of your Zapier account with + Add connection. You then sign in to MFPInTheCloud in the tab that opens and grant Zapier access. Once linked, every Zap that uses MFPInTheCloud reuses that same connection. Pick that account carefully: every step built on this connection acts through it.
05Where does Start Workflow get its workflow id?
From your MFPInTheCloud settings page, according to the field's own note in Zapier. Workflow is a required field: without that id, the action has nothing to launch. The other required field, File Name, wants the file's full name, and its note says that name comes from the trigger step. That is why the cleanest setup pairs both operations. Check at the test that the id you pasted points to the workflow you meant.
06What if the MFPInTheCloud operation you want is not there?
Then this integration cannot do it as it stands. The editor offers one trigger and one action for MFPInTheCloud, and no search, so a Zap cannot look up an existing file. The MFPInTheCloud page on Zapier shows the current list, so compare your need with it before you design the rest of the Zap. If the step you want is missing, plan the Zap around the two operations that exist, or keep that part of the work outside Zapier.
07Zapier, Make or n8n for MFPInTheCloud?
It depends on your criteria, not on a ranking. Start with the catalogue: check that each tool offers a ready-made MFPInTheCloud step, since nothing else matters without it. On Zapier you get 1 trigger and 1 action, usable on the free plan and billed per successful action. Then weigh how quickly new files must be seen: the trigger polls, so your plan's interval sets the pace. Last, think about who will maintain the automation and which editor they find easiest.
Same platform

Other docs you might need on this stack.

Browse all integrations