Resources · Make integration

Apollo Make integrationAutomate Apollo with Make.

What if every new Apollo contact came with a follow-up task already assigned? The Apollo Make integration gives you 15 modules: 3 triggers, 8 actions and 4 searches. This page shows sales and ops teams how to connect the account and build a first scenario step by step.

Try the Apollo integration on MakeSee the 15 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Apollo Make integration do for your pipeline?

The Apollo Make integration links your Apollo account to Make, a visual tool where you chain apps into a scenario, the automation you build. Each brick of that chain is a module. With Apollo you can watch for new records, then create, update or list accounts, contacts, opportunities and tasks without writing code.

No new lead left without an owner. Start on Watch New Contacts and add Create a Task: each person who lands in Apollo gets a task assigned to a rep, so nobody has to remember to follow up.

A deal opened the moment a company shows up. Watch New Accounts spots each new company, and Create an Opportunity opens a record to track the possible deal. Your pipeline view reflects new accounts without manual entry.

Contact changes pushed to the rest of your stack. Watch Updated Contacts picks up edited contacts, and the next module can send those changes to a spreadsheet or another CRM. The Airtable Make integration is a common destination for that kind of copy.

What Make does not offer here: an instant trigger. All 3 Apollo triggers are scheduled, so Make checks Apollo on the scenario's schedule rather than being called by Apollo. When a listed module does not cover what you need, Make an API Call reaches the rest of the Apollo API with the same connection.

New to the tool? The Make training walks through the editor from scratch. Also weighing n8n? The n8n vs Make comparison sets the two tools side by side.

Connect

How do you connect your Apollo account to Make?

  1. 01

    Generate an API key in Apollo

    In Apollo, open Settings then Integrations in the left sidebar. Under the API option click Connect, then API Keys and Create New Key. Give it a name, a description and the APIs it covers, click Create API Key and copy it.

  2. 02

    Open the connection window in Make

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

  3. 03

    Paste the key and save

    Paste the key you copied into the API Key field and click Save. If Apollo asks you to authenticate and confirm access, accept. Make can then read your accounts, contacts, opportunities and tasks in the module fields.

First scenario

Your first scenario: a follow-up task for each new contact

GoalWhen a new contact appears in Apollo, Make creates a follow-up task and assigns it to a rep.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario. An empty canvas opens with a large +: click it to add the first module, the one that starts everything.

  2. 02

    Add Watch New Contacts

    Search for Apollo, pick Watch New Contacts and click Create a connection, or choose the one you already made. This trigger looks for contacts created since the last check.

  3. 03

    Chain Create a Task

    Click the + on the right of the trigger and pick Create a Task. Map the contact coming from the trigger into the task, then choose the user who should receive it. Each contact travels as one bundle.

  4. 04

    Test with Run once

    Add a test contact in Apollo, then click Run once. Make runs the scenario one time and shows the bundles each module received, so you can check the task landed on the right person.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, which is also the shortest interval on the Free plan. Keep it or change it, then switch the scenario on.

Triggers

Which Apollo triggers can start a scenario?

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

Apollo1Watch New Accounts

Watch New Accounts

Scheduled trigger

In Make“Triggers when a new account is created.”

This trigger hands your scenario every company account created in Apollo since the previous check, so each new account can kick off its own follow-up without anyone copying it by hand.

How it fires
it is a scheduled trigger, so Make checks Apollo on the scenario's schedule instead of waiting for Apollo to call it.
When to use it
when a new target company should open an opportunity or alert the team that owns that market.
Watch out
it only reacts to new accounts; an edit on an existing account will not start the scenario.
Apollo2Watch New Contacts

Watch New Contacts

Scheduled trigger

In Make“Triggers when a new contact is created.”

You get each person newly added to Apollo as a bundle, ready to be turned into a task, a message or a row somewhere else. It is the natural starting point for any lead routing flow.

How it fires
scheduled; Make looks at Apollo on the rhythm you set on the scenario, every 15 minutes by default.
When to use it
when every fresh prospect must be assigned to a rep or copied into another tool at the next check.
Watch out
contacts that already existed are ignored, so pick Watch Updated Contacts if edits matter to you.
Apollo3Watch Updated Contacts

Watch Updated Contacts

Scheduled trigger

In Make“Triggers when an existing contact is updated.”

Here the scenario starts on change rather than on creation: any existing Apollo contact that gets edited comes through, which keeps other tools in line with what your reps change in Apollo.

How it fires
scheduled as well, with Make checking Apollo on the scenario's schedule and passing along the contacts edited since its last visit.
When to use it
when a spreadsheet or a second CRM has to mirror the latest version of each contact.
Watch out
if a later module writes back to the same contacts, the scenario may pick up its own edits on the next check.
Modules

What else can Make do in Apollo?

Apollo gives you 12 modules in 5 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Accounts

3 modules
Apollo1

Create an Account

Action

In Make“Creates an account for a company in your database.”

Adds a company to your Apollo database from data found elsewhere, such as a signed form, a spreadsheet row or a deal won in another tool, so the account exists before your reps start prospecting it.

When to use it
when companies first appear outside Apollo and you want them there without retyping.
Watch out
run List Accounts first if the company might already exist, to avoid a duplicate.
Apollo2

Update an Account

Action

In Make“Updates information about the selected account.”

Changes the details of an account you pick, which keeps Apollo aligned with the source of truth your team trusts, for example a billing tool or an internal company sheet.

When to use it
when a company changes something in another system and Apollo should reflect it.
Watch out
the module needs to know which account to edit, so place a search or a trigger before it to supply that account.
Apollo3

List Accounts

Search

In Make“Returns a list of accounts.”

Returns the accounts stored in Apollo so a later module can act on them. As a search, it can send back zero, one or several bundles, and every bundle runs the modules that follow.

When to use it
to check whether a company is already there before creating it, or to process a set of accounts together.
Watch out
each returned account costs operations downstream, so narrow the search when you can.

Contacts

3 modules
Apollo4

Create a Contact

Action

In Make“Creates a contact for a person in your database.”

Puts a new person into Apollo from any other app in the scenario: a webinar signup, a demo request, a business card scanned into a sheet. Your reps then find that person in Apollo with the rest of their pipeline.

When to use it
when leads are captured outside Apollo and should be worked there.
Watch out
a Watch New Contacts scenario will see these contacts too, so avoid building a loop between the two.
Apollo5

Update a Contact

Action

In Make“Updates information about the selected contact.”

Edits a contact you select, so a job change, a new phone number or a qualification decided elsewhere ends up on the right person in Apollo without a rep doing it by hand.

When to use it
when another tool, such as a form or a support desk, learns something new about a prospect.
Watch out
if Watch Updated Contacts runs in another scenario, every edit made here will start that one as well.
Apollo6

List Contacts

Search

In Make“Returns a list of contacts.”

Pulls a list of contacts out of Apollo and passes each one to the next module as its own bundle, which lets a scenario review, export or enrich many people in a single run.

When to use it
before creating a contact, to see if the person is already there, or to send a batch of contacts to a spreadsheet.
Watch out
an empty result stops the flow there, which is often exactly what a duplicate check needs.

Opportunities

3 modules
Apollo7

Create an Opportunity

Action

In Make“Creates records that you can use to track possible deals with your prospective customers.”

Opens a deal record in Apollo so a possible sale is tracked from the first signal, whether that signal is a new account, a demo booked in a calendar tool or a quote request.

When to use it
when an event in another app means a prospect has become a real opportunity worth following.
Watch out
tie it to a clear event; creating deals on every new contact quickly fills the pipeline with noise.
Apollo8

Update an Opportunity

Action

In Make“Updates the details of an already existing opportunity.”

Moves an existing deal forward by changing its details, so the pipeline in Apollo follows what really happened: a contract signed, a quote sent, a meeting that went well.

When to use it
when the progress of a deal is recorded in another tool, such as an e-signature or invoicing app.
Watch out
it edits a deal that already exists; List Opportunities is the usual way to find which one.
Apollo9

List Opportunities

Search

In Make“Returns a list of opportunities.”

Gives you the opportunities stored in Apollo, one bundle per deal, so the scenario can report on them, copy them to a sheet or pick the one to update next.

When to use it
to build a pipeline table outside Apollo or to locate the deal matching an event in another tool.
Watch out
each deal returned sends its own bundle to every following module, and each module run counts as an operation.

Tasks

2 modules
Apollo10

Create a Task

Action

In Make“Creates and assigns a task to a user.”

Creates a to-do in Apollo and assigns it to a user, which turns an event anywhere in your stack into a clear next step for a named person on the team.

When to use it
right after a new contact, a form submission or a deal update that someone has to act on.
Watch out
choose the assignee on purpose; sending every task to the same user hides who really owns the follow-up.
Apollo11

List Tasks

Search

In Make“Returns a list of tasks.”

Reads the tasks in Apollo and returns them one by one, handy when you want a view of pending work outside Apollo or need to check what already exists before adding more.

When to use it
to send open tasks to a team channel or a shared sheet, or to avoid creating the same task twice.
Watch out
no task list means no bundle, so the modules after it simply do not run.

Other

1 module
Apollo12

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Lets you reach any endpoint of the Apollo API from the scenario, using the same connection as the other modules. It covers whatever the dedicated Apollo modules leave out.

When to use it
when the operation you need has no dedicated module in the list above.
Watch out
you build the request yourself, so keep the Apollo API documentation open while you set it up.
Need help

Need help automating Apollo with Make?

A person reads every message.

FAQ

Questions about the Apollo Make integration

01Is the Apollo Make integration free?
Yes, Apollo is a standard app, so it works on the Make Free plan. That plan has limits: 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 allow unlimited active scenarios. Make counts usage in operations, one per module run on one bundle. Your Apollo subscription is a separate matter.
02What do you need to connect Apollo to Make?
You need an Apollo account and an API key created in it. In Apollo, go to Settings then Integrations, click Connect under the API option, then API Keys and Create New Key. Give the key a name, a description and the APIs it covers, create it and copy it. In Make, click Create a connection on any Apollo module, paste the key in the API Key field and click Save. Confirm access if Apollo asks.
03Do Apollo triggers fire instantly in Make?
No. Watch New Accounts, Watch New Contacts and Watch Updated Contacts are all scheduled triggers. Make checks Apollo on the scenario's schedule, every 15 minutes by default, and picks up what changed since the last check. On the Free plan 15 minutes is the shortest interval; paid plans go down to 1 minute. Apollo has no instant trigger in Make, so there is no webhook option on any of these modules.
04What if the Apollo module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Apollo API with the same connection as the other Apollo modules, so you can reach data that accounts, contacts, opportunities and tasks modules do not cover. You write the request yourself with the Apollo API documentation at hand. The Make documentation for Apollo does not publish any numeric limit for these modules. It reuses your existing connection, so no new key is needed. Since you chose the APIs tied to that key when you created it, check that they include the one you plan to call.
05Make or n8n for Apollo automations?
It depends on which tool your team already builds in. On Make, Apollo comes with 15 ready modules, including 3 scheduled triggers and Make an API Call, and it runs from the Free plan. n8n often has a node for the same app, so check what it offers for Apollo if your automations already live there. The n8n vs Make comparison on this site sets both tools side by side without naming a winner.
Same platform

Other docs you might need on this stack.

Browse all integrations