Resources · Make integration

mWork365 Make integrationAutomate mWork365 with Make.

Can Make take the busywork out of your mWork365 jobs, stock and customers? The mWork365 Make integration offers 78 action modules and no trigger. This guide is for ops teams: link your account, then build a first scenario, the automation you assemble in Make.

Try the mWork365 integration on MakeSee the 78 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the mWork365 Make integration do for you?

The mWork365 Make integration links your mWork365 account to Make, so other apps can create and update job orders, customers, equipment and warehouse stock without copy and paste. Each of the 78 modules is one brick of a scenario, and all of them are actions: something outside mWork365 has to start the run.

Signed deal, ready job. When a deal closes in your CRM, Přidej nebo uprav zákazníka puts the client into mWork365 and Přidej zakázku opens the job, with nobody retyping a thing.

Stock that follows the field. Parts used on a visit leave the warehouse through Odeber materiál ze skladu, and restocking a service van goes through Přesuň materiál mezi sklady.

Visits your customers hear about. Naplánuj výjezd k zakázce podle ID books the trip, then Načti výjezd podle ID hands its details to your messaging tool.

Two things to know first. Module names are in Czech, and Make's documentation for mWork365 is flagged as limited, with no field descriptions. Plan a Run once test (the editor button that runs a scenario one time) for every new module. If you are still choosing a tool, the n8n vs Make comparison sets out the criteria, Make pricing explains the plans, and Make troubleshooting helps when a run fails.

Connect

How do you connect mWork365 to Make?

  1. 01

    Add an mWork365 module

    In a scenario, click the +, search for mWork365 and pick any module, Načti firmu for instance. The module opens with a Create a connection button. A connection is your mWork365 account linked to Make once, then reused by all 78 modules.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later, such as the company or environment it points to. Then approve Make on the mWork365 page that opens, or paste the key mWork365 gives you, whichever the window asks for.

  3. 03

    Save and check

    Click Save. Back in the module, Make can now read what your account exposes and offer it in the fields. If a first Run once returns data, the connection works.

First scenario

Your first mWork365 scenario: turn a request into a job

GoalWhen a request comes in through another app, Make adds or updates the customer in mWork365 and opens a job order for them.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. The first module comes from the app where requests arrive, such as your form or CRM tool, because mWork365 has no trigger.

  2. 02

    Add the customer module

    Click the + on the right, search for mWork365 and choose Přidej nebo uprav zákazníka. Create the connection, then map the client's details coming from the first module.

  3. 03

    Open the job

    Add Přidej zakázku after it and map the customer from the previous module's bundle plus the request text; Run once shows what that bundle holds. Each item passed along is a bundle: here one customer, then one job.

  4. 04

    Test with Run once

    Click Run once with a genuine test request. Read the bundles each module received, then check in mWork365 that exactly one customer and one job appeared.

  5. 05

    Schedule and switch on

    Set the schedule on the first module; a new scenario runs every 15 minutes by default. Switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Modules

What the mWork365 modules do

mWork365 gives you 78 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

mWork3651

Nahraj přílohu

ActionIn the docs only

Puts a file into mWork365 straight from your scenario, so a site photo, a signed report or a PDF lands where your team works. The Czech name means “upload attachment”.

When to use it
a technician's photos arrive through another app and belong with the job in mWork365.
Watch out
on the Free plan Make moves files of 5 MB at most, so a heavy scan may need a paid plan.
mWork3652

Naplánuj výjezd k zakázce podle ID

ActionIn the docs only

Books a field visit against an existing job order without opening mWork365. The name reads “schedule a visit for a job order by ID”, the ID being the number mWork365 itself gives the job.

When to use it
a customer confirms a slot in your booking tool and the technician's trip should appear on the job.
Watch out
you need that mWork365 ID in hand, usually mapped from a reading module placed earlier.
mWork3653

Naplánuj výjezd k zakázce podle externího ID

ActionIn the docs only

Schedules the same visit, but finds the job through its external ID, the reference your own ERP or CRM stores. Your other tool never needs to learn mWork365's numbers.

When to use it
the order number from your sales tool is the only key you have.
Watch out
check in mWork365 that the external ID is actually filled on the job, then test with Run once.
mWork3654

Nastav množství materiálu na skladě

