Resources · Make integration

DigitalPilot Make integrationAutomate DigitalPilot with Make.

Can Make act on the visits and leads DigitalPilot spots? Yes: the DigitalPilot Make integration gives you 3 triggers and 3 actions. This page is for sales and marketing teams, and it walks you from the connection to a first working scenario.

Try the DigitalPilot integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the DigitalPilot Make integration do?

It links your DigitalPilot account to Make so that visits, captured leads and your target account list can feed other tools without code. In Make you build a scenario (the automation itself, a chain of modules), and each module is one brick: a trigger that starts things or an action that does something.

Alert sales on a hot visit. Watch High Intent Visits starts a scenario when DigitalPilot flags a visit worth a follow-up, and the next module can post it wherever your reps already work.

Turn a new lead into a tracked account. Watch Lead Capture picks up the lead, then Add Target Account puts the company on your list, so the next visits from that company show up in Watch Target Account Visits.

Keep the list clean. When a deal closes or a prospect drops out in your CRM, Remove Target Account takes the company off the list without anyone logging in to DigitalPilot.

Know the limits before you start. The Make documentation for DigitalPilot is thin: it lists the 6 modules by name and says openly that it lacks public information on this app. You find the exact fields inside each module once your account is connected, and Make an API Call covers what the listed modules miss. If you are still weighing platforms, the n8n vs Make comparison sets out the criteria, and the Make pricing page explains how operations are counted on each plan.

Connect

How do you connect DigitalPilot to Make?

  1. 01

    Add a DigitalPilot module

    In a new scenario, click the +, type DigitalPilot and pick any of its modules. Then click Create a connection. A connection is your DigitalPilot account linked to Make once, then reused by every DigitalPilot module.

  2. 02

    Name the connection

    Give it a clear name if you like, for example the workspace or the client it belongs to. This step is optional, yet it saves confusion later when several people or several accounts share the same Make organization.

  3. 03

    Authorize and save

    Depending on what DigitalPilot offers, either approve Make on the DigitalPilot page that opens, or paste the key DigitalPilot gives you. Then click Save, and the module can now read your data.

First scenario

Build your first scenario with DigitalPilot

GoalWhen DigitalPilot captures a new lead, Make adds that company to your target accounts.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the canvas to place the first module.

  2. 02

    Place the trigger

    Search for DigitalPilot, choose Watch Lead Capture and pick your connection. Make then shows the options this trigger accepts, so you only fill what it asks for.

  3. 03

    Add the action

    Click the + on the right of the trigger and pick Add Target Account. Map the company details from the lead into its fields by clicking the values the trigger returns.

  4. 04

    Test with Run once

    Click Run once. Each module shows the bundles it received, a bundle being one item passed along, here one lead. Check that the right company reached the action.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, which is also the shortest gap on the Free plan. Set the schedule, then switch the scenario on.

Triggers

Triggers: what can start a DigitalPilot scenario?

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

DigitalPilot1Watch High Intent Visits

Watch High Intent Visits

triggerIn the docs only

This trigger brings the visits DigitalPilot rates as high intent into Make, so a rep can follow up while the interest is fresh instead of finding it later in a report.

How it fires
scheduled, Make checks the app on the scenario's schedule. The docs give no detail, so this type comes from the module name; the clock badge on the module confirms it.
When to use it
you want a sales alert, a task or a CRM note for every promising visit.
Watch out
the docs do not define what counts as high intent, so run it once and read the bundles before you wire alerts to it.
DigitalPilot2Watch Lead Capture

Watch Lead Capture

triggerIn the docs only

Every lead DigitalPilot captures can reach your CRM, your email tool or a spreadsheet with this trigger, which saves you from exporting contacts by hand.

How it fires
scheduled, Make checks the app on the scenario's schedule (a type read from the name, as the docs give none), so new leads arrive in batches rather than one by one the moment they appear.
When to use it
a form or a visitor capture in DigitalPilot should create a contact somewhere else.
Watch out
each lead is a bundle and each module that handles it costs one operation, the unit Make counts on your plan, so a busy site adds up.
DigitalPilot3Watch Target Account Visits

Watch Target Account Visits

triggerIn the docs only

Here you get the visits coming from companies on your target account list, which tells the account owner that a named prospect is back on the site.

How it fires
scheduled, Make checks the app on the scenario's schedule. With no official description, the scheduled type is read from the name, so check the clock badge.
When to use it
your team runs account based marketing and wants each tracked company visit logged in the CRM.
Watch out
it only sees companies already on the list, so pair it with Add Target Account to feed that list first.
Modules

Actions: what can Make do in DigitalPilot?

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

DigitalPilot1

Add Target Account

ActionIn the docs only

With this action a company joins your DigitalPilot target list straight from another tool, and its later visits become visible to Watch Target Account Visits.

When to use it
a deal is created in your CRM, or a lead comes in, and sales wants to follow that company.
Watch out
the docs list no fields, so open the module after connecting to see what it asks for.
DigitalPilot2

Make an API Call

ActionIn the docs only

You reach any endpoint of the DigitalPilot API from your scenario, with the same connection, when none of the five other modules does what you need.

When to use it
you need data or an action the listed modules skip, which is likely given how short the docs are.
Watch out
you will need the DigitalPilot API documentation at hand, since Make does not describe the endpoints for you.
DigitalPilot3

Remove Target Account

ActionIn the docs only

This one takes a company off your DigitalPilot target list, so reps stop getting visit alerts for accounts that no longer matter to them.

When to use it
a deal is won or lost in the CRM, or a prospect asks not to be contacted again.
Watch out
treat it as final and test on a sample account with Run once first, because the docs say nothing about restoring a removed account.
Need help

Need help automating DigitalPilot with Make?

A person reads every message.

FAQ

Questions about DigitalPilot and Make

01Is the DigitalPilot Make integration free?
Yes, on the Make side. DigitalPilot is a standard app, so its modules work from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Your DigitalPilot subscription is a separate matter that this page does not cover.
02What do you need to connect DigitalPilot to Make?
A DigitalPilot account and a Make account. The Make documentation lists no other prerequisite for this app. You add any DigitalPilot module, click Create a connection, optionally name it, then either authorize Make on the DigitalPilot page or paste the key DigitalPilot provides, and click Save. The docs do not say which of the two methods applies, so keep your DigitalPilot settings open in case a key is requested, and test the connection with Run once right after.
03Do DigitalPilot triggers in Make work in real time?
No. All 3 DigitalPilot triggers are scheduled, a type read from their names since the docs describe none: Make checks the app on the scenario's schedule instead of being called by DigitalPilot the moment something happens. A new scenario checks every 15 minutes by default, which is also the minimum on the Free plan. Paid plans can go down to 1 minute. There is no instant DigitalPilot trigger, the kind an app calls through a webhook, listed for this integration, so plan your follow-ups around that delay.
04What if a DigitalPilot module is missing in Make?
Use Make an API Call. It is one of the 6 DigitalPilot modules and lets your scenario reach any endpoint of the DigitalPilot API with the same connection, which covers what the 3 triggers and the two list actions do not. Expect some reading: the Make documentation for DigitalPilot is limited and states that public information on the app is scarce, so the DigitalPilot API docs become your main reference when you build the call.
05Should you use Make or n8n for DigitalPilot?
It depends on the platform your team already runs. On Make, DigitalPilot comes with 6 ready modules, including an API call module for anything else, and runs from the Free plan. n8n often has a node for the same apps, so check whether one exists for DigitalPilot before you decide. Nothing here ranks one tool above the other; compare the modules available on each side and pick the one your team will maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations