Resources · Make integration

MyCarTracks Make integrationAutomate MyCarTracks with Make.

Your fleet already records every trip, so why copy tracks by hand? The MyCarTracks Make integration gives you 9 modules: 3 triggers, 5 actions and 1 search. This guide is for fleet and ops managers, and it walks you from the connection to a working first scenario.

Try the MyCarTracks integration on MakeSee the 9 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the MyCarTracks Make integration do for you?

The MyCarTracks Make integration links your tracking account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger, an action or a search. Make watches your tracks, vehicles and users, then pushes that data into the other apps you use, without a line of code.

Feed a report with every logged trip. Start with Watch Tracks, add Get a Track to pull the full record, and send it to a spreadsheet or a billing tool. Mileage claims stop living in someone's inbox.

Keep your vehicle list in sync. When a car joins the fleet, Watch Vehicles picks it up and hands it to your asset register or your maintenance app. The same idea works for staff: Watch Users spots new drivers so an onboarding checklist can start.

Tidy tracks in bulk. Search Tracks finds the trips that match your filter, and Update a Track or Delete a Track acts on each one. Test a deletion on one track with Run once before letting it run on many.

What Make does not do here: the three triggers are scheduled, so Make checks MyCarTracks on the scenario's schedule rather than hearing from it the second a trip ends. If a module is missing, Make an API Call reaches the rest of the API. MyCarTracks may also exist as an n8n node; the n8n vs Make page lays out the differences. New to the tool? Our Make review and the Make training are good next reads.

Connect

How do you connect MyCarTracks to Make?

  1. 01

    Generate your API keys in MyCarTracks

    In MyCarTracks, click your profile picture or initials at the top right, open Settings, then API in the left menu. If the Client ID and Client secret boxes are empty, click Generate, then Save, and copy both values.

  2. 02

    Open a connection in Make

    In your scenario, add any MyCarTracks module and click Create a connection. A connection is your MyCarTracks account linked to Make once, then reused by every MyCarTracks module. The Connection name field is optional, but a clear name helps later.

  3. 03

    Paste the credentials and authorize

    Enter the Client ID and Client secret you copied, or follow the on-screen instructions, and confirm. Make can now read your tracks, vehicles and users, and lists them for you in the module fields.

First scenario

Your first scenario with MyCarTracks

GoalWhen a new track appears in MyCarTracks, Make fetches its full details so you can send them wherever you need.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place your first module on the canvas.

  2. 02

    Add Watch Tracks

    Search for MyCarTracks, pick Watch Tracks and choose the connection you made earlier. This trigger will start the scenario whenever it finds new tracks.

  3. 03

    Fill in the trigger

    Complete the fields Make shows you. Once the connection exists, Make lists what it can read in your account, so you pick values instead of typing them.

  4. 04

    Add Get a Track

    Click the + on the right of the trigger, add Get a Track, and map the track coming from Watch Tracks. Each track travels as a bundle, one item passed from module to module.

  5. 05

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, so you can check the track data before going further.

  6. 06

    Schedule and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default. Keep it or change it, then switch the scenario on.

Triggers

What can start a MyCarTracks scenario?

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

MyCarTracks1Watch Tracks

Watch Tracks

triggerIn the docs only

Watch Tracks gives you a scenario that reacts to new trips recorded in MyCarTracks, so the trip data can move on to a spreadsheet, a billing tool or a message without anyone copying it across. Each track arrives as its own bundle.

How it fires
scheduled. Make checks the app on the scenario's schedule, which is every 15 minutes by default on a new scenario, and picks up what appeared since the last check.
When to use it
when the recorded trip itself is the event your process depends on, such as a mileage claim or a client visit log.
MyCarTracks2Watch Users

Watch Users

triggerIn the docs only

With Watch Users, a new person on your MyCarTracks account becomes the starting point of a workflow: you can open an onboarding task, notify a manager or add the driver to your HR tool automatically.

How it fires
scheduled. Make checks the app on the scenario's schedule, so the new user shows up at the next run, not the instant the account is created.
When to use it
when you want other tools to know about drivers without keeping two lists by hand.
Watch out
each run that finds users uses operations, the unit Make counts on your plan.
MyCarTracks3Watch Vehicles

Watch Vehicles

triggerIn the docs only

Watch Vehicles hands you each vehicle added to MyCarTracks as a bundle, ready to land in your asset register, your insurance file or a maintenance planner, so the fleet list stays the same everywhere.

How it fires
scheduled. Make checks the app on the scenario's schedule and passes along the vehicles it did not see before.
When to use it
when a new car or van should trigger paperwork elsewhere, for instance a maintenance record.
Watch out
on the Free plan, scheduled runs are at least 15 minutes apart, so plan for that gap.
Modules

What can Make do in MyCarTracks?

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

MyCarTracks1

Create a Track

ActionIn the docs only

Create a Track adds a new trip record to MyCarTracks from data that lives in another app, so trips logged outside the tracker still end up in one place.

When to use it
when drivers declare journeys in a form or a spreadsheet and you want MyCarTracks to hold the full history.
Watch out
run the scenario with Run once first and check the result in MyCarTracks before switching it on.
MyCarTracks2

Delete a Track

ActionIn the docs only

Delete a Track removes one trip from MyCarTracks, which keeps test entries and duplicates from polluting your reports.

When to use it
after Search Tracks has isolated records you are sure you no longer need, such as trips created during a test.
Watch out
treat every deletion as final. Test on one track with Run once before letting the scenario loop over many.
MyCarTracks3

Get a Track

ActionIn the docs only

Get a Track fetches the complete record of one trip, handy when a previous module only passed you part of it and the next step needs everything.

When to use it
right after Watch Tracks or Search Tracks, before sending trip details to a report or an invoice.
Watch out
it reads one track per bundle, and each bundle it handles counts as one operation.
MyCarTracks4

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of the MyCarTracks API from your scenario, using the same connection as the other modules, which covers what the eight ready-made modules leave out.

When to use it
when none of the listed modules does what you need and the MyCarTracks API documentation shows a way.
Watch out
you build the request yourself here, so keep the API documentation open while you set it up.
MyCarTracks5

Search Tracks

SearchIn the docs only

Search Tracks finds the trips matching your criteria and returns zero, one or several bundles, one per track, which the modules after it then process one by one.

When to use it
when you need a batch of trips, for example to prepare a report or to clean up records.
Watch out
every module placed after it runs once per track found, and each of those runs uses operations on your plan.
MyCarTracks6

Update a Track

ActionIn the docs only

Update a Track changes an existing trip in MyCarTracks, so corrections made elsewhere flow back into the tracker instead of staying in a side file.

When to use it
when a manager validates or corrects a trip in another tool and MyCarTracks should reflect it.
Watch out
pair it with Search Tracks or Get a Track so Make knows exactly which track to modify.
Need help

Need help automating MyCarTracks with Make?

A person reads every message.

FAQ

MyCarTracks and Make: common questions

01Is the MyCarTracks Make integration free?
Yes, MyCarTracks is a standard app, so its modules are available from the Make Free plan. That plan 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) lower the interval to 1 minute and count usage in credits. You still need your own MyCarTracks subscription, which is separate from Make.
02What do you need to connect MyCarTracks to Make?
You need an active MyCarTracks account and API credentials generated in it. Go to Settings, then API, click Generate if the Client ID and Client secret are empty, save, and copy both values. In Make, add a MyCarTracks module, click Create a connection and paste them. If MyCarTracks asks for a callback URI, use the Make address given in the documentation. Naming the connection is optional, and once it exists every MyCarTracks module in your scenarios reuses it.
03Do MyCarTracks triggers in Make work in real time?
No. Watch Tracks, Watch Users and Watch Vehicles are scheduled triggers: Make checks MyCarTracks on the scenario's schedule instead of being notified the second something happens. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Paid plans allow a schedule down to 1 minute when you need data sooner. Keep this in mind for anything urgent, such as alerts: the data arrives at the next run, not the moment the trip ends.
04What if a MyCarTracks module is missing in Make?
It depends on what you need, but the integration includes Make an API Call. That module can call any endpoint of the MyCarTracks API from your scenario, with the same connection as the other modules, so it covers actions the 9 listed modules do not offer. Keep the MyCarTracks API documentation at hand, since you set up the request yourself. The Make documentation for this app also notes its content is AI-generated, so check important details with MyCarTracks.
05Should you use Make or n8n for MyCarTracks?
It depends on your criteria. Make gives you 9 ready-made MyCarTracks modules, including 3 scheduled triggers and Make an API Call for the rest of the API, all built in a visual editor. The same app often exists as an n8n node too. Compare the modules each tool offers for your exact use case, test the one you lean toward on a real trip, and pick the one your team will actually maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations