Resources · Make integration

Dr.Tracker Make integrationAutomate Dr.Tracker with Make.

Every lead that lands somewhere else can reach Dr.Tracker on its own. The Dr.Tracker Make integration gives you 2 action modules and no trigger. This page shows who it suits, how to connect your account and how to build your first scenario step by step.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Dr.Tracker Make integration do for you?

The Dr.Tracker Make integration lets a Make scenario (the automation you build, a chain of steps) write into your Dr.Tracker account without code. Each step is a module, and Dr.Tracker offers two of them: one adds a lead, the other calls any endpoint of the Dr.Tracker API with your saved connection.

No more retyping contacts. A sales rep who collects prospects through a web form can pass each answer to Add a new lead, so the lead shows up in Dr.Tracker the moment the scenario runs.

Covering what the listed modules skip. When you need something other than a new lead, Make an API Call reaches the rest of the Dr.Tracker API with the same connection. It asks more of you, since you have to know the endpoint you are calling.

Starting from another tool. Dr.Tracker has no trigger in Make, so the event that starts the scenario always comes from elsewhere: a form app, a spreadsheet row, or a plain schedule set in Make. The Make training walks through that pattern if it is new to you.

Know the limits before you start. Make itself says its documentation for Dr.Tracker is limited, because little public information exists about the app, so field names and error messages are something you discover in the editor. If you are still weighing tools, the n8n vs Make comparison lays out the criteria, and Make troubleshooting helps when a run fails.

Connect

How do you connect Dr.Tracker to Make?

  1. 01

    Open the connection window

    Add a Dr.Tracker module to your scenario, then click Create a connection. A connection is your Dr.Tracker account linked to Make once and reused by both modules afterward.

  2. 02

    Name it if you like

    Giving the connection a name is optional. It helps when several people or several Dr.Tracker accounts share the same Make organization, because the list of connections stays readable.

  3. 03

    Authorize Make and save

    Depending on what Dr.Tracker asks, either approve Make on the app's own page or paste the key that Dr.Tracker gives you. Then click Save and the module is ready to fill in.

First scenario

Your first scenario with Dr.Tracker

GoalWhen a new contact comes in from another app, Make adds it to Dr.Tracker as a lead.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. It belongs to the app where your contacts first arrive, such as a form tool.

  2. 02

    Set the starting module

    Pick the module of that other app that returns new contacts and connect its account. Each contact it hands over is a bundle, one item passing from a module to the next one.

  3. 03

    Add Dr.Tracker

    Click the + on the right, search for Dr.Tracker and choose Add a new lead. Create the connection, then map the name, email or other details from the first module into its fields.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Read the bundles each module received, then check in Dr.Tracker that the lead appeared.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set how often it runs (every 15 minutes by default, 15 minutes at the shortest on the Free plan), then switch the scenario on.

Modules

What the Dr.Tracker modules do

Dr.Tracker gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Dr.Tracker1

Add a new lead

ActionIn the docs only

This module creates a lead in Dr.Tracker from data that another module passed along, so a prospect captured elsewhere lands in your pipeline without anyone copying it by hand.

When to use it
right after a form, a chat or a spreadsheet hands you a new prospect and you want Dr.Tracker to hold the record.
Watch out
the documentation lists no fields, so run it once and check which ones Dr.Tracker really fills before switching the scenario on.
Dr.Tracker2

Make an API Call

ActionIn the docs only

With this one you reach any endpoint of the Dr.Tracker API while reusing the connection you already created, which opens up everything the lead module does not cover.

When to use it
you need an operation other than adding a lead and you know which endpoint handles it.
Watch out
you write the request yourself and Make documents little about this app, so read the answer in Run once before relying on it.
Need help

Need help automating Dr.Tracker with Make?

A person reads every message.

FAQ

Questions about the Dr.Tracker Make integration

01Is the Dr.Tracker Make integration free?
Yes, Dr.Tracker is a standard app, so it works on the Free plan of Make. That plan gives you 2 active scenarios, runs spaced 15 minutes apart at the shortest, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Every plan counts usage in operations, one module running on one bundle. Your Dr.Tracker subscription is a separate matter.
02What do you need to connect Dr.Tracker to Make?
You need a Dr.Tracker account and a Make account. The documentation lists no other prerequisite and gives no official steps, so the generic flow applies: add a Dr.Tracker module, click Create a connection, optionally name it, then authorize Make on the app's page or paste the key Dr.Tracker provides, and click Save. Make says its documentation for this app is limited, so if Dr.Tracker asks for a credential you cannot find, its own support is the place to ask. The connection is then shared by both modules.
03Does the Dr.Tracker Make integration have a real-time trigger?
No, Dr.Tracker has no trigger module in Make, neither scheduled nor instant. The scenario has to start elsewhere. You can open it with a trigger from another app, like a form tool that reports new entries, and then add Add a new lead. Or you can simply put a schedule on the first module, every 15 minutes by default. Whether it reacts instantly depends on that first module, not on Dr.Tracker.
04What if the Dr.Tracker module you need is missing in Make?
It depends on the action, but there is a way out. Dr.Tracker only lists Add a new lead as a ready-made module, and Make an API Call covers the rest: it reaches any endpoint of the Dr.Tracker API through the connection you already set up. You have to know the endpoint and the shape of the request, and Make's documentation for this app is limited, so ask Dr.Tracker for its API documentation first. Test every call with Run once and read the returned bundle before you switch the scenario on.
05Make or n8n for Dr.Tracker?
It depends on where the rest of your automations already live. In Make, Dr.Tracker brings Add a new lead plus Make an API Call, available from the Free plan, and each run is counted in operations. The same app often has an n8n node too, so check which modules it offers there before you choose. Compare what each tool actually covers for your case, which other apps you need to connect, and who on the team will maintain the scenario. Neither choice is wrong if it reaches the Dr.Tracker actions you need.