Resources · Zapier integration

mfr - field service management Zapier integrationAutomate mfr - field service management with Zapier.

mfr - field service management Zapier integration: 5 triggers, 16 actions and 7 searches. Jobs, customers, locations, appointments and reports in mfr can start a Zap or be written by one. Here is what each step does, what it costs and what breaks.

See the 28 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the mfr - field service management Zapier integration does

The integration links your mfr account to the rest of your tools through Zapier. mfr is a field service platform: it dispatches technicians and organises the jobs they carry out on site. On Zapier, it reports five events (new jobs, customers, locations, appointments, job state changes) and accepts 16 actions and 7 searches.

A job that lands with the right technician. New Job starts the Zap, Find Best Technician ranks who fits by location, availability, qualifications and workload, and Change Job Owner hands the job over.

A customer and a job opened from outside mfr. When a request arrives in your form tool, Create Customer and Create Job set both up in mfr, the job tied to the customer who pays the bill.

Paperwork that follows the job. Job State Change Event can call Generate Report on that job, or Create Invoice Draft from it, so the document exists without anyone opening mfr.

The detail that matters most on a free plan: all five mfr triggers are instant. mfr tells Zapier itself, so the plan's polling interval never applies to them.

What Zapier does not do here: no action deletes anything in mfr, and no search offers a find-or-create variant. To weigh Zapier against other tools, open our Make vs Zapier comparison or see our Zapier review.

Vocabulary

Zapier words, in plain English

Eight terms carry this page. One line each.

Zap
Your automation on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event that starts the Zap, such as a new job in mfr. Once the Zap is switched on, Zapier waits for it.
Action
What the Zap does once started: the step that writes, sends or moves something, such as Create Job.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan counts those.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. None of the mfr triggers works this way.
Instant trigger
A trigger the app reports itself: it calls Zapier the moment the event happens. All five mfr triggers are instant.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something already in an app, such as a job or a customer, so later steps can use what it found.
Cost

What an mfr Zap really costs

The trigger never costs a task. Only a completed action is billed: each successful Create Job, Update Job or Upload Document counts one task, and an action that fails costs nothing.

  • TriggerNever counted
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • mfr triggers5 instant, interval not applied

mfr is not a premium app, so it runs on the free plan: 100 tasks a month and unlimited Zaps, each limited to one trigger and one action. Add a search like Find Best Technician, a filter or a second action, and the Zap becomes multi-step, which needs a paid plan. A few apps and actions take more than one task when they complete. The grid below is Zapier's polling interval per plan; it does not apply to the mfr triggers, which are all instant.

Connect

Connect mfr to Zapier in three steps

  1. 01

    Open the Apps page

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

  2. 02

    Pick mfr

    Search for mfr - field service management in the dialog, pick it and 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

    Sign in to mfr in the tab that opens, then grant Zapier access to the account. Back in the editor, that connection is the one you choose on every mfr trigger, action and search.

First Zap

Your first Zap: hand each new job to the best technician

GoalEvery new job in mfr starts the Zap, Find Best Technician picks who fits it, and Change Job Owner makes that person the owner.

  1. 01

    Set the trigger

    Create a new Zap, pick mfr - field service management as the app and New Job as the event, then choose your mfr connection.

  2. 02

    Test it on a real job

    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 job. Read what came back before going further.

  3. 03

    Add the search

    Add Find Best Technician and map the job's id into Service Request ID. Turn on Return Only Best Match if one name is enough. This search makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add Change Job Owner

    Add Change Job Owner, map the job's id into Service Request ID, then map the technician the search returned. The owner can be given by email or internal ID; check at the test which value fits.

  5. 05

    Test, then publish

    Test each step once and read what came back. Then click Publish to switch the Zap on. For a guided practice run, see our Zapier training.

Triggers

The mfr - field service management triggers

5 events start a Zap when something happens in mfr - field service management, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Appointment

Instant trigger

In Zapier“Triggers when a new appointment is created.”

A fresh appointment created in mfr hands its details to your Zap. Zapier puts this one forward on the app page, and it is the natural start for anything that should mirror a technician's schedule in another tool, such as a shared calendar or a team chat.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your office wants a line or a message for every appointment booked in mfr, without opening the planner.
2

New Customer

Instant trigger

