Resources · Make integration

mfr field service management Make integrationAutomate mfr field service management with Make.

Can Make run your field service desk while your technicians stay on the road? The mfr field service management Make integration gives you 25 modules: 1 trigger, 18 actions and 6 searches. This guide shows how to connect your account and build a first working scenario.

Try the mfr field service management integration on MakeSee the 25 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the mfr field service management Make integration automate?

It links your mfr field service management account to Make, so service requests, companies, appointments and documents can move between mfr and your other tools without code. You build a scenario, which is the automation itself: a chain of modules, each module being one brick that watches, creates, reads or searches something.

Requests that open themselves. A support form or a CRM sits in front of mfr. When a customer reports a broken machine there, Create a Service Request opens the job in mfr, and Find Best Technician suggests who should take it. Nobody retypes the ticket.

Clean records before the visit. A new client signs in your sales tool: Create a Company and Create a Service Object register the customer and the equipment you maintain, so the first appointment starts from a complete file. Create an Appointment can then book the slot.

Follow-ups nobody forgets. Watch Events picks up what happens in mfr, and Create Follow-up Service Request or Add tags to Service Request keep the next step visible for the back office.

Keep one limit in mind: Make itself says its documentation for this app is limited, because little public information exists about it. Test every module with Run once before trusting it. If you are weighing tools, read n8n vs Make, check the plans in Make pricing, or learn the editor with Make training.

Connect

How do you connect mfr field service management to Make?

  1. 01

    Add a module and create the connection

    Drop any mfr field service management module into your scenario and click Create a connection. A connection is your mfr account linked to Make once, then reused by every mfr module in every scenario.

  2. 02

    Name it so you can find it later

    Giving the connection a name is optional, but it helps when you manage several mfr accounts, such as a test tenant and your live one. Pick something your colleagues will recognize.

  3. 03

    Authorize Make and save

    Depending on what mfr asks for, approve Make on the mfr page that opens, or paste the key your mfr account gives you. Then click Save, and the module can read your data.

First scenario

Your first scenario with mfr field service management

GoalWhen a customer reports an issue in another app, Make opens a service request in mfr field service management and looks for the right technician.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + to add the first module. Here it comes from the app where customers report problems, such as your form tool or helpdesk.

  2. 02

    Add Create a Service Request

    Click the + on the right of the first module, search for mfr field service management and pick Create a Service Request. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the customer data

    Fill the module with data from the previous module: Make shows what arrived in each bundle, one bundle being one item passed from module to module, here one reported issue.

  4. 04

    Add Find Best Technician

    Add the next module with the + and choose Find Best Technician. The documentation lists no fields, so open the module and see what it asks for, mapping what the request module returned. Then decide what to do with the suggestion.

  5. 05

    Test with Run once

    Click Run once and send a test issue from the first app. Open each module's bubble to read the bundles it received and check that the request really appeared in mfr.

  6. 06

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Triggers

What can start a scenario in mfr field service management?

1 module starts a scenario when something happens in mfr field service management. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by mfr field service management as soon as it happens.

mfr field service management1Watch Events

Watch Events

triggerIn the docs only

Watch Events hands your scenario the new events it finds in mfr field service management, so the rest of the chain can react to what happens on your service desk. Make gives no official description of which events it covers, so a first Run once is the best way to see what it returns.

How it fires
scheduled: Make checks the app on the scenario's schedule, shown by the clock badge on the module.
When to use it
whenever a change in mfr should notify a team, update another tool or open a follow-up.
Watch out
on the Free plan the shortest interval is 15 minutes, so reactions are never immediate.
Modules

What can each mfr field service management module do?

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

mfr field service management1

Add tags to Service Request

ActionIn the docs only

This module labels an existing service request, which makes it easy for dispatchers to filter jobs by urgency, contract or region inside mfr without opening each one.

When to use it
after another module has decided something about a request, for example that the customer holds a priority contract.
Watch out
it adds labels only; to take one off, use Remove Tag From Service Request.
mfr field service management2

Create Follow-up Service Request

ActionIn the docs only

Here you get a new job chained to an earlier one, so the history of a repair stays in one thread instead of scattered tickets.

When to use it
when a first visit ends with a missing part or a second intervention to plan.
Watch out
it needs the original request, so place a Get or List module before it if the scenario does not already carry that request.
mfr field service management3

Create Time Event

ActionIn the docs only

Time spent on a job lands in mfr as a time event, which keeps billing and workload reports closer to what really happened on site.

When to use it
when hours are captured elsewhere, such as a timesheet app or a form technicians fill after a visit.
Watch out
the documentation says nothing about the expected format, so check the result in mfr after your first Run once.
mfr field service management4

Create a Company

ActionIn the docs only

With this module, a new customer account appears in mfr straight from the tool where the deal was closed, with no copy and paste between systems.

When to use it
when a CRM or signed quote marks the start of a service relationship.
Watch out
run List Companies first if the same customer might already exist, otherwise you risk duplicate accounts.
mfr field service management5

Create a Service Object

ActionIn the docs only

A service object is the equipment you maintain, and this module registers it in mfr so every future job can point at the right machine.

When to use it
when a sale or installation adds a unit at a customer site and the record should exist before the first maintenance.
Watch out
link it to the right company, which usually means a Get a Company or Create a Company module earlier in the chain.
mfr field service management6

Create a Service Request

ActionIn the docs only

This is the module that opens a job in mfr from outside, turning an email, a form entry or a helpdesk ticket into work your dispatchers can plan.

When to use it
whenever customers report problems somewhere other than mfr and you want the request logged without retyping.
Watch out
each run creates a new request, so filter test data before you switch the scenario on.
mfr field service management7

Create an Appointment

ActionIn the docs only

Booking a visit becomes automatic: the module places an appointment in mfr, so the planning board reflects what was agreed with the customer.

When to use it
when the slot is chosen in another tool, like a booking page or a call with the customer logged in your CRM.
Watch out
pair it with Find Best Technician when you do not already know who should go.
mfr field service management8

Create an Item Type

ActionIn the docs only

Your catalog of parts or services grows in mfr without manual entry, because this module adds an item type from data held elsewhere.

When to use it
when a new reference is added in your ERP or stock sheet and technicians should be able to use it on jobs.
Watch out
check List Item Types first so the same reference does not end up in mfr twice.
mfr field service management9

Delete a Service Request

ActionIn the docs only

This module removes a service request from mfr, which keeps the board clean when a job was opened by mistake or cancelled upstream.

When to use it
when a cancellation in another system must be mirrored in mfr.
Watch out
nothing in the documentation mentions a way to restore a deleted request, so add a filter before it and test on a dummy request with Run once.
mfr field service management10

Find Best Technician

SearchIn the docs only

Instead of guessing who is free, you ask mfr which technician suits a job, and the answer feeds the next module of your scenario.

When to use it
right after a request is created, before booking the appointment or alerting the person in charge.
Watch out
as a search module it can return zero, one or several results, so plan what happens when nobody comes back.
mfr field service management11

Generate Report

ActionIn the docs only

A report comes out of mfr on demand, ready to be sent or filed by the modules that follow, so nobody has to export it by hand.

When to use it
when a job closes and the customer or your manager expects a document summarizing the intervention.
Watch out
the documentation does not describe the output, so look at the bundle after Run once before mapping it into an email.
mfr field service management12

Get a Company

ActionIn the docs only

Get a Company brings back one customer account from mfr, so later modules can use its details without a second lookup.

When to use it
when you already hold the company's identifier from a previous module and want its full record, for example to address a report.
Watch out
it reads a single company; to browse or match by name, List Companies fits better.
mfr field service management13

Get a Service Object

ActionIn the docs only

This module fetches one piece of equipment from mfr, giving your scenario what it needs to describe the machine in a message or another app.

When to use it
when a request points at a service object and your technician or supplier should receive its details.
Watch out
you need the object's identifier; without it, start with List Service Objects.
mfr field service management14

Get a Service Request

ActionIn the docs only

You get the full content of one job in mfr, which is handy when an earlier module only passed along a reference.

When to use it
after Watch Events, to read the request behind an event before deciding what to do next.
Watch out
it returns one request only, so check with Run once that the reference you map really reaches the module.
mfr field service management15

Get an Item Type

ActionIn the docs only

One item type comes back from your mfr catalog, so a scenario can reuse its details in a quote, a stock alert or a purchase order.

When to use it
when a job references a part and another tool needs to know what that part is.
Watch out
it reads a single entry; if you do not have its identifier yet, begin with List Item Types.
mfr field service management16

List Companies

SearchIn the docs only

Your customer accounts come out of mfr as separate bundles, one per company, which lets the scenario compare, sync or check them one by one.

When to use it
before creating a company, to see whether it already exists, or to copy the list into a spreadsheet.
Watch out
every company returned can trigger an operation in each following module, which adds up on your plan.
mfr field service management17

List Item Types

SearchIn the docs only

The whole catalog of item types in mfr becomes available to the scenario, bundle by bundle, ready to be matched against another source.

When to use it
to keep a stock sheet or an ERP aligned with the references your technicians see in mfr.
Watch out
a search can return nothing; add a filter or a fallback path so the scenario does not stop silently.
mfr field service management18

List Service Objects

SearchIn the docs only

This search returns the equipment registered in mfr, so you can review the installed base or push it to another tool without exporting it.

When to use it
when a manufacturer recall or a maintenance campaign means finding every unit concerned.
Watch out
large results mean many bundles and many operations downstream, so narrow the search where the module allows it.
mfr field service management19

List Service Requests

SearchIn the docs only

Open and past jobs leave mfr as individual bundles, which gives you raw material for dashboards, alerts or a sync with another planning tool.

When to use it
when you need several requests at once, rather than the single one Get a Service Request returns.
Watch out
it can return zero, one or many requests, and each one feeds the modules after it.
mfr field service management20

List Users

SearchIn the docs only

The people of your mfr account come back one bundle each, which helps when a scenario must address or assign work to the right person.

When to use it
to sync your team roster into a chat tool or to find who should receive a notification.
Watch out
it lists people, it does not choose one; for dispatch, Find Best Technician is the better fit.
mfr field service management21

Make an API Call

ActionIn the docs only

When none of the listed modules does what you need, this one lets you call any endpoint of the mfr API from the scenario, reusing the same connection.

When to use it
to reach a feature of mfr that has no ready module, once you know the endpoint from the mfr API documentation.
Watch out
you write the request yourself, so check the response bundle with Run once before building on it.
mfr field service management22

Remove Tag From Service Request

ActionIn the docs only

A label comes off a service request, so the status your team reads in mfr stays true once the reason for the tag is gone.

When to use it
when a part arrives or a customer pays, and the tag that flagged the wait should disappear.
Watch out
test it on a dummy request first; to add labels, use Add tags to Service Request instead.
mfr field service management23

Update Service Request

ActionIn the docs only

An existing job in mfr gets new information without anyone opening it, which keeps the request aligned with what other tools know.

When to use it
when the customer changes details by email or a partner confirms a delivery that affects the job.
Watch out
make sure the scenario targets the right request, usually found first with Get a Service Request or List Service Requests.
mfr field service management24

Upload Document

ActionIn the docs only

Files reach mfr from other apps, so photos, signed forms or manuals sit next to the job instead of in someone's inbox.

When to use it
when a document lands in a cloud folder or an email and belongs to an ongoing intervention.
Watch out
on the Free plan Make handles files up to 5 MB, so check the size of site photos before you rely on it.
Need help

Need help automating mfr field service management with Make?

A person reads every message.

FAQ

Questions about the mfr field service management Make integration

01Is the mfr field service management Make integration free?
Yes, to start. mfr field service management is a standard app, available from the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits, meaning operations, per month. Your mfr subscription is a separate matter this page does not cover.
02What do you need to connect mfr field service management to Make?
An mfr field service management account and a Make account. The Make documentation lists no specific prerequisite for this app, so the generic steps apply: add an mfr module, click Create a connection, optionally name it, authorize Make on the mfr page or paste the key your account provides, then click Save. That single connection is reused by all 25 modules. Because the documentation is limited, ask your mfr administrator which access method your account uses if the authorization does not go through.
03Does the mfr field service management Watch Events trigger fire instantly?
No. Watch Events is a scheduled trigger: Make checks mfr on the schedule you set for the scenario, and the module shows a clock badge rather than a lightning one. A new scenario runs every 15 minutes by default. On the Free plan that is also the shortest possible interval, while paid plans go down to 1 minute. So a new event in mfr reaches your scenario at the next check, not the second it happens. Choose the schedule based on how quickly your team needs to react.
04What if an mfr field service management module is missing in Make?
Use Make an API Call. This module calls any endpoint of the mfr field service management API from your scenario with the same connection, so it covers what the 25 listed modules leave out. You will need the endpoint and its parameters from the mfr API documentation. Keep in mind that Make describes its own documentation for this app as limited, so test every call with Run once and read the returned bundle before mapping it into later modules.
05Should you use Make or n8n for mfr field service management?
It depends on the tool your team already knows. On Make, you get 25 ready modules for mfr field service management, including Find Best Technician and Generate Report, plus Make an API Call for the rest, all inside a visual editor with Run once testing. The same app often has an n8n node as well, so check its coverage there before deciding. Compare the modules you actually need, how your team builds and tests automations, and which tool already runs your other workflows.
Same platform

Other docs you might need on this stack.

Browse all integrations