ActionIn the docs only

Aligns stock in mWork365 with a count made elsewhere. “Nastav” means “set”, so going by its name the module writes a quantity rather than adding or removing some.

When to use it
after an inventory count kept in a spreadsheet, push the counted figure.
Watch out
for a delivery that adds to what is already there, Přidej materiál na sklad fits better.
mWork3655

Nastav množství materiálu na skladě podle externího ID

ActionIn the docs only

Corrects a stock figure for a material identified by the code in your own catalog instead of the mWork365 ID. Handy when a webshop or ERP owns the product codes.

When to use it
your inventory export comes out of the ERP with its own references.
Watch out
that external code must exist on the material in mWork365 before the first run.
mWork3656

Načti firmu

ActionIn the docs only

Brings a company record from mWork365 into the scenario, so later modules reuse its details instead of hardcoded text. The name means “load company”, and unlike most readers here it carries no “by ID”.

When to use it
a quote or email built later in the flow should show the company name as mWork365 stores it.
Watch out
the doc does not describe what it returns, so run it once and read the bundle.
mWork3657

Načti formulář podle ID

ActionIn the docs only

Pulls one completed form out of mWork365 by its ID, ready to travel to another tool. “Formulář” is simply “form”.

When to use it
a visit report filled in the field should become a PDF, a chat message or a spreadsheet row.
Watch out
when a single answer is all you need, Získej hodnotu z formuláře, listed further down, may be the lighter choice.
mWork3658

Načti materiál podle ID

ActionIn the docs only

Hands you one material record, looked up by its mWork365 ID and ready to map into the next module. “Načti materiál” means “load material”.

When to use it
before sending an order to a supplier, fetch the details mWork365 keeps on that part.
Watch out
it reads a single item; with only a name to go on, reach for Vyhledat materiál, the search module further down.
mWork3659

Načti materiál podle externího ID

ActionIn the docs only

Gives you the same material record, reached with the external ID your product catalog already uses. That saves a lookup step whenever codes are born outside mWork365.

When to use it
an order line from your online store carries the product code and you need the stock data behind it.
Watch out
the external ID has to be stored on the material in mWork365 beforehand.
mWork36510

Načti sklad podle ID

ActionIn the docs only

Returns one warehouse (sklad, in Czech) found by its internal ID, so its record can feed a report or the next step of a stock move.

When to use it
before adding or moving material, confirm which warehouse you are about to touch.
Watch out
every read costs an operation, so skip it when an earlier module already gave you the same data.
mWork36511

Načti sklad podle externího ID

ActionIn the docs only

Finds a warehouse through the code your other system gives it, then passes the record down the scenario. Choose it over the ID version when warehouses were set up from an ERP with its own numbering.

When to use it
a transfer request arrives carrying the ERP's warehouse code.
Watch out
two tools means two numbering schemes; dropping an mWork365 ID into this field is the classic slip.
mWork36512

Načti výjezd podle ID

ActionIn the docs only

Puts a field visit's record in your hands, výjezd meaning a trip out to a site, fetched by its mWork365 ID. The next module can then notify the customer or log the visit.

When to use it
right after scheduling a visit, reload it to send a confirmation with its details.
Watch out
the doc lists no returned fields, so inspect the bundle after Run once before mapping.
mWork36513

Načti výjezd podle externího ID

ActionIn the docs only

Lets your planning tool look up a visit in mWork365 with its own reference, the external ID, with no need to store mWork365 numbers on its side.

When to use it
a dispatcher moves a slot in the planning tool and the scenario must load the matching visit before acting.
Watch out
this module only reads; to call a visit off, Zruš výjezd podle externího ID is the one that acts.
mWork36514

Načti zakázku podle ID

ActionIn the docs only

Retrieves a full job order from mWork365 by its ID. Zakázka is Czech for an order or contract job, the unit most modules of this app revolve around.

When to use it
once work is finished on site, load the job to build the invoice in your accounting app.
Watch out
a module placed after this read runs once per bundle it receives, and each run counts as an operation.
mWork36515

Načti zakázku podle externího ID

ActionIn the docs only

Reaches a job order through its external ID, the number your CRM or ERP gave it when the deal was signed. Your scenario can stay keyed on that one number from start to finish.

When to use it
a status change in the CRM needs the matching job from mWork365.
Watch out
a job created by hand in mWork365 may have no external ID at all, and this route then misses it.
mWork36516

Načti zařízení podle ID

ActionIn the docs only

Delivers one equipment record, zařízení meaning a device or installed unit, straight from mWork365 by its ID. Useful whenever a visit or report needs the machine's details.

When to use it
a maintenance ticket names the device ID and the technician's brief should show its record.
Watch out
keep mWork365 IDs and other tools' IDs apart in your mapping; the external-ID variant exists for the second kind.
mWork36517

Načti zařízení podle externího ID

ActionIn the docs only

Pulls the same device record using a code your own system keeps, an asset number for example, stored as the external ID in mWork365. No lookup table between tools.

When to use it
an alert from a monitoring tool quotes that code and you want the matching device.
Watch out
if two devices shared one external ID the result would be unclear, so keep those codes unique.
mWork36518

Načti zákazníka podle ID

ActionIn the docs only

Gives you a customer's record from mWork365, looked up by its mWork365 ID, so any later module can reuse its details.

When to use it
before emailing a visit summary, load the customer to address the message to the right person.
Watch out
to find a customer by name rather than by ID, Vyhledat zákazníky is the search module meant for it.
mWork36519

Načti zákazníka podle externího ID

ActionIn the docs only

Finds a customer through the external ID, such as the account number in your CRM, and passes the record on. Two tools can then talk about the same client without a shared numbering.

When to use it
a CRM deal moves to won and the job needs the client's mWork365 record.
Watch out
customers created directly in mWork365 need that external ID filled in first.
mWork36520

Odeber materiál ze skladu

ActionIn the docs only

Takes material out of a warehouse in mWork365, so the stock drops when parts leave. “Odeber” means “remove”.

When to use it
a technician reports the parts used on a job and the warehouse count should follow.
Watch out
this removes an amount; if all you know is the new total after a count, Nastav množství materiálu na skladě is the better fit.
mWork36521

Odeber materiál ze skladu podle externího ID

ActionIn the docs only

Records the same stock withdrawal while naming the material with your own catalog code rather than mWork365's ID. The webshop or ERP stays the single home of product codes.

When to use it
an order shipped from your online store should pull the item out of the matching warehouse.
Watch out
a scenario that runs twice on one order withdraws twice, so test on a dummy order.
mWork36522

Přesuň materiál mezi sklady

ActionIn the docs only

Moves material from one warehouse to another inside mWork365 in a single step. “Přesuň” means “move”, and one module spares you pairing a withdrawal with an addition.

When to use it
a service van is restocked from the central depot and both counts must change together.
Watch out
after a first Run once, check which warehouse went down; a swapped source and target is easy to miss.
mWork36523

Přesuň materiál mezi sklady podle externího ID

ActionIn the docs only

Runs the same transfer between warehouses, with everything identified through external IDs from your own system. Pick it when warehouse or material codes originate in an ERP.

When to use it
the ERP books a transfer between two sites and mWork365 should mirror it.
Watch out
mixing an mWork365 ID and an external one in the same run is an easy mistake to make.
mWork36524

Přidej adresu k zákazníkovi podle ID

ActionIn the docs only

Attaches a new address to an existing customer in mWork365, so a second site or a delivery point sits on the right record.

When to use it
a client opens a new branch and your CRM captures the address first.
Watch out
the customer is picked by its mWork365 ID here; if you only hold your CRM's reference, the external-ID variant just below does the job.
mWork36525

Přidej adresu k zákazníkovi podle externího ID

ActionIn the docs only

Adds that extra address to the customer your CRM already knows, found through its external ID. No need to fetch the mWork365 ID first, which saves an operation.

When to use it
a sales rep adds a site in the CRM and the field team needs it in mWork365.
Watch out
to change an address already there, use the Uprav adresu modules instead of adding a duplicate.
mWork36526

Přidej definici materiálu

ActionIn the docs only

Creates a new material type in mWork365, the catalog entry, before any stock of it exists. “Definice” means “definition”.

When to use it
a new product appears in a supplier's price list and should become orderable in mWork365.
Watch out
this only defines the item; placing quantities in a warehouse is the job of Přidej materiál na sklad afterwards.
mWork36527

Přidej kontaktní osobu k zákazníkovi podle ID

ActionIn the docs only

Adds a named contact person to a customer in mWork365, so technicians know whom to call on site.

When to use it
a form on your website collects a new site manager's details for an existing client.
Watch out
the customer is targeted by its mWork365 ID; put a reading module first if the scenario starts in another tool.
mWork36528

Přidej kontaktní osobu k zákazníkovi podle externího ID

ActionIn the docs only

Links a new contact person to the customer your CRM identifies by its external ID, keeping both tools in step without extra lookups.

When to use it
someone is added to an account in the CRM and the field team should see the same person.
Watch out
editing that person later goes through Uprav kontaktní osobu, not through a second add.
mWork36529

Přidej materiál na sklad

ActionIn the docs only

Raises the stock of a material in a chosen warehouse, the everyday move when goods arrive.

When to use it
a supplier's delivery note is logged in another tool and the parts should show up in mWork365.
Watch out
it adds to what is there; to overwrite with a counted total, Nastav množství materiálu na skladě is the right pick.
mWork36530

Přidej materiál na sklad podle externího ID

ActionIn the docs only

Books incoming stock against a material named by your own product code, the external ID. Good when purchasing lives in an ERP and mWork365 follows.

When to use it
a purchase order is received in the ERP and the warehouse count needs to rise.
Watch out
if the material does not exist yet in mWork365, create it with Přidej definici materiálu first.
mWork36531

Přidej nebo uprav zakázku

ActionIn the docs only

Creates a job order, or updates it when it already exists, in one module. That spares you a search followed by a branch in the scenario.

When to use it
the same CRM deal may be sent to mWork365 several times as it evolves.
Watch out
the doc does not say how the app decides between creating and updating, so compare the results of two Run once tests.
mWork36532

Přidej nebo uprav zákazníka

ActionIn the docs only

Keeps customer records in mWork365 current without doubles: one module that adds the client or edits the existing one. “Nebo uprav” means “or edit”.

When to use it
every change on an account in your CRM should reach mWork365.
Watch out
click Run once twice with the same customer and check you still see a single record.
mWork36533

Přidej sklad

ActionIn the docs only

Adds a new warehouse to mWork365, whether your team models that as a building, a storeroom or a service van.

When to use it
a new depot is opened in your ERP and should exist before any stock moves there.
Watch out
create it before any Přidej materiál na sklad module runs, or that later step has no warehouse to fill.
mWork36534

Přidej zakázku

ActionIn the docs only

Opens a brand-new job order in mWork365 from data arriving elsewhere, so nobody retypes a request.

When to use it
a quote is accepted in your sales tool and the work should be scheduled.
Watch out
its name only says “add”; if the same deal can come back, Přidej nebo uprav zakázku keeps you clear of duplicate jobs.
mWork36535

Přidej zařízení k zákazníkovi podle ID

ActionIn the docs only

Registers a piece of equipment under an existing customer, so the machine's history starts in the right place.

When to use it
an installation is signed off and the unit should be tracked for future service visits.
Watch out
the owner is chosen by mWork365 ID; bring it in from an earlier read such as Načti zákazníka podle ID.
mWork36536

Přidej zařízení k zákazníkovi podle externího ID

ActionIn the docs only

Files equipment under the customer your own system knows by its external ID, letting an installation form or a sales tool feed mWork365 directly.

When to use it
an equipment sale closes in the CRM and the unit should appear on the client's record.
Watch out
a device added twice becomes two records, so keep one sale from running the scenario twice.
mWork36537

Přidej zákazníka

ActionIn the docs only

Creates a new customer in mWork365 from a lead, a form or a deal signed in another tool.

When to use it
a first order arrives from a client mWork365 has never seen.
Watch out
if the client might already be there, Přidej nebo uprav zákazníka guards against duplicates better than this plain add, which its name limits to creating.
mWork36538

Sleduj události

ActionIn the docs only

Gives your scenario a way into what mWork365 calls events: the name means “watch events”. Yet it is listed here among the actions, not the triggers, so it will not start a scenario on its own.

When to use it
only once a Run once test has shown what its bundles contain, since the doc says nothing about it.
Watch out
to start a flow, rely on another app's trigger or on the schedule of the first module.
mWork36539

Smaž adresu zákazníka podle ID

ActionIn the docs only

Removes an address from a customer in mWork365, keeping the list of sites clean when one closes.

When to use it
a site is marked closed in your CRM and technicians should stop seeing it.
Watch out
Make has no undo for this; once the scenario runs the address is gone, so try it first on a test customer.
mWork36540

Smaž adresu zákazníka podle externího ID

ActionIn the docs only

Deletes a customer address located through your own system's reference, the external ID. Sensible when the CRM decides which sites exist.

When to use it
an address is dropped from an account in the CRM and mWork365 should follow suit.
Watch out
run your tests on a dummy customer; a wrong mapping here wipes real data that Make cannot bring back.
mWork36541

Smaž definici materiálu podle ID

ActionIn the docs only

Removes a material definition, the catalog entry that describes one item, from mWork365 once you hand it the record's mWork365 ID. Your catalog stops offering items nobody buys anymore.

When to use it
a product line is dropped in your purchasing tool and its catalog card should go as well.
Watch out
Make cannot undo a delete, so try it with Run once on a test item first.
mWork36542

Smaž definici materiálu podle externího ID

ActionIn the docs only

Does the same catalog clean-up, but points at the material definition through its external ID, the reference your other system keeps. No lookup module is needed when that system already has the code.

When to use it
a spreadsheet or ERP is your master item list and deletes on its side first.
Watch out
pick it only when that external reference is filled in mWork365; otherwise the ID version is the safer bet.
mWork36543

Smaž kontaktní osobu podle ID

ActionIn the docs only

Takes one contact person off a customer in mWork365, located by its mWork365 ID. The customer record stays; only that person leaves the list your team calls.

When to use it
someone leaves the client company and your CRM marks them as gone.
Watch out
the delete is final. If only a detail changed, Uprav kontaktní osobu podle ID keeps the person and fixes the record.
mWork36544

Smaž kontaktní osobu podle externího ID

ActionIn the docs only

Deletes a customer's contact person, found through the external ID that comes from your own tools. It fits contacts that were first pushed into mWork365 from a CRM carrying its own reference.

When to use it
your CRM archives a contact and mWork365 should follow in the same run.
Watch out
Make counts one operation, one module run on one bundle, per contact removed, so a big clean-up weighs on your plan.
mWork36545

Smaž přílohu podle ID

ActionIn the docs only

Gets rid of an attachment stored in mWork365, using its ID. It is the counterpart of Nahraj přílohu, the upload module, and keeps records free of files that no longer belong there.

When to use it
a file was attached by mistake, or a newer version replaced it.
Watch out
attachments have no external ID variant, so the scenario needs the attachment's mWork365 ID from an earlier module.
mWork36546

Smaž sklad podle ID

ActionIn the docs only

Removes a warehouse from mWork365 by its ID, so a closed storage location no longer shows up when stock is moved or counted.

When to use it
a depot shuts down and your team should stop picking it from the list.
Watch out
read the warehouse first with Načti sklad podle ID and check the bundle, since a deleted warehouse does not come back.
mWork36547

Smaž sklad podle externího ID

ActionIn the docs only

Closes a warehouse on the mWork365 side using the external ID your inventory or accounting tool gives it. Both systems end up with the same list of locations.

When to use it
warehouses are created and retired in another tool, and mWork365 only mirrors that list.
Watch out
click Run once, the editor button that runs the scenario a single time, and read the result before you switch the scenario on.
mWork36548

Smaž zakázku podle ID

ActionIn the docs only

Erases a job, a zakázka in mWork365, when you know its ID. The record disappears for good instead of being closed or cancelled.

When to use it
a test run of your scenario created a duplicate job that should never have existed.
Watch out
for a job that was real but will not happen, the app has Zruš zakázku podle ID; keep delete for records created by mistake.
mWork36549

Smaž zakázku podle externího ID

ActionIn the docs only

Deletes a job through its external ID, for example the order number from your shop or quoting tool. The scenario skips the step of finding the mWork365 ID first.

When to use it
an order is removed upstream as a test or spam and must vanish from the field side too.
Watch out
map the external ID with care in the field; a wrong value from the previous module deletes the wrong job.
mWork36550

Smaž zařízení podle ID

ActionIn the docs only

Deletes a piece of equipment, a zařízení, found by its mWork365 ID. The customer's equipment list becomes accurate again and technicians stop seeing a machine that is gone.

When to use it
a customer scraps a device and tells your office.
Watch out
if the device is still there and only a detail changed, Uprav zařízení podle ID keeps the record instead of wiping it.
mWork36551

Smaž zařízení podle externího ID

ActionIn the docs only

Same equipment removal, keyed on the external ID so an asset register kept in another tool can drive it. Nothing has to be retyped in mWork365.

When to use it
your asset list marks a device as retired and mWork365 should match.
Watch out
the edit twin of this module is spelled Uprav zařízení podle ExternalID, not externího ID, so search both spellings in the module list.
mWork36552

Smaž zákazníka podle ID

ActionIn the docs only

Deletes a customer from mWork365 with its ID. Keep it for genuine mistakes: duplicates, test accounts, records an early version of your scenario created twice.

When to use it
a data import left duplicate customers behind and you clean them up.
Watch out
this is the heaviest delete in the app; run it once on a single customer and read the output before it touches a list.
mWork36553

Smaž zákazníka podle externího ID

ActionIn the docs only

Removes a customer through the external ID, meaning the customer number your billing tool or CRM already uses. The deletion follows the source system with no extra lookup.

When to use it
a customer is removed from the CRM and should not linger in the field-service app.
Watch out
each bundle that reaches this module deletes one customer, so check how many bundles the previous module sends before activating.
mWork36554

Univerzální Požadavek

ActionIn the docs only

The name translates as universal request. The doc gives no description, so treat it as the open module to try when none of the named mWork365 modules covers what you need.

When to use it
you need something from mWork365 that the load, add, edit and delete modules leave out.
Watch out
Make says its mWork365 documentation is limited; test with Run once and read the returned bundle before you build on it.
mWork36555

Uprav adresu podle externího ID

ActionIn the docs only

Changes an address in mWork365, found by its external ID, so the next visit goes to the right door without anyone editing the record by hand.

When to use it
a customer moves and your CRM gets the new address first.
Watch out
the name drops the word zákazníka that its ID twin carries, so type uprav adresu in the module search to see both side by side.
mWork36556

Uprav adresu zákazníka podle ID

ActionIn the docs only

Edits a customer's address when your scenario holds the mWork365 ID of that address. The corrected version replaces the old one on the record.

When to use it
an address typed wrong in a web form gets fixed and the fix must reach mWork365.
Watch out
to add a second site rather than overwrite the first, the right module is Přidej adresu k zákazníkovi podle ID.
mWork36557

Uprav definici materiálu podle ID

ActionIn the docs only

Updates a material definition, the catalog card for an item, by its ID. Your technicians keep picking the right item with the right wording.

When to use it
a supplier renames a product and the catalog should say the same thing.
Watch out
the editable fields are not documented; once the connection exists, open the module in the editor to see which ones Make offers.
mWork36558

Uprav definici materiálu podle externího ID

ActionIn the docs only

Edits a catalog item through the external ID, the code your purchasing tool uses. Master data can live elsewhere and mWork365 simply follows.

When to use it
item details change in your ERP and you want one scenario to push them over.
Watch out
this module only edits; if the item may not exist yet in mWork365, Přidej definici materiálu is the one that creates it.
mWork36559

Uprav kontaktní osobu podle ID

ActionIn the docs only

Brings a customer's contact person up to date, located by its mWork365 ID. The office calls the right person with current details instead of an old record.

When to use it
a contact's details change in your inbox or CRM and mWork365 lags behind.
Watch out
the ID here is the contact's, not the customer's; mapping the customer ID into this field targets nothing useful.
mWork36560

Uprav kontaktní osobu podle externího ID

ActionIn the docs only

Updates a contact person found by the external ID from your CRM or address book. Two tools, one version of each person.

When to use it
your sales team edits contacts in the CRM, and the field team works from mWork365.
Watch out
every edited contact costs one operation; a scenario that sends the whole contact list on each run spends far more than the handful that changed.
mWork36561

Uprav sklad podle ID

ActionIn the docs only

Changes the details of a warehouse, found by its mWork365 ID. The location keeps its stock; only its description in the app moves.

When to use it
a depot gets a new name or new details and the list should reflect it.
Watch out
to change quantities, this is the wrong module; stock levels go through Nastav množství materiálu na skladě.
mWork36562

Uprav sklad podle externího ID

ActionIn the docs only

Edits a warehouse through the external ID that your inventory system assigned it, so locations stay aligned without a manual pass in mWork365.

When to use it
warehouse data is maintained in your accounting or stock tool and mWork365 mirrors it.
Watch out
read one warehouse with Načti sklad podle externího ID and click Run once to confirm the reference matches before editing.
mWork36563

Uprav zakázku podle ID

ActionIn the docs only

Updates a job in mWork365 once you have its ID. The job stays the same record while its details catch up with what the customer asked.

When to use it
a customer changes the scope of a job by email and your office logs it.
Watch out
when you are unsure whether the job exists yet, Přidej nebo uprav zakázku adds or edits in one module.
mWork36564

Uprav zakázku podle externího ID

ActionIn the docs only

Edits a job found by the external ID, typically the order number from the system where the sale happened. The field team sees the change without a phone call.

When to use it
an order is amended in your shop or quoting tool after the job was created.
Watch out
a job that was never created with that external reference cannot be matched this way; test with Run once on a real order.
mWork36565

Uprav zařízení podle ExternalID

ActionIn the docs only

Updates a piece of equipment through its external ID, the reference your asset tool keeps. Note the spelling: Make lists this one as ExternalID, unlike every other external ID module of the app.

When to use it
a device gets serviced or relocated and your asset register records it first.
Watch out
searching for externího in the module list will not find it; search for zařízení instead.
mWork36566

Uprav zařízení podle ID

ActionIn the docs only

Edits a device record found by its mWork365 ID, so what technicians read on site matches what is really installed at the customer's.

When to use it
a technician reports a change in a form, and the equipment card should follow.
Watch out
fetch the device first with Načti zařízení podle ID and check the bundle, so you edit the right machine and not its neighbor.
mWork36567

Uprav zákazníka podle ID

ActionIn the docs only

Changes a customer's record in mWork365, located by its ID. Company details stay consistent for every job, visit and invoice built on that customer.

When to use it
a customer sends updated company details and your office wants them in one place.
Watch out
it edits only; for data that might be new, Přidej nebo uprav zákazníka creates the customer when it is missing.
mWork36568

Uprav zákazníka podle externího ID

ActionIn the docs only

Updates a customer through the external ID your CRM or billing tool uses, so the customer number becomes the bridge between the two apps.

When to use it
the CRM is where account managers edit customers, and mWork365 should never drift from it.
Watch out
map exactly the same reference you used when the customer was added, or the module finds no match.
mWork36569

Vyhledat materiál

ActionIn the docs only

The name means search materials: it looks through your mWork365 items and hands the results to the next module, so you can work with an item without knowing its ID.

When to use it
an incoming request names a part and you need its record before booking stock.
Watch out
Make lists it as an action; click Run once and count the bundles it returns before you plug an edit or delete behind it.
mWork36570

Vyhledat výjezdy

ActionIn the docs only

Searches field visits, the výjezdy your technicians go out on, and passes what it finds along the scenario. A good starting point to report on visits in another tool.

When to use it
you want visits copied into a planning sheet or a team chat.
Watch out
the result can contain several visits; check with Run once how many bundles come out, as each later module runs once per bundle.
mWork36571

Vyhledat zakázky

ActionIn the docs only

Finds jobs in mWork365 so the rest of the scenario can read, edit or report on them. It is how you reach jobs when you do not hold an ID.

When to use it
an email mentions a job and you need its record to update the status.
Watch out
the module's search options are not documented; open it in the editor after connecting to see what Make lets you filter on.
mWork36572

Vyhledat zařízení

ActionIn the docs only

Looks up equipment across your customers and returns it to the scenario, handy to get a device's ID before editing or deleting it.

When to use it
a service request quotes a device and you want its record without searching by hand.
Watch out
several devices may match; read the bundles after Run once and decide whether the next module should act on all of them.
mWork36573

Vyhledat zákazníky

ActionIn the docs only

Searches your customers in mWork365, which lets a scenario recognize an existing client before it creates a new one.

When to use it
a web form arrives and you want to check whether that company is already a customer.
Watch out
if the search finds nobody, the next module gets no bundle; for add-or-update in a single step, Přidej nebo uprav zákazníka is simpler.
mWork36574

Zruš výjezd podle ID

ActionIn the docs only

Cancels a scheduled field visit, identified by its mWork365 ID. The technician's plan frees up without anyone phoning the office.

When to use it
a customer cancels an appointment through your booking tool.
Watch out
cancel is not delete; it fits visits that were really planned, and Naplánuj výjezd k zakázce podle ID books a new one if the customer reschedules.
mWork36575

Zruš výjezd podle externího ID

ActionIn the docs only

Calls off a visit through its external ID, the reference from the calendar or booking app where it was set up. mWork365 and that tool stay in step.

When to use it
visits are booked outside mWork365 and cancellations happen there too.
Watch out
test on a dummy visit with Run once; a cancelled real visit means a technician missing from a customer's site.
mWork36576

Zruš zakázku podle ID

ActionIn the docs only

Cancels a job by its ID, so it no longer counts as work to do. The name says cancel, not delete, which suits jobs that really existed.

When to use it
a customer withdraws an order after the job was created.
Watch out
pick Smaž zakázku podle ID only for jobs that should never have existed; cancel is the gentler choice for everything else.
mWork36577

Zruš zakázku podle externího ID

ActionIn the docs only

Cancels a job found by its external ID, such as an order number from your online shop, so a cancellation made there reaches the field team.

When to use it
orders are cancelled in your sales tool and mWork365 should drop the matching job.
Watch out
the job must carry that same external reference; check one job with Načti zakázku podle externího ID before activating.
mWork36578

Získej hodnotu z formuláře

ActionIn the docs only

Pulls a value out of an mWork365 form, for instance an answer a technician filled in on site, and makes it available to the next modules.

When to use it
one answer from a completed form should update a spreadsheet, a job or a message to the customer.
Watch out
load the form first with Načti formulář podle ID so you know which values exist before mapping one.
Need help

Need help automating mWork365 with Make?

A person reads every message.

FAQ

mWork365 and Make: frequent questions

01Is the mWork365 Make integration free?
Yes. mWork365 is a standard app in Make, so its modules work from the Free plan onward. That plan allows 2 active scenarios, at least 15 minutes between 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) bring the interval down to 1 minute, lift the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits, meaning operations, each month. Your mWork365 subscription is a separate matter that this page does not cover.
02What do you need to connect mWork365 to Make?
An mWork365 account and a Make account. Make's documentation lists no specific prerequisite for mWork365 and gives no official connection steps, so the generic flow applies: add any mWork365 module, click Create a connection, name it if you wish, authorize Make on the mWork365 page or paste the key the app provides, then click Save. Since the documentation is flagged as limited, keep your mWork365 administrator within reach in case the window asks for a key. One connection then serves every mWork365 module in your scenarios.
03Does mWork365 start Make scenarios in real time?
No. None of the 78 mWork365 modules is a trigger, scheduled or instant, so mWork365 cannot start a scenario by itself. There are two ways around that. Open the scenario with a trigger from another app, such as the tool where requests or orders arrive, and let the mWork365 modules act after it. Or rely on scheduling: a new scenario runs every 15 minutes by default, and paid plans go down to 1 minute. Note that Sleduj události, despite a name meaning watch events, is listed as an action.
04What if an mWork365 module is missing in Make?
It depends on what is missing. mWork365 has no Make an API Call module, so you cannot send a custom request to its API from a generic Make module. The list does include Univerzální Požadavek, Czech for universal request, but the documentation does not describe it, so test it with Run once before relying on it. Otherwise, see whether another app in your stack can hold that step, or ask the team to look at your case. The documentation for mWork365 is flagged as limited, which also rules out promises about hidden options.
05Should you use Make or n8n for mWork365?
It depends on your criteria, not on a universal winner. On Make, mWork365 comes with 78 action modules, available from the Free plan, and no trigger. Before leaning toward n8n, check whether it offers a node for mWork365 at all, then compare the actions it covers with the list on this page. After that, weigh where your other apps already run and who in your team will maintain the scenarios. The n8n vs Make comparison linked higher up lays these criteria out side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations