Resources · Make integration

Aimfox Make integrationAutomate Aimfox with Make.

What should happen when a prospect answers your LinkedIn outreach? The Aimfox Make integration gives you 20 modules, 12 of them triggers and 8 actions. This guide is for sales and growth teams: connect the account, build a first flow, then pick the right module.

Try the Aimfox integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Aimfox Make integration do for you?

The Aimfox Make integration links your Aimfox workspace to Make, so events from your LinkedIn campaigns start a scenario, the automation you build in Make as a chain of modules. A module is one brick of that chain: a trigger that listens, or an action that changes something in Aimfox. No code is needed.

Replies land where your team works. Watch New Message Reply and Watch Inmail Reply fire as soon as a prospect answers, and the next module can post the message to your sales channel or CRM, then Add a Note to a Lead keeps the context inside Aimfox.

Fresh leads get sorted on arrival. Watch New Leads fires when a campaign wins a lead; Add a Label to a Lead tags it by source or segment, so your follow-up lists stay clean without manual tagging.

Campaigns follow the rest of your stack. A form entry or a signed deal in another tool can call Add a Profile to a Campaign, while Pause a Campaign and Resume a Campaign let an outside event stop or restart outreach.

The listed modules do not cover every part of Aimfox. When one is missing, Make an API Call reuses the same connection to reach other endpoints of the Aimfox API. The Make documentation also warns that its Aimfox page is AI-generated, so check important details with Aimfox. If you are weighing tools, the n8n vs Make comparison sets out the criteria, and the Make pricing page explains how operations are counted. Teams that prefer a hand can look at our Make training.

Connect

How do you connect your Aimfox account to Make?

  1. 01

    Generate an API key in Aimfox

    In Aimfox, open Workspace Settings, then Integrations, and click Create API Key. Give the key a name, choose its permission level, generate it and copy the key shown on screen.

  2. 02

    Add an Aimfox module in Make

    Inside your scenario, search for Aimfox, pick a module and click Create a connection. The Connection name field is optional; a clear name helps when several workspaces share one Make account.

  3. 03

    Paste the key and save

    Paste the API key you copied and confirm. The connection, your Aimfox account linked to Make once, is then reused by every Aimfox module you add later in any scenario.

First scenario

Your first scenario with Aimfox and Make

GoalWhen an Aimfox campaign wins a new lead, Make adds a label to that lead so your team can spot it at a glance.

  1. 01

    Create the scenario

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

  2. 02

    Add Watch New Leads

    Search for Aimfox and pick Watch New Leads. Click Create a webhook, then Create a connection and paste your API key when Make asks for it.

  3. 03

    Chain Add a Label to a Lead

    Click the + on the right of the trigger and choose Add a Label to a Lead. Map the lead coming from the trigger into the module, then pick the label your team uses for new leads.

  4. 04

    Test with Run once

    Click Run once, then let a campaign produce a lead. Open each module's bubble to read the bundle it received, the single lead that flowed through, and check the label in Aimfox.

  5. 05

    Switch the scenario on

    Turn the scenario on. Because Watch New Leads is instant, it runs whenever Aimfox calls Make, not on the clock that scheduled triggers follow.

Triggers

Which Aimfox events can start a scenario?

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

Aimfox1Watch Connected Accounts

Watch Connected Accounts

Instant trigger

In Make“Triggers when a LinkedIn account is connected to Aimfox.”

You learn the moment a LinkedIn account gets linked to your Aimfox workspace, which is handy when several people on one team send outreach.

How it fires
instant trigger, meaning Aimfox calls Make through a webhook as soon as the account is connected; the module shows a lightning badge.
When to use it
announce a new sender in your team chat or log the change in a shared sheet so managers know who is live.
Watch out
it tells you about the account, not about a campaign, so pair it with a campaign module if you need that side too.
Aimfox2Watch Connect Sent

Watch Connect Sent

Instant trigger

In Make“Triggers when a LinkedIn connection request is successfully sent.”

Each connection request that Aimfox manages to send on LinkedIn reaches your scenario, which gives you a trace of outreach volume outside Aimfox.

How it fires
instant, Aimfox pings Make by webhook right after the request goes out.
When to use it
build an activity log in a spreadsheet or mark the prospect as contacted in your CRM so nobody reaches out twice.
Watch out
a busy campaign sends many requests, and every bundle, one request here, costs operations on your Make plan.
Aimfox3Watch Created Campaigns

Watch Created Campaigns

Scheduled trigger

In Make“Triggers when a new Aimfox campaign has been created.”

New campaigns in Aimfox show up in Make, so the rest of your tools can hear about a launch without anyone copying names around.

How it fires
scheduled trigger, Make checks Aimfox on the scenario's schedule (every 15 minutes by default); the module wears a clock badge.
When to use it
create a matching record in your project tool or tell the team a new campaign exists.
Watch out
this is one of only two scheduled triggers here, so it waits for the next check instead of reacting on the spot.
Aimfox4Watch Disconnected Accounts

Watch Disconnected Accounts

Instant trigger

In Make“Triggers when a LinkedIn account is disconnected from Aimfox.”

A LinkedIn account that drops out of Aimfox is flagged to Make, so a silent break in your outreach does not go unnoticed.

How it fires
instant; Aimfox sends the event to Make by webhook as it happens.
When to use it
alert the account owner by email or chat so they reconnect before campaigns stall.
Watch out
pausing campaigns automatically from this event may sound tidy, but check which campaigns actually depend on that account before chaining Pause a Campaign.
Aimfox5Watch Inmail Reply

Watch Inmail Reply

Instant trigger

In Make“Triggers when a user replies to a LinkedIn Inmail message.”

Answers to your LinkedIn InMail messages arrive in Make, ready to be routed to the person who owns the conversation.

How it fires
instant, sent by Aimfox through a webhook once the prospect replies.
When to use it
send a quick alert to the account executive who owns the prospect, or open a new deal in your CRM.
Watch out
regular message replies come through Watch New Message Reply instead; add both triggers in two scenarios if you want every answer.
Aimfox6Watch Inmail Sent

Watch Inmail Sent

Instant trigger

In Make“Triggers when a LinkedIn Inmail message is successfully sent.”

Every InMail that Aimfox delivers successfully becomes a bundle in Make, so you keep a record of InMail outreach outside Aimfox.

How it fires
instant; the webhook call reaches Make right after sending.
When to use it
log InMail activity per prospect in your CRM, which helps later when you check which accounts were already approached.
Watch out
it only covers messages that went out; a failed send does not reach this trigger, so it cannot serve as an error alert.
Aimfox7Watch Message Request Sent

Watch Message Request Sent

Instant trigger

In Make“Triggers when a message request is sent.”

When Aimfox sends a message request, your scenario hears about it and can record the first touch with that prospect.

How it fires
instant, Aimfox calls Make by webhook once the request is sent.
When to use it
set a follow-up task in your CRM or add the prospect to a tracking sheet so the team sees who is waiting for an answer.
Watch out
this is a separate event from connection requests and InMail; pick the trigger that matches the step of your sequence you want to track.
Aimfox8Watch New Leads

Watch New Leads

Instant trigger

In Make“Triggers when a new workspace lead is gained through an Aimfox campaign.”

This trigger hands you every lead a campaign wins in your Aimfox workspace, the most direct way to feed your pipeline from LinkedIn.

How it fires
instant; Aimfox calls Make through a webhook when the lead is gained.
When to use it
create the contact in your CRM, then tag it in Aimfox with Add a Label to a Lead, as in the first scenario above.
Watch out
test with Run once while a campaign is active, otherwise the trigger has no lead to send and the test looks empty.
Aimfox9Watch New Message Reply

Watch New Message Reply

Instant trigger

In Make“Triggers when a user replies to a LinkedIn message.”

A prospect answering one of your LinkedIn messages starts the scenario, so the reply reaches a human fast instead of waiting in the inbox.

How it fires
instant; the webhook from Aimfox arrives in Make as soon as the reply exists.
When to use it
post the reply to your sales channel, then add a note on the lead with Add a Note to a Lead so the context stays in Aimfox.
Watch out
Watch New Replies looks similar but is most likely scheduled; choose this one when speed matters.
Aimfox10Watch Sent Messages

Watch Sent Messages

Instant trigger

In Make“Triggers when a message is successfully sent to a LinkedIn profile.”

Each message Aimfox delivers to a LinkedIn profile is passed to Make, giving you a full trace of the conversation from your side.

How it fires
instant, sent by webhook right after delivery.
When to use it
copy outgoing messages into your CRM timeline so anyone opening the contact sees what was said.
Watch out
messages sent with Send a Message to a Conversation are likely to show up here too, so do not use this trigger to fire that same action again, or the scenario feeds itself.
Aimfox11Watch Viewed Lead

Watch Viewed Lead

Instant trigger

In Make“Triggers when a LinkedIn profile is viewed.”

You get a bundle whenever a LinkedIn profile is viewed from Aimfox, a light signal of who your outreach is looking at.

How it fires
instant, Aimfox calls Make by webhook when the view happens.
When to use it
add a line to a prospect tracking sheet or update a field in your CRM to show the first touch.
Watch out
profile views can be frequent in an active campaign, so filter the flow before any heavy module to keep operations under control.
Aimfox12Watch New Replies

Watch New Replies

triggerIn the docs only

Collects new replies from Aimfox on a schedule, a calmer option when you prefer to review answers in batches.

How it fires
scheduled, as far as we can tell: the documentation gives no type, and the name follows Make's pattern for polling triggers. Make would then check Aimfox on the scenario's schedule, every 15 minutes by default.
When to use it
send a digest of replies to a sales manager instead of one alert per message.
Watch out
the Make documentation lists this module without any description, so its exact scope is not documented; run it once and read the bundles before building on it, and prefer Watch New Message Reply when you need instant alerts.
Modules

What can Make change in Aimfox?

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

Aimfox1

Add a Label to a Lead

Action

In Make“This action adds a specific label to the selected lead.”

Puts a label on a lead in Aimfox, so your lists sort themselves by source, stage or priority without manual tagging.

When to use it
right after Watch New Leads, or when your CRM moves a deal forward and Aimfox should reflect it.
Watch out
the module needs to know which lead to update, so map the lead from the previous module instead of typing it by hand.
Aimfox2

Add a Note to a Lead

Action

In Make“This actions add a specific note to the selected Aimfox lead.”

Writes a note on a lead, which keeps context from other tools visible to anyone who opens that lead in Aimfox.

When to use it
after a call logged in your CRM or a reply received, paste a short summary so the next message is informed.
Watch out
a note adds text rather than replacing it, so a scenario that runs often can pile up duplicates; filter before this module.
Aimfox3

Add a Profile to a Campaign

Action

In Make“Adds a LinkedIn profile to an Aimfox campaign.”

Drops a LinkedIn profile into an existing Aimfox campaign, turning a lead found elsewhere into outreach without a copy and paste.

When to use it
someone fills a form or attends a webinar, and you want them in the matching LinkedIn sequence.
Watch out
if your campaign messages rely on personalised variables, use Add a Profile to a Campaign with Custom Variables instead.
Aimfox4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Aimfox API from your scenario with the connection you already have, the way to cover what the listed modules leave out.

When to use it
you need an Aimfox action or read that none of the other modules offers.
Watch out
you describe the request yourself, so keep the Aimfox API documentation open and check that your API key's permission level allows the call.
Aimfox5

Pause a Campaign

Action

In Make“Pauses an existing Aimfox campaign.”

Stops an Aimfox campaign from your scenario, so an event in another tool can halt outreach before a wrong message goes out.

When to use it
a target account signs, an offer ends, or a sender account disconnects and you want everything on hold.
Watch out
pausing hits the whole campaign, not one prospect, so check which campaign the module points to before switching the scenario on.
Aimfox6

Resume a Campaign

Action

In Make“Used to resume an existing Aimfox campaign.”

Restarts a paused Aimfox campaign, the counterpart of Pause a Campaign when the reason for the stop is gone.

When to use it
a sender account is connected again, which Watch Connected Accounts can tell you, or a manager approves the new copy.
Watch out
pair it with a clear condition; resuming a campaign that was paused on purpose can restart messages nobody wanted to send.
Aimfox7

Add a Profile to a Campaign with Custom Variables

ActionIn the docs only

Adds a LinkedIn profile to a campaign together with custom variables, so your sequence can greet each prospect with details from your other tools.

When to use it
the lead comes from a form or CRM that already holds useful context, such as the event they joined.
Watch out
the Make documentation gives no description of this module, so run it once and check in Aimfox how the variables appear before scaling.
Aimfox8

Send a Message to a Conversation

ActionIn the docs only

Posts a message into an existing Aimfox conversation, letting a scenario answer or follow up without opening LinkedIn.

When to use it
a prospect books a meeting in your calendar tool and you want a confirmation line in the same thread.
Watch out
the module is listed without an official description; keep a human check on the wording, and never trigger it from Watch Sent Messages, or it will loop.
Need help

Need help automating Aimfox with Make?

A person reads every message.

FAQ

Aimfox and Make: common questions

01Is the Aimfox Make integration free?
Yes, on the Make side. Aimfox is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution and 512 MB of data transfer. Each operation, one module running on one bundle, counts against your plan. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. You still need an active Aimfox account with an API key, and Aimfox sets its own subscription terms.
02What do you need to connect Aimfox to Make?
An active Aimfox account and an API key. You create the key in Aimfox under Workspace Settings, then Integrations, with the Create API Key button, where you name it and choose its permission level. In Make, you add an Aimfox module, click Create a connection, optionally name the connection and paste the key. For an instant module, Make first asks you to click Create a webhook. The permission level you pick decides what the modules are allowed to do.
03Do Aimfox triggers in Make react in real time?
Most of them do. Ten of the twelve triggers are instant: Aimfox calls Make by webhook as soon as a reply, a lead, a sent message or an account change happens. The other two are scheduled: Watch Created Campaigns for sure, and Watch New Replies judging by its name, since the documentation gives it no type. That means Make checks Aimfox on the scenario's schedule, every 15 minutes by default and never below 15 minutes on the Free plan. Pick an instant trigger when a fast human follow-up matters.
04What if an Aimfox module is missing in Make?
It depends on the gap. The integration includes Make an API Call, which calls any endpoint of the Aimfox API with the connection you already set up, so an action missing from the list can usually be built there. You write the request yourself, following the Aimfox API documentation, and the permission level of your API key has to allow it. The Make documentation also notes that its Aimfox page is AI-generated, so confirm important details with Aimfox.
05Should you use Make or n8n for Aimfox?
It depends on what you need to build. On Make, Aimfox comes with 20 ready modules: 12 triggers, most of them instant, and 8 actions, plus Make an API Call for anything else, all set up without code. On the n8n side, check first whether a node for Aimfox exists, since this page cannot confirm it. The comparison page on the site lays out the criteria side by side without declaring a winner.
Same platform

Other docs you might need on this stack.

Browse all integrations