In Zapier“Triggers when new customer is created.”

Whenever someone adds a customer in mfr, this trigger passes the new record on. Its key says company, its label says customer: it is the same thing, the account that pays for the work.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your invoicing or contact tool should hold the same customers as mfr, and nobody wants to type them twice.
Watch out
if another Zap also creates customers in mfr, check that the two do not keep feeding each other.
3

New Location (Service Location)

Instant trigger

In Zapier“Triggers when new location (service location) is available.”

Fires on each service location that becomes available in mfr, the place where a job will take place. It lets the address side of your work travel to other tools as soon as mfr knows it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a dispatcher keeps a list of sites in a spreadsheet, or a map tool needs every new address.
Watch out
a location is not a customer; use New Customer for the paying account.
4

New Job

Instant trigger

In Zapier“Triggers when new job was created.”

Each job created in mfr starts the Zap with that job in hand. Zapier puts it forward, and it suits Zaps around dispatching: assign, notify, log.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
new work should reach a person or a tool without anyone watching the mfr job list.
Watch out
in the Zapier fields, a job is often called a service request; the Service Request ID of the later steps is the job's id.
5

Job State Change Event

Instant trigger

In Zapier“Triggers when a job state changed.”

When a job moves from one state to another in mfr, this trigger reports it. That makes it the hook for everything that should happen at a given stage of the job, from a report to a follow-up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a finished job should produce its report, or a stalled one should alert the office.
Watch out
Service Request State is a required field, so you select a state when you set the trigger; check at the test which changes it picks up.
Actions

The mfr - field service management actions

mfr - field service management gives you 16 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Tag to Entity (Job)

Action

In Zapier“Adds a tag to an entity like a (job).”

Attaches a tag to a job, using its entity id, the entity type and the tag id. Tags in mfr help filter and spot certain job states, such as Installation, Maintenance or Repair.

When to use it
jobs coming from one channel should be marked so the office can sort them.
2

Change Job Owner

Action

In Zapier“Changes the current owner of an existing Job in MFR. You can specify the owner by email or internal ID.”

Gives an existing job a new owner, named by email or by internal ID. The job is pointed to by its Service Request ID.

When to use it
a Find Best Technician search has picked someone and the job should land on that person.
Watch out
check at the test which owner value the search hands over.
3

Create Appointment

Action

In Zapier“Create an appointment (holiday,Illness,appointment) in mfr.”

Puts an appointment in a technician's mfr schedule: illness, vacation or others, meaning anything not tied to a job. It needs the type, a start date and time in the format 2021-06-02T14:45:48Z, a duration in minutes and the technician's username.

When to use it
absences recorded in another tool should block the technician's mfr schedule.
Watch out
without a duration, mfr counts 120 minutes from the start.
4

Create Customer

Action

In Zapier“Creates a customer with a unique customer id in mfr.”

Adds a customer to mfr with its own unique customer id. The Customer Name is required: it is the name on the invoice address.

When to use it
a deal won in your sales tool should exist as a customer in mfr before the first job.
Watch out
for a private individual, Create Customer Single Person fits better.
5

Create Customer Single Person

Action

In Zapier“Creates a customer of type single person along with location and with a unique customer id in mfr.”

Creates a customer of the single-person type, with a location and a unique customer id. It asks for a first name and a last name, both used for the invoice address, instead of a company name.

When to use it
your bookings come from private households rather than businesses.
6

Create Follow-Up Job

Action

In Zapier“Creates a follow-up Job in mfr based on an existing service request. Allows cloning various aspects of the original job and scheduling appointments.”

Builds a second job from an existing one, the Original Service Request ID. You decide what carries over from the first job, comments, documents, tags or open appointments among them, and appointments can be scheduled along the way.

When to use it
a visit ends with work left to do and the next one should start with the history attached.
7

Create Invoice Draft

Action

In Zapier“Creates a new Invoice draft in mfr either from an existing Offer or a Job.”

Prepares an invoice draft in mfr, starting either from an existing offer or from a job. What it creates is a draft, not a finished invoice.

When to use it
a job reaching its final state should leave a draft waiting for the accounts team.
8

Create ItemType

Action

In Zapier“Create an itemtype (material, service, equipment) in mfr.”

Adds an item type to mfr, whether material, service or equipment. It takes a short name and an ItemType Id that must be unique across the whole system.

When to use it
your product list lives in another tool and mfr should follow it.
Watch out
an id already in use elsewhere in mfr will clash.
9

Generate Report

Action

In Zapier“Generates new Report for a job id. Please provide a job id and a report definition code.”

Produces a report for a given job, from a job id and a report definition code such as R-212. The code comes from Tools > ReportDefinitions in mfr.

When to use it
every completed job should come with its report, without anyone clicking through mfr.
Watch out
the code must match a report definition in mfr; check it at the test.
10

Create Location (Service Location)

Action

In Zapier“Create a location (service location) with a contact. This is an important job information for the technician.”

Records a service location with a contact, which mfr treats as key job information for the technician. A Location Name and an Address, street plus house number, are required.

When to use it
a new site comes in with an order and should be ready before the job is planned.
11

Create Job

Action

In Zapier“Creates a new Job in mfr. Jobs always have a job description and can be created from a job template.”

Opens a new job in mfr, with its description, and can start from a job template. The Job Name is what you will type in the mfr global search later, and the Customer Id ties the job to the customer who pays.

When to use it
a request accepted elsewhere should become a job without retyping.
Watch out
the customer must exist first.
12

Create Time Event

Action

In Zapier“Create a time event (working, driving, vacation, illness, etc.) in MFR.”

Logs a time event for a technician in mfr: working, driving, vacation, illness and similar types. You give the type and the technician's username, which is an email, and can mark the event as approved.

When to use it
hours tracked in another tool should land in mfr.
Watch out
Working and Driving require a Service Request ID.
13

Remove Tag From Entity (Job)

Action

In Zapier“Removes a tag from an entity like a (job).”

Takes a tag back off a job, with the same three inputs as adding one: entity id, entity type and tag id.

When to use it
a temporary marker, such as a waiting state, should disappear once the job moves on.
Watch out
you need the tag's id, not its label.
14

Update Job

Action

In Zapier“Updates an existing Job in MFR. You can update the name, description, state, current owner, and target time.”

Changes an existing job in mfr: its name, description, state, current owner or target time. The Service Request ID tells it which job to touch.

When to use it
a reply from the customer in another tool should move the job forward or shift its target time.
15

Upload Document

Action

In Zapier“Uploads a document.”

Sends a file into mfr and attaches it to a job. It needs a filename, the file itself and the job id.

When to use it
a signed form or a photo collected elsewhere belongs in the job file.
Watch out
the File field expects an actual file from an earlier step, not just its name.
16

Upload Purchase Invoice

Action

In Zapier“Uploads a purchase invoice (additional cost item) to MFR.”

Uploads a purchase invoice to mfr as an additional cost item, PDF or image, with its filename. Both the filename and the file are required.

When to use it
supplier invoices arrive by email or in a storage folder and should be logged in mfr as costs.
Searches

The mfr - field service management searches

7 search steps look for data that already exists in mfr - field service management, so a later step can use it.

A search looks up what already exists in mfr and hands it to the next steps. In the editor, searches sit at the bottom of the Action event list under SEARCH. Three settings decide what happens when the result is not a clean single match.

1

Find Best Technician

Search

In Zapier“Find the best available technician for a service request based on location, availability, qualifications, and workload.”

Ranks the technicians who fit a job, weighing location, availability, qualifications and workload. You give the job's Service Request ID, and Return Only Best Match keeps only the top name.

When to use it
dispatching should start from a recommendation instead of a guess.
2

Find Company (Customer)

Search

In Zapier“Find a Company”

Looks up a customer that already exists in mfr, so a later step can lean on it instead of creating a duplicate.

When to use it
a request arrives for a known customer and the job must be tied to the right account.
Watch out
check at the test which value goes into Customer Id.
3

Find ItemType

Search

In Zapier“Finds an itemtype by id or by name.”

Finds an item type, either by its id or by its name.

When to use it
a line on an order names a product and you need the matching mfr item type before using it.
Watch out
whether the name must match exactly is up to mfr; check at the test.
4

Find Location (Service Location)

Search

In Zapier“Find a Location”

Fetches a service location already recorded in mfr, so a later step can reuse it rather than create a duplicate site with the same address.

When to use it
repeat visits to the same site should point to the location you already have.
5

Find Job

Search

In Zapier“Find a job in the mfr account by its job id.”

Looks a job up in your mfr account by its job id. The job it returns can drive an update, a tag or a report later in the Zap.

When to use it
another tool carries the job id and you need the job's current details.
6

Find User

Search

In Zapier“Find a user by email or externalid.”

Finds a user of your mfr account by email or by external id.

When to use it
a technician is known by email in another tool and a later step, a time event for instance, needs the matching mfr user.
7

Get Job by Id

Search

In Zapier“Returns the job by Id”

Returns one job from its ServiceRequest Id, a required field. Next to Find Job, it is the direct route when the id is already in hand.

When to use it
an earlier step passed the id along and the Zap needs the full job before acting.

The three settings every search exposes

  1. Successful if no search results are found?
    Left as is, a search that finds nothing stops the Zap there and the steps that depend on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. None of the mfr searches offers that variant on Zapier, so you will not see it here.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks

When an mfr Zap breaks

Zapier links no help article to mfr, so the cases below are Zapier's general limits. They apply to every mfr Zap.

Here are the general limits to know before you publish. When a run fails and the reason is not obvious, see our Zapier troubleshooting guide.

  • Old jobs are not picked up

    A Zap reacts only to what happens after you switch it on. Jobs, customers or appointments already in mfr 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 your trigger and actions at the test.

  • A bulk import 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.

  • A missing id stops the step

    Many mfr actions need an existing id: customer, job, tag or report definition. When an earlier step does not carry it, add a search such as Find Job or Find Company first.
Need help

Need help automating mfr - field service management with Zapier?

A person reads every message.

FAQ

mfr and Zapier: frequent questions

01Is the mfr - field service management Zapier integration free?
Yes. mfr is not a premium app, so it works on Zapier's free plan. That plan gives you 100 tasks a month and as many Zaps as you like, each with two steps: one trigger and one action. New Job followed by an action in your team chat fits. A Zap that adds Find Best Technician, a filter or a second action becomes multi-step, and that needs a paid plan.
02How many tasks does an mfr Zap use?
One per successful action, nothing for the rest. The trigger never costs a task. A search like Find Best Technician makes the Zap multi-step, and each action that completes, such as Change Job Owner, counts one task. An action that fails is not counted. So a Zap that creates a customer, then a job, uses two tasks per request. With the free plan's 100 tasks a month, count your expected jobs times the actions in the Zap.
03Are the mfr triggers real time?
Yes, all five of them. New Appointment, New Customer, New Location, New Job and Job State Change Event are instant triggers: mfr tells Zapier the moment the event happens, so the Zap starts right away, whatever your plan. The polling intervals of the plan grid do not apply to them. In the editor, a Zap built on an instant trigger shows a lightning bolt, which is a quick way to confirm it.
04What does it take to connect an mfr account?
An account on mfr, plus read or write access on anything you do not own yourself and want the Zap to touch. You start from the Apps page of your Zapier account, click + Add connection, search for mfr - field service management, sign in in the tab that opens and grant Zapier access. That single connection then serves every mfr trigger, action and search in all your Zaps, so pick the account with care.
05Why does Create Time Event fail on working hours?
Because the Working and Driving types require a Service Request ID, the id of the job those hours belong to. Vacation or illness can be logged without a job; working and driving cannot. Map the job's id from an earlier step, a Job State Change Event trigger or a Find Job search for instance. The technician is named by username, which is an email, so make sure the address matches the one in mfr.
06What if the mfr operation you want is not offered?
Then this integration cannot do it as it stands. On Zapier, mfr offers 5 triggers, 16 actions and 7 searches; nothing deletes a record, for example. The mfr - field service management page on Zapier shows the current list, so compare your need with it before you build. When a step is missing, shape the Zap around what exists, such as a tag or a state change, or keep that part in mfr itself.
07Zapier, Make or n8n for mfr?
It depends on your criteria, not on a ranking. First, check whether each tool has a ready-made mfr connector, because without one everything else is moot. On Zapier, mfr brings 28 operations and five instant triggers, so the polling interval does not apply and new jobs reach the Zap right away on any plan. Then look at billing: Zapier counts each successful action. Finally, think about who will maintain the automation, and which editor that person reads most easily.
Same platform

Other docs you might need on this stack.

Browse all integrations