Resources · Zapier integration

Aimfox Zapier integrationAutomate Aimfox with Zapier.

The Aimfox Zapier integration gives you 18 triggers, 15 actions and 14 searches to wire your LinkedIn outreach into the rest of your tools. Every trigger is instant, Aimfox is not a premium app, and a free plan is enough to start.

See the 47 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Aimfox Zapier integration actually does for you

The Aimfox Zapier integration links your Aimfox workspace to Zapier, so that something happening on LinkedIn (a reply, an accepted invite, a profile view) starts an automation on its own. Zapier calls that automation a Zap: one starting event, then the steps that follow every time it happens.

Three results come up again and again once it is running.

A sorted inbox. When someone answers a campaign, Campaign Reply fires and Add Label to Lead tags them, so your SDRs open a filtered list instead of scrolling through everything.

Campaigns that react on their own. If a LinkedIn account drops out of the workspace, Account Disconnected can call Pause Campaign so the sequence waits instead of running without its sender. Resume Campaign brings it back once the account is fixed.

A cleaner audience. Add Profile to Blacklist and Add Company to Blacklist keep customers, partners or competitors out of every future sequence, driven by whatever tool knows who they are.

What Zapier does not do here: it never reaches back into history. A Zap only sees events that happen after you switch it on, so last month's replies stay where they are. It also cannot change how a trigger works: all 18 Aimfox triggers are instant, and that is decided by Aimfox, not by you.

If you are weighing other tools, the Aimfox Make integration covers the same app on Make, and n8n vs Zapier sets the two platforms side by side.

Vocabulary

Zapier vocabulary in one minute

Eight words carry the whole page. Read them once, and the rest reads like plain English.

Zap
Your automation on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it, here inside Aimfox.
Action
What the Zap does after it starts: the step that writes, sends or changes something for you, like labelling a lead.
Task
What Zapier bills you for: one action that completes successfully. The number on your plan counts exactly those.
Polling vs instant trigger
Polling: Zapier checks the app on a timer. Instant: the app calls Zapier the second the event happens. Aimfox only has instant ones.
Filter
A step that lets the Zap continue only when the incoming data matches your condition, and stops it quietly otherwise.
Search step
A step that looks up something already stored in an app, so the steps after it can use what it found.
Connection
Your Aimfox account linked to Zapier once, then reused by every step that talks to Aimfox in any of your Zaps.
Cost

What an Aimfox Zap really costs

Zapier counts tasks, not Zaps. The trigger is free, checking for new data is free, and only an action that goes through is billed.

  • TriggerNever costs a task
  • Successful action1 task each
  • Free plan100 tasks a month, two-step Zaps only
  • Filter or searchMakes the Zap multi-step, paid plan needed
  • AimfoxNot premium, works on the free plan

A Zap with three actions uses three tasks per run, one per action that succeeds. An action that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. Add a filter or a search step and it becomes a multi-step Zap, which needs a paid plan. Aimfox is not a premium app, so the free plan can use it. The polling grid below does not touch Aimfox, since every one of its triggers is instant.

Connect

Connect your Aimfox account to Zapier

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an Aimfox account, plus access to any workspace you do not own yourself but want the Zap to touch.

  2. 02

    Pick Aimfox

    Type Aimfox in the search box of the dialog, select it in the results, then click Add connection. Zapier opens a new tab where Aimfox asks you to sign in.

  3. 03

    Sign in and grant access

    Log in to Aimfox in that tab and allow Zapier to reach the account. The connection is now stored once, and every Aimfox step of every Zap can reuse it.

First Zap

Your first Zap: label the hot replies

GoalAn SDR team wants every positive reply to a campaign tagged in Aimfox, so follow-ups start from a short list.

  1. 01

    Build: pick the trigger

    Create a Zap, choose Aimfox as the starting app and Campaign Reply as the event. Select your connection, then the Workspace that runs the campaign.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items from the account, so you map fields on a real reply rather than a guess.

  3. 03

    Add a filter

    Click the plus icon and add Filter. Pick the reply text, a text rule, and your keyword. This step makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the action

    Add Add Label to Lead. Choose the same Workspace, map the lead from the trigger, type the label text and pick its colour.

  5. 05

    Test, then Publish

    Test the action once with the sample reply and check the label in Aimfox. Then click Publish: from now on, every matching reply gets tagged.

Triggers

The 18 Aimfox triggers

18 events start a Zap when something happens in Aimfox, and 18 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Account Connected

Instant trigger

In Zapier“Triggers when a LinkedIn account has been connected to an Aimfox workspace.”

Fires as soon as a LinkedIn account joins one of your Aimfox workspaces, so the rest of your stack learns about the new sender right away.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an agency onboarding a client's sales rep can log the new seat in its billing sheet the minute the account goes live.
Watch out
you pick one Workspace per Zap, so a second workspace needs its own Zap.
2

Account Disconnected

Instant trigger

In Zapier“Triggers when a LinkedIn account has been disconnected from an Aimfox workspace.”

Goes off when a LinkedIn account drops out of an Aimfox workspace. Whoever runs that sender needs to know fast.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a growth lead running several reps wants an alert, or wants Pause Campaign called on that rep's sequences, before prospects notice gaps.
Watch out
the Zap watches a single Workspace, the one you select when you set the trigger.
3

Campaign Created

Instant trigger

In Zapier“Triggers when an Aimfox campaign has been created.”

Reports each new campaign built in Aimfox. Useful when someone else in the team owns reporting and needs to know what has just been set up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a sales manager wants every new campaign listed in the team's tracker before it starts sending, to review targeting.
Watch out
creation is not launch; Campaign Started is the event that says it is actually running.
4

Campaign Ended

Instant trigger

In Zapier“Triggers when an Aimfox campaign has ended.”

Signals that an Aimfox campaign has finished. It is the natural hook for wrap-up work: reporting, handing leads over, or planning the next wave.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an outbound consultant sends the client a note that the sequence is done, then pulls results with Find Campaign in a later step.
5

Campaign Reply

Instant trigger

In Zapier“Triggers when a user replies to an Aimfox campaign message.”

Catches replies to messages sent by an Aimfox campaign. Only campaign traffic counts here, which keeps the Zap focused on outreach results.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an SDR team labels replies in Aimfox and pings the account executive, so nobody waits on a hot lead.
Watch out
replies outside campaigns are missed; New Reply is the broader trigger.
6

Campaign Started

Instant trigger

In Zapier“Triggers when an Aimfox campaign is started for the first time.”

Fires the first time a campaign starts sending. Later restarts after a pause do not count, which makes it a clean launch signal.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a marketing lead wants the launch date of each campaign logged once, to line up LinkedIn outreach with an email push.
Watch out
resuming a paused campaign does not fire it again.
7

Connect Sent

Instant trigger

In Zapier“This event triggers when a LinkedIn connection request is successfully sent”

Goes off whenever Aimfox successfully sends a LinkedIn connection request. Think of it as a running log of every invite that left your account.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a founder doing outreach alone keeps a sheet of who was invited and when, to compare with acceptances later.
Watch out
on a busy account this fires a lot, and each action after it costs a task.
8

Inbox Event

Instant trigger

In Zapier“Triggers for all inbox-related activities such as new messages, new replies etc. The 'type' field inside the event object indicates whether the event was sent or received.”

The widest trigger of the app: any inbox activity, new messages and replies alike. Each event says whether it was sent or received.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a team mirroring the whole LinkedIn inbox into its CRM timeline, both directions, without building one Zap per message type.
Watch out
add a filter on that sent or received value, otherwise your own messages run the Zap too.
9

Inmail Sent

Instant trigger

In Zapier“This event triggers when a LinkedIn Inmail message is successfully sent.”

Fires once a LinkedIn InMail goes out successfully through Aimfox. Only successful sends count, so the log matches what actually reached people.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a recruiter logs every InMail sent to a candidate in the hiring pipeline, so two people never message the same person.
Watch out
this is InMail only; plain messages go through Message Sent.
10

Inmail Reply

Instant trigger

In Zapier“This event triggers when a user replies to a LinkedIn Inmail message, initiating a conversation.”

Picks up the answer when someone replies to an InMail and a conversation opens. It is the moment a cold contact becomes a live one.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a talent team moves the candidate to the screening stage and alerts the hiring manager as soon as they answer.
Watch out
regular message replies do not fire it; this one is for InMails only.
11

Lead Label Added

Instant trigger

In Zapier“Triggers when a label is added to a lead in the inbox.”

Reacts when someone puts a label on a lead in the Aimfox inbox. Your team's manual sorting becomes a switch for automations.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a rep tags a lead as qualified, and the Zap pushes it into the CRM without a second click.
Watch out
a Zap that adds labels and listens for labels can loop; keep them on different labels with a filter.
12

Message Sent

Instant trigger

In Zapier“This event triggers when a message is successfully sent to a LinkedIn profile.”

Starts the Zap after Aimfox successfully delivers a message to a LinkedIn profile. Failed sends stay out of it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a sales ops person stamps a last contacted date on the matching CRM record, so reps see recent activity at a glance.
Watch out
InMails and message requests have their own triggers, Inmail Sent and Message Request Sent.
13

Message Request Sent

Instant trigger

In Zapier“This event triggers when a message request is sent.”

Covers message requests sent through Aimfox. Each request that goes out starts the Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a growth marketer testing message requests against classic invites logs both in one sheet to compare reply rates.
Watch out
classic invites fire Connect Sent instead, so you need both Zaps for that comparison.
14

New Connection

Instant trigger

In Zapier“Triggers when a new connection is acquired through Aimfox, indicating the successful addition of a LinkedIn connection.”

Fires when Aimfox gains a new LinkedIn connection for you. Your network grows, and the rest of your tools hear about it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a consultant adds each new connection to a nurture list in the email tool, with a tag saying where it came from.
Watch out
Connect Request Accepted reads very close; test both on a real item and keep the one that fits your goal.
15

Connect Request Accepted

Instant trigger

In Zapier“Triggers when a LinkedIn connection request is accepted, establishing a new connection between profiles.”

Watches for the yes: a LinkedIn connection request accepted, the moment a cold profile becomes a connection.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an agency running outbound for a SaaS client creates a CRM contact the moment the invite is accepted, before any message is sent.
Watch out
its workspace field is labelled Choose Workspace, not Workspace, but it does the same job.
16

New Reply

Instant trigger

In Zapier“Triggers whenever a message is replied to on LinkedIn. This event catches all replies, not just Aimfox campaign replies.”

Catches every reply on LinkedIn, inside campaigns or not. Nothing a prospect writes back slips through.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a small sales team pushes all replies into one shared channel, including conversations a rep started by hand.
Watch out
it overlaps with Campaign Reply and Message Reply; running two of them on the same Zap goal doubles your tasks.
17

Message Reply

Instant trigger

In Zapier“Triggers when a user replies to an Aimfox campaign message, initiating a conversation. Only captures the first reply.”

Fires on the first reply to an Aimfox campaign message, the one that opens a conversation. Follow-up replies in that thread do not count.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a team wants exactly one deal or one alert per prospect who engages, not one per message.
Watch out
only the first reply is captured, so do not count on it to track a whole exchange.
18

Lead Viewed

Instant trigger

In Zapier“This event triggers when a LinkedIn profile is viewed.”

Each time a LinkedIn profile is viewed through Aimfox, the Zap runs. On a running campaign, that can mean a lot of runs.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an outbound team logs the first touch on each prospect, to measure how long it takes to go from view to reply.
Watch out
views pile up quickly; with 100 tasks a month on the free plan, think twice before hanging an action on it.
Actions

The 15 Aimfox actions

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

1

Add Company to Blacklist

Action

In Zapier“This action is used to add a company to the blacklist.”

Blocks a whole company, by its LinkedIn company URL, so no one there gets targeted.

When to use it
a new partner signs and the partnerships team wants their staff off every list.
Watch out
use the company page URL, not a person's profile.
2

Add Custom Variables to Target

Action

In Zapier“This action is used to add custom variables to a specific target of an Aimfox campaign.”

Updates the variables of someone already inside a campaign, without removing and re-adding them.

When to use it
your CRM enriches a prospect with a job change, and the next message should mention it.
Watch out
you need both the Campaign ID and the Target URN, so a search step usually comes first.
3

Add Note to Lead

Action

In Zapier“This action adds a specific note to the selected lead.”

Writes the note you choose on the lead you pick, straight from Zapier.

When to use it
a call summary from your meeting tool lands on the lead, so the next touch has context.
Watch out
you choose the lead and type the note text, both mandatory.
4

Add Multiple Profiles to Blacklist

Action

In Zapier“This action is used to blacklist multiple profiles using their URLs.”

Blocks several profiles in one go from a list of LinkedIn URLs separated by commas.

When to use it
an export of current customers is pushed once so no campaign targets them.
Watch out
the URLs go in one field, separated by commas.
5

Add Profile to Blacklist

Action

In Zapier“This action is used to blacklist a LinkedIn profile.”

Blocks one LinkedIn profile from your future Aimfox campaigns in that workspace.

When to use it
a deal marked won in the CRM keeps that customer out of cold outreach.
Watch out
it asks for the Target URN, not a profile URL, so map it from an earlier step.
6

Add Profile to Campaign

Action

In Zapier“This action is used to add a LinkedIn profile to a specific Aimfox campaign using the profile's URL.”

Drops a LinkedIn profile into an existing Aimfox campaign from its URL, and the sequence picks it up from there.

When to use it
a webinar signup with a LinkedIn link goes straight into the follow-up campaign.
Watch out
it needs the full profile URL, not just a name.
7

Add Profile to Campaign With Custom Variables

Action

In Zapier“This action is used to add a LinkedIn profile with custom variables to a specific Aimfox list campaign using the profile's URL.”

Same move, but with custom variables attached, so your message templates can quote the company, the event or the pain point for that person.

When to use it
event leads join a list campaign with the session they attended as a variable.
Watch out
it targets list campaigns.
8

Add Label to Lead

Action

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

Puts a label on a lead, with the text and colour you set.

When to use it
replies containing a pricing question get a label the sales lead filters on.
Watch out
label text and label colour are both required fields.
9

Update Account Limits

Action

In Zapier“This action is used to update the interaction limits of an Aimfox account.”

Changes how many connects, message requests and InMails an Aimfox account may send.

When to use it
a warm-up plan raises a new account's limits in steps, driven from a sheet.
Watch out
all three limits plus the Account ID are required in the same step.
10

Pause Campaign

Action

In Zapier“This action pauses an Aimfox campaign.”

Puts a running Aimfox campaign on hold from Zapier, from the campaign you choose.

When to use it
an account gets disconnected and the campaign should hold until it is back.
Watch out
if the pause is temporary, plan a second Zap with Resume Campaign.
11

Read a Conversation

Action

In Zapier“This action is used to mark a specific conversation as read.”

Marks a conversation as read in Aimfox, so the thread no longer reads as unread.

When to use it
a reply already handled in your helpdesk should not sit unread for the rep.
Watch out
Account ID and Conversation URN are both required.
12

Remove Profile From Campaign

Action

In Zapier“This actions is used to remove a profile from an Aimfox campaign using the profile URN.”

Pulls one person out of a running campaign, so no more steps go to them.

When to use it
a prospect books a meeting through your calendar tool, and the sequence should stop chasing them.
Watch out
it works with the Profile URN, not the URL.
13

Resume Campaign

Action

In Zapier“This action resumes an Aimfox campaign.”

Restarts a paused campaign from Zapier, the mirror of Pause Campaign.

When to use it
an Account Connected event tells you the sender is back, and the campaign can run again.
Watch out
resuming does not fire Campaign Started a second time.
14

Send Message to Conversation

Action

In Zapier“This action is used to send a message to a specific Aimfox conversation”

Adds a message to a conversation that already exists in Aimfox, keeping the thread in one place.

When to use it
a payment confirmed in your billing tool triggers a short thank-you in the existing chat.
Watch out
you need the Conversation URN and the sending Account ID.
15

Start Conversation

Action

In Zapier“This action is used to start a conversation with a specific LinkedIn account.”

Opens a new LinkedIn conversation from one of your accounts with a message you write or map from earlier steps.

When to use it
a form asks to be contacted on LinkedIn, and the rep's account sends the first message.
Watch out
it wants both the sender's Account ID and the recipient's Target ID.
Searches

The 14 Aimfox searches

14 search steps look for data that already exists in Aimfox, so a later step can use it.

A search step looks up something that already exists in Aimfox and hands it to the next steps. In the editor, Aimfox searches sit at the bottom of the Action event list, under SEARCH. Many Aimfox actions want an ID or a URN; a search is how you get one. Some fields even offer + Add search step, which inserts the search right before and wires the result in. Aimfox has no find-or-create variant.

1

Find Account Limits

Search

In Zapier“This actions is used to get the interaction limits of an Aimfox account”

Reads the current interaction limits of one Aimfox account.

When to use it
check today's ceiling before Update Account Limits raises it, so a warm-up never jumps too far.
Watch out
it needs the Account ID of the Aimfox account, which Find Accounts can hand over if you do not have it at hand.
2

Find Campaign

Search

In Zapier“This actions is used to find the details of an Aimfox campaign.”

Pulls the details of one campaign from its Campaign ID.

When to use it
after Campaign Ended, fetch the campaign to build a short wrap-up for the client.
Watch out
it needs the ID, not the campaign name. A Find Campaigns step earlier in the Zap can supply it.
3

Find Campaign Custom Variables

Search

In Zapier“This action is used to find the custom variables of a specific campaign.”

Lists which custom variables a campaign uses, so you map the right ones in later steps.

When to use it
before adding profiles with variables, confirm the campaign expects a company field.
Watch out
it only takes a Campaign ID, so pair it with Find Campaigns when your trigger did not bring one.
4

Find Campaign Custom Variables for a Target

Search

In Zapier“This actions is used to find the custom variables of an Aimfox campaign for a specific target.”

Returns the variables stored for one person inside one campaign.

When to use it
check what a prospect's message will say before Add Custom Variables to Target overwrites it.
Watch out
Campaign ID and Target URN are both needed, so they must come from earlier steps.
5

Find Conversation Messages

Search

In Zapier“This actions is used to find messages of a specific conversation.”

Fetches the messages of a given conversation, for a given account.

When to use it
copy the full thread into a CRM note when a lead turns into an opportunity.
Watch out
it needs both the Account ID and the Conversation URN; Find Conversations or Find Lead Conversation can provide the URN.
6

Find Lead Conversation

Search

In Zapier“This action is used to find the details of a specific lead conversation”

Finds the conversation tied to a specific lead, starting from the Lead ID.

When to use it
you know the lead but not the thread, and Send Message to Conversation needs that URN.
Watch out
the Account ID is required too, so run Find Accounts first if the Zap does not carry it.
7

Find Lead

Search

In Zapier“This actions is used to find details of a specific lead.”

Looks up the details of one lead from its Aimfox Lead ID.

When to use it
a label-based Zap needs the lead's profile before it creates a CRM contact.
Watch out
it works from the Aimfox Lead ID only; a LinkedIn profile URL will not do the job here.
8

Find Accounts

Search

In Zapier“This action is used to list all LinkedIn accounts of a specific Aimfox workspace.”

Lists every LinkedIn account in a workspace, with no other input than the workspace.

When to use it
get the right Account ID to send from, instead of copying it by hand.
Watch out
with several accounts in one workspace, decide which match to keep in the multiple-results setting.
9

Find Blacklisted Profiles

Search

In Zapier“This action is used to find all blacklisted profiles of an Aimfox workspace”

Returns the profiles currently on the workspace blacklist.

When to use it
audit the list against your customer base, before adding more names.
Watch out
it reads one workspace at a time, so an agency with several clients needs one search per workspace.
10

Find Blacklisted Companies

Search

In Zapier“This action is used to find all blacklisted companies of an Aimfox workspace.”

Returns the companies blocked in the workspace.

When to use it
make sure a partner is already excluded before a new campaign goes live.
Watch out
this list is separate from blocked profiles; check Find Blacklisted Profiles as well for a full picture.
11

Find Campaigns

Search

In Zapier“This action is used to find all campaigns of an Aimfox workspace.”

Lists all campaigns of a workspace, handy when an action asks for a Campaign ID.

When to use it
feed Remove Profile From Campaign with the ID of the right sequence.
Watch out
a busy workspace returns many campaigns, so set the multiple-results option to the behaviour you want.
12

Find Conversations

Search

In Zapier“This action is used to find all Aimfox conversations.”

Lists the Aimfox conversations of the workspace.

When to use it
find a Conversation URN when the trigger that started the Zap did not carry one.
Watch out
it covers the whole workspace; when you already know the lead, Find Lead Conversation is more precise.
13

Find Interactions

Search

In Zapier“This action is used to retrieve all interactions of a specific workspace.”

Retrieves all the interactions recorded in one Aimfox workspace.

When to use it
an activity digest built in a later step from what this search returns.
Watch out
it returns everything for the workspace, so a filter after it keeps only what the digest needs.
14

Find Recent Leads

Search

In Zapier“This action is used to list recent leads of a specific Aimfox workspace.”

Lists the latest leads of a workspace.

When to use it
hand a list of fresh leads to a scoring step before anyone reaches out.
Watch out
it is a lookup, not a trigger; it only runs when a Zap reaches it.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, an empty search stops the Zap and skips what depends on it. Switched on, the Zap carries on without a result.
  2. Create X if it doesn't exist yet?
    Turns a search into a find-or-create. Aimfox offers none, so this box does not appear on its searches.
  3. If multiple search results are found?
    Keep the first match (the default), stop the Zap, or pass every match on to the next steps.
When it breaks

When an Aimfox Zap breaks

Zapier links no help article to Aimfox, and no limit specific to the app is documented. What breaks is the usual Zapier behaviour, plus the IDs Aimfox asks for.

Four cases cover most surprises. If a Zap still fails after this, the Zapier troubleshooting page is the next stop.

  • Nothing from before the Zap

    A Zap only reacts to events after you switch it on. Replies, invites or views from last week are never picked up; moving that backlog is a separate job.

  • A Zap that sets itself off

    Listening for Lead Label Added while also running Add Label to Lead, or Message Sent while sending messages, can loop and burn through your task count fast.

  • A sudden flood of events

    A big import of leads or a mass campaign launch can send a huge batch at once, and Zapier's flood protection may hold part of it back.

  • Missing ID or URN

    Many actions want a Campaign ID, Account ID or URN. Mapping the wrong value, or none, makes the step fail; add a search step to fetch the real one.
Need help

Need help automating Aimfox with Zapier?

A person reads every message.

FAQ

Aimfox Zapier integration: frequent questions

01Is the Aimfox Zapier integration free?
Yes, you can start on Zapier's free plan. Aimfox is not a premium app, so it is not locked behind a paid plan. The free plan gives you 100 tasks a month and unlimited Zaps, but each Zap is limited to two steps: one trigger and one action. As soon as you add a filter, a search step or a second action, the Zap becomes multi-step and needs a paid plan.
02How many tasks does an Aimfox Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap that fires on Campaign Reply and adds a label uses one task per reply. Add a note on top and it becomes two per reply. Failed actions are not counted. Because Aimfox triggers like Lead Viewed or Connect Sent can fire often on an active account, the count climbs faster than people expect, so put a filter in front of costly actions.
03Do Aimfox triggers run in real time?
Yes. All 18 Aimfox triggers are instant: Aimfox tells Zapier the moment the event happens, so the Zap starts right away. The polling interval of each plan, 15 minutes on the free plan, does not apply here. That makes Aimfox a good fit for a free plan, where polling apps would otherwise wait between checks. In the editor, a Zap built on an instant trigger shows a lightning bolt. Nothing to tune on your side.
04What does it take to connect Aimfox to Zapier?
An Aimfox account, and access to the workspace the Zap will work on. In Zapier, open Apps, click + Add connection, search for Aimfox, click Add connection, then sign in to Aimfox in the new tab and grant access. Every Aimfox operation asks you to choose a Workspace, and several actions also want an Account ID or a URN, so check that your login sees the right workspace. If you work in several workspaces, the Zap only uses the one you pick.
05What is the difference between Message Reply, Campaign Reply and New Reply?
They cover different scopes. Message Reply fires only on the first reply to an Aimfox campaign message, the one that opens a conversation. Campaign Reply fires on replies to campaign messages. New Reply catches every reply on LinkedIn, campaigns or not. Pick one per goal: running two of them for the same purpose doubles the actions and the tasks. For a full log of both directions, Inbox Event is the widest option.
06What if the Aimfox operation you need is not listed?
Then Zapier cannot do it with this app today. The 47 visible operations (18 triggers, 15 actions, 14 searches) are the full list. Before giving up, check whether a search plus an existing action gets you there: many gaps close once you fetch an ID with a search step. If not, the same need can be checked on another automation platform. Keep in mind that a search step makes the Zap multi-step, so it needs a paid plan.
07Zapier, Make or n8n for Aimfox?
It depends on your criteria rather than on a winner. On Zapier, judge by three things: whether the 47 operations cover your scenario, how many tasks your volume will use, and whether two-step Zaps on the free plan are enough. Then apply the same criteria to the other platforms, looking at the operations they list for Aimfox and how they bill. The answer usually follows from your volume and from who will maintain the automations.
Same platform

Other docs you might need on this stack.

Browse all integrations