Resources · Make integration

Odyssee Field Service Make integrationAutomate Odyssee Field Service with Make.

Can Make keep your field service records moving on their own? The Odyssee Field Service Make integration offers 23 modules for companies, contacts, tasks, articles and invoices. This guide shows ops teams how to connect the account and build a first scenario.

Try the Odyssee Field Service integration on MakeSee the 23 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Odyssee Field Service Make integration do?

The Odyssee Field Service Make integration links your Odyssee account to Make so records can move without copy and paste. You build a scenario, which is the automation itself: a chain of modules, each one a single brick that watches, creates, reads or updates something in Odyssee or in another app.

Follow-up that starts itself. Watch Companies picks up companies in Odyssee, and Create a Task opens a matching task for the technician or office team, so nobody has to remember to do it by hand.

One contact book everywhere. Put a form or a CRM in front, then use Create a Contact, or List Contacts followed by Update a Contact, to keep the same person in sync between tools.

Billing data where finance works. Watch Invoices and Watch Invoice Details hand invoice data to the next module, which can file it in a spreadsheet or an accounting app.

Know the limits before you start. The module list is short on explanations: the official documentation gives names only, so test each module with Run once before you rely on it. What the 23 modules do not cover, Make an API Call can reach with the same connection. If you also weigh n8n, our n8n vs Make comparison lays out the criteria, and the Make pricing page explains what each plan allows. Stuck on an error later? See Make troubleshooting.

Connect

How do you connect Odyssee Field Service to Make?

  1. 01

    Get an API key in Odyssee

    In Odyssee Field Service, open Marketplace from the main menu, click Odyssee API, then the Install link. Odyssee creates a new API user and shows an API key on screen. Copy it right away.

  2. 02

    Open the connection window in Make

    Add any Odyssee Field Service module to your scenario and click Create a connection. A connection is your Odyssee account linked to Make once, then reused by every Odyssee module you add later.

  3. 03

    Name it and paste your credentials

    The Connection name field is optional, but a clear name helps when you run several accounts. Paste the credentials you copied, or follow the instructions Make shows on screen, and save.

First scenario

Your first scenario with Odyssee Field Service

GoalWhen Watch Companies picks up a company in Odyssee Field Service, Make creates a follow-up task with Create a Task.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big + to add the first module. The editor opens with an empty canvas.

  2. 02

    Add Watch Companies

    Search for Odyssee Field Service, pick Watch Companies and select the connection you made earlier, or click Create a connection if this is your first Odyssee module.

  3. 03

    Add Create a Task

    Click the + on the right of the trigger and choose Create a Task. Fill its fields and map data from Watch Companies, such as the company name, into the task text.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, one bundle per item. Check that the task looks right in Odyssee.

  5. 05

    Schedule it and switch it on

    Open the clock on Watch Companies to set the schedule, every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest interval.

Triggers

What can start an Odyssee Field Service scenario?

6 modules start a scenario when something happens in Odyssee Field Service. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Odyssee Field Service as soon as it happens.

Odyssee Field Service1Watch Articles

Watch Articles

triggerIn the docs only

Watch Articles hands your catalog items to the scenario, so the articles stored in Odyssee can feed a price list, a stock sheet or an online shop without retyping.

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
when another tool has to mirror the articles your technicians use in the field.
Watch out
the documentation does not say which articles it returns on each check, so read the bundles from Run once before building on it.
Odyssee Field Service2Watch Companies

Watch Companies

triggerIn the docs only

Watch Companies gives you a starting point each time Odyssee holds a customer company worth acting on: a welcome email, a CRM record or a first task for the team.

How it fires
scheduled. Make checks the app on the scenario's schedule, so the scenario reacts at the next check, not the second a company appears.
When to use it
when a new customer account should kick off a follow-up in Odyssee or elsewhere.
Watch out
test with Run once to see exactly which companies the first check returns.
Odyssee Field Service3Watch Contacts

Watch Contacts

triggerIn the docs only

Watch Contacts lets people stored in Odyssee flow into your mailing tool, your CRM or a shared sheet, so the office and the field see the same names and phone numbers.

How it fires
scheduled. Make checks the app on the scenario's schedule; each contact found becomes one bundle and costs operations downstream.
When to use it
when another app must stay in step with the contacts your team adds in Odyssee.
Watch out
an operation is one run of one module on one bundle, so large batches count up quickly on your plan.
Odyssee Field Service4Watch Invoice Details

Watch Invoice Details

triggerIn the docs only

Watch Invoice Details passes invoice data from Odyssee to the rest of the scenario, which is handy when finance wants more than a total in its own tools.

How it fires
scheduled. Make checks the app on the scenario's schedule and processes what it found at that moment.
When to use it
when a spreadsheet or an accounting app needs invoice content, not just the invoice itself.
Watch out
the documentation lists it next to Watch Invoices without explaining the difference, so compare both with Run once before choosing.
Odyssee Field Service5Watch Invoices

Watch Invoices

triggerIn the docs only

Watch Invoices turns billing activity in Odyssee into the start of a scenario: send the invoice data to accounting, alert a manager or log it in a tracking sheet.

How it fires
scheduled. Make checks the app on the scenario's schedule; on the Free plan, the shortest gap between two checks is 15 minutes.
When to use it
when an invoice issued after an intervention should reach the finance team without a manual export.
Watch out
no description in the documentation, so confirm on a test run what one bundle contains.
Odyssee Field Service6Watch Tasks

Watch Tasks

triggerIn the docs only

Watch Tasks follows the work itself, so the rest of your stack hears about interventions without anyone forwarding an email or updating a board by hand.

How it fires
scheduled. Make checks the app on the scenario's schedule; new scenarios check every 15 minutes by default, and paid plans go down to 1 minute.
When to use it
when a planning board, a chat channel or a client notice depends on task activity in Odyssee.
Watch out
check with Run once which tasks come back before you connect anything customer facing.
Modules

What Odyssee Field Service modules can you use in Make?

Odyssee Field Service gives you 17 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Odyssee Field Service1

Create a Company

ActionIn the docs only

Create a Company adds a customer company to Odyssee from another tool, so a signed deal or a web form becomes an account your team can plan work for.

When to use it
right after a quote is accepted in your CRM or sales app.
Watch out
nothing stops duplicates by itself; run List Companies first if the company may already exist.
Odyssee Field Service2

Create a Contact

ActionIn the docs only

Create a Contact puts a person into Odyssee with the data mapped from the previous module, which saves the office from typing names and phone numbers twice.

When to use it
when a booking form, a CRM lead or an email reply brings in someone the field team will call.
Watch out
check with List Contacts first when the same person can arrive from two sources.
Odyssee Field Service3

Create a Task

ActionIn the docs only

Create a Task opens a piece of work in Odyssee straight from the scenario, so a request received elsewhere lands in the planning without a manual step.

When to use it
when a support ticket, a form or a new company should turn into an intervention to schedule.
Watch out
each run creates a new task, so place a filter before it if the trigger can send the same item twice.
Odyssee Field Service4

Create an Article

ActionIn the docs only

Create an Article adds an item to the Odyssee catalog from another source, which keeps your parts and services list aligned with the tool where products are born.

When to use it
when a supplier file or an e-commerce back office introduces a product your technicians will use.
Watch out
map the fields carefully on a Run once test, because a wrong mapping creates a wrong article in the catalog.
Odyssee Field Service5

Get a Company

ActionIn the docs only

Get a Company fetches one company from Odyssee so later modules can use its details, for example to address an email or fill a document.

When to use it
after a trigger that only brings a reference to the company, when you need the full record.
Watch out
it returns one company; to find several, List Companies is the module to pick.
Odyssee Field Service6

Get a Contact

ActionIn the docs only

Get a Contact reads a single person from Odyssee and makes their details available to the next step, so a reminder or a message goes to the right name.

When to use it
when a task or an invoice points to a contact and you want to reach that person from another app.
Watch out
for a lookup by search rather than a known record, List Contacts fits better.
Odyssee Field Service7

Get a Task

ActionIn the docs only

Get a Task pulls the current state of one task from Odyssee, which lets a scenario decide what to do next based on fresh data rather than an old copy.

When to use it
before sending a status update to a client or a manager about a specific intervention.
Watch out
it reads, it does not change anything; pair it with Update a Task to edit.
Odyssee Field Service8

Get an Article

ActionIn the docs only

Get an Article brings back one catalog item so its details can travel to a quote, an order or a stock sheet further down the scenario.

When to use it
when another module already knows which article is involved and you need its full record.
Watch out
to browse the catalog or match several items, use List Articles instead.
Odyssee Field Service9

List Articles

SearchIn the docs only

List Articles searches the Odyssee catalog and returns zero, one or several articles, each as its own bundle, ready to be copied or compared elsewhere.

When to use it
to sync a whole price list or check whether an article exists before creating it.
Watch out
every bundle it returns runs the next modules once, which counts operations on your plan.
Odyssee Field Service10

List Companies

SearchIn the docs only

List Companies looks through your customer companies in Odyssee and hands back every match, so the scenario can check, update or report on them.

When to use it
as a duplicate check before Create a Company, or to feed a report in a spreadsheet.
Watch out
if nothing matches, it returns no bundle and the rest of that route does not run.
Odyssee Field Service11

List Contacts

SearchIn the docs only

List Contacts finds people in Odyssee and returns each result separately, which is the base of any clean two-way contact sync.

When to use it
to see whether a person already exists before you add or update them from another tool.
Watch out
several results mean several passes through the following modules; add a filter if only one should go on.
Odyssee Field Service12

List Tasks

SearchIn the docs only

List Tasks returns the tasks that match your search, one bundle per task, so you can build a digest, a board or an export from Odyssee data.

When to use it
when a manager wants a summary of interventions sent to a chat channel or a sheet.
Watch out
a long list means many operations downstream; an aggregator can merge the bundles into a single message.
Odyssee Field Service13

Make an API Call

ActionIn the docs only

Make an API Call reaches any endpoint of the Odyssee API with the connection you already set up, which covers whatever the other modules leave out.

When to use it
when you need an object or an action that has no dedicated module, such as invoices beyond the two watch triggers.
Watch out
you write the request yourself, so keep the Odyssee API documentation at hand.
Odyssee Field Service14

Update a Company

ActionIn the docs only

Update a Company changes an existing company in Odyssee with data coming from another app, so an address or a status edited in your CRM is not left stale.

When to use it
when the source of truth for customer accounts lives outside Odyssee.
Watch out
the documentation says nothing on how empty fields are handled, so try it on a test company with Run once first.
Odyssee Field Service15

Update a Contact

ActionIn the docs only

Update a Contact corrects a person already stored in Odyssee, keeping phone numbers and emails right for the technicians who call before a visit.

When to use it
after List Contacts finds the person, when a form or CRM sends new details.
Watch out
the scenario must first know which contact to edit, so place a search or a Get module before it.
Odyssee Field Service16

Update a Task

ActionIn the docs only

Update a Task moves an intervention forward from outside Odyssee, for instance when a client confirms a slot by email or a part arrives in stock.

When to use it
when an event in another tool should change a task that already exists.
Watch out
a change made here cannot be undone by the scenario, so try it on a test task with Run once first.
Odyssee Field Service17

Update an Article

ActionIn the docs only

Update an Article refreshes a catalog item in Odyssee when the product changes somewhere else, so technicians and invoices use the current version.

When to use it
when a supplier file or your shop back office carries the latest article data.
Watch out
run List Articles or Get an Article before it, so the scenario edits the right item and not a similar one.
Need help

Need help automating Odyssee Field Service with Make?

A person reads every message.

FAQ

Questions about Odyssee Field Service and Make

01Is the Odyssee Field Service Make integration free?
Yes, on the Make side. Odyssee Field Service is a standard app, so it works on the Free plan, which allows 2 active scenarios, at least 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) remove the cap on active scenarios, allow a 1 minute interval and count usage in credits each month. You still need your own Odyssee Field Service subscription; Odyssee's pricing page covers that part.
02What do you need to connect Odyssee Field Service to Make?
You need an active Odyssee Field Service account with valid credentials, plus an API key. In Odyssee, open Marketplace in the main menu, click Odyssee API, then the Install link: this creates a new API user and displays the key. In Make, add an Odyssee module, click Create a connection, give it a name if you like, and paste the credentials. That single connection then serves all 23 Odyssee modules in every scenario you build.
03Do Odyssee Field Service triggers in Make fire in real time?
No. All 6 Odyssee Field Service triggers are scheduled: Make checks Odyssee on the scenario's schedule instead of being called the moment something happens. A new scenario checks every 15 minutes by default. The Free plan cannot go below 15 minutes, while paid plans can go down to 1 minute. The integration has no instant trigger, the kind an app calls through a webhook, so plan your scenario around a short delay between the event in Odyssee and the reaction.
04What if a module is missing from the Odyssee Field Service Make integration?
Use Make an API Call. It calls any endpoint of the Odyssee API with the connection you already have, so an object or action without a dedicated module is still within reach. You write the request yourself, which takes a look at the API documentation. Keep in mind that Make's own documentation for this app is AI-generated from the official Odyssee docs and may contain mistakes, so check anything important with a Run once test or with Odyssee directly.
05Should you use Make or n8n for Odyssee Field Service?
It depends on the tool your team already knows. On Make, Odyssee Field Service comes with 23 ready modules, a single API key connection and Make an API Call for the rest, which is enough for most sync scenarios between companies, contacts, tasks and articles. Many apps also have an n8n node, so if n8n is already part of your stack, check whether one exists for Odyssee. Pick the platform where your existing scenarios live, since maintaining one tool is simpler than two.
Same platform

Other docs you might need on this stack.

Browse all integrations