Aimfox
Sales OutreachRun LinkedIn outreach campaigns through Aimfox, covering audiences, connected accounts, sending limits, leads, labels, templates, and the unified inbox. Agents build target lists, launch sequences, and route replies to the right owner.
What This Integration Enables
Aimfox is built for teams where the sending account belongs to a named person. That is the fact the whole connector organizes around. Weekly interaction limits are not a hidden safety setting here, they are readable and writable values on each connected LinkedIn account, alongside a warm-up flag, and Aimfox publishes its own recommended range for them. FlowRunner agents can therefore treat capacity as a first-class input: read the ceiling, read the week's actual interactions, and load an audience that fits inside what is left rather than discovering the ceiling by hitting it.
Around that core, agents get the full working surface of a LinkedIn outreach workspace through FlowRunner connectors. They create and pause campaigns, load audiences with per-profile custom variables so the sequence can personalize, search and label leads, work the unified inbox, and maintain a workspace-wide blacklist that every campaign audience respects. The realtime event stream carries acceptances, replies, label changes and account session changes, so a flow can react the moment a connection is accepted instead of polling for it. What FlowRunner adds on top is the thesis the platform is built on: agents do the volume, and the decisions that put a real person's account at risk stop and wait for that person.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Capacity-aware audience loading
A sourcing flow assembles target profiles from a saved search and hands them to the outreach agent. Before touching a campaign, the agent calls List Accounts to see which LinkedIn accounts are connected, Get Account Limits for each one, and List Interactions for the current week to see how much of each ceiling has already been consumed. It filters the batch against List Blacklisted Profiles, then splits the remainder across accounts using Add Profiles With Custom Variables so no single account is loaded beyond its configured weekly allowance. The leftovers are reported rather than forced in. Volume becomes a function of capacity instead of a function of whatever the sourcing run happened to return.
Acceptance to CRM, in real time
The On Aimfox Event trigger fires when a connection request is accepted. The agent calls Get Lead to pull the full stored record, writes the contact and the accepting account into HubSpot, applies a workspace label with Add Label To Lead so the segment is queryable later, and posts a short note into Slack for the rep who owns the account. The rep sees a warm connection, not a nightly export.
Honoring an opt-out captured somewhere else
Someone replies to a marketing email asking never to be contacted again, or a rep marks a record do-not-contact in the CRM. A flow picks up that signal, calls Remove Profile From Campaign so no further steps run against the person, then Add Profiles To Blacklist so no future campaign can pick them up either. It writes the reason onto the lead with Create Lead Note, so the next person who searches that lead can see why it is suppressed rather than guessing. The opt-out propagates from wherever it was captured into the system that would otherwise have kept sending.
Human-in-Loop Highlight
Set Account Limits is the action that decides how hard a real employee's LinkedIn account gets pushed. The field accepts anything from 1 to 1000 weekly connection requests, while Aimfox itself recommends staying between 50 and 200 for healthy sending, and the consequence of getting it wrong does not land on a server. It lands on the person whose name, network and job history are attached to that account. So the agent never writes that value on its own initiative. When a campaign backs up because capacity is short, the agent gathers the evidence and asks the account owner directly: "Rachel, the ANZ campaign has 180 profiles queued and your account is at its 100 per week connection ceiling with 6 remaining. Raise the weekly limit to 140, or hold the queue for next week?" Rachel answers, because it is her account. The human-in-the-loop step is not ceremony here, it is the only place in the workflow where the risk and the authority sit with the same person.
Agent Capabilities
31 actionsWorkspace and Sending Accounts
4- List Workspaces Returns every workspace the configured key can reach, with seat and licence counts, member count, subscription state and the caller's role. Requires an Aimfox Master API key rather than a workspace key, so agencies running several client workspaces use this as the entry point.
- List Accounts Returns every LinkedIn account connected to the workspace with its numeric id, public identifier, name, occupation and premium flag. The numeric id is what the limit and conversation actions expect, so most account-aware flows start here.
- Get Account Limits Reads the weekly interaction ceilings configured for one LinkedIn account, covering connection requests, email-verified connection requests and InMails, plus the warm-up setting. Read this before increasing volume so a sending account is not pushed past a safe ceiling.
- Set Account Limits Writes new weekly interaction ceilings for a LinkedIn account. Omitted limits keep their current value. This is the action that changes how hard a named person's account is worked, which is why it belongs behind a human decision rather than inside an automatic ramp.
Campaigns
6- List Campaigns Returns every campaign in the workspace with its state, target count, campaign type, outreach type, owning accounts and labels. Filters narrow to inbound versus outbound campaigns or to campaigns that still accept new profiles.
- Create Campaign Creates a campaign shell. Only the outreach type is required, and it decides the shape of the campaign: connection requests, InMails, or an inbound drip to existing first-degree connections. The audience, schedule and message flows are still configured in the Aimfox dashboard, so this is the programmatic half of a two-step setup.
- Get Campaign Retrieves one campaign in full, including its weekly sending schedule with per-day intervals and timezone, audience and target counts, completion ratio, owning accounts, custom variable keys and the message flows attached to it. Used to audit exactly what a campaign will do before adding people to it.
- Update Campaign Changes a campaign's name, run state or audience exclusion rules. Setting the state to Active resumes sending and Paused halts it. Used to pull the brake on a sequence when an upstream signal says the timing is wrong.
- Delete Campaign Permanently removes a campaign, its audience and its scheduled steps. Conversations with leads already contacted survive, but the campaign does not, and the action cannot be undone. Prefer pausing when the stop is temporary.
- Get Campaign Metrics Returns lifetime counters for one campaign covering connection requests sent and accepted, messages, replies, InMails, endorsements, profile views and post likes. Used to compute acceptance and reply rates for a single sequence without exporting anything.
Campaign Audience
4- Get Campaign Audience Returns the profiles currently loaded into a campaign with each one's state in the sequence. This is how an agent audits who a campaign will actually contact before it starts running.
- Add Profile To Campaign Adds one LinkedIn profile to a campaign audience by public profile URL. Rejections come back with a reason, including profiles that are blocked, already connected or locked into another campaign, which makes this a usable single-lead bridge from a form fill or a CRM stage change.
- Add Profiles With Custom Variables Adds several profiles in one call, attaching a custom variable map to each so the sequence can personalize per recipient. The response separates the profiles that loaded from a failed list carrying the reason for each rejection, so a flow can act on partial success rather than treating the batch as all or nothing.
- Remove Profile From Campaign Removes a profile from a campaign audience so no further steps run against it. Used the moment an upstream system says the person is no longer a valid target, for example when a deal is won or a support escalation opens.
Leads and Labels
8- Search Leads Searches every lead in the workspace across keywords, current and past companies, education, interests, labels, languages, locations, campaign origins and skills. Returns lead ids, labels, notes and originating campaigns, which makes it the natural dedup check before enrolling someone new.
- Get Lead Retrieves the complete stored record for one lead, including industry, occupation, location and full work experience history. Used to enrich a CRM record the moment a connection is accepted.
- Create Lead Note Attaches a free-text note to a lead so context gathered elsewhere travels with the record inside Aimfox. Used to write a disqualification reason, a call summary or a suppression rationale where the next person will actually see it.
- Add Label To Lead Applies an existing workspace label to a lead. Labels are how leads are segmented for later search and reporting, and applying one emits a workspace event that a listening flow can act on.
- Remove Label From Lead Detaches a label from a lead while leaving the label itself available for other leads. Used when a lead moves between segments.
- List Labels Returns every label defined in the workspace with its colour and the number of leads carrying it. Label ids are required by the labelling actions and by the label filter on Search Leads.
- Create Label Creates a new workspace label so segmentation can be applied consistently from a flow rather than by hand in the dashboard.
- List Recent Leads Returns the most recent lead transitions in the workspace, each carrying the campaign and flow that produced it and the transition type such as accepted or replied. Useful as a lightweight activity feed for teams that would rather poll on a schedule than receive realtime events.
Inbox
5- List Conversations Returns LinkedIn conversations across the workspace inbox with unread counts, connection state and the full last message. Filters narrow to specific campaigns, unread threads only, or Aimfox campaign conversations only, which is how a triage flow gets a clean work queue.
- Start Conversation Opens a new LinkedIn conversation from a workspace account and sends the first message. Supplying several recipients creates a single group thread rather than separate ones, which is worth knowing before an agent iterates a list.
- Send Message Sends a message into an existing conversation from a specific workspace account. Used to deliver a reply that a person has already approved, attributed to the right sender.
- Mark Conversation Read Clears the unread badge on a conversation for a given account. Used at the end of a triage flow so the same thread is not processed twice.
- List Templates Returns every message template in the workspace with its body text, AI flag and usage statistics covering messages sent, replies received and connections accepted. Used to compare template performance without leaving the flow.
Suppression
3- List Blacklisted Profiles Returns the profiles on the workspace blacklist, which are excluded from every campaign audience. Read this before loading an audience so suppressed people never enter a sequence.
- Add Profiles To Blacklist Adds one or more profiles to the workspace blacklist by profile URL, stopping every campaign from targeting them. This is how an opt-out captured in email, in the CRM or in a phone call becomes enforceable inside Aimfox.
- Remove Profile From Blacklist Lifts the blacklist on a single profile so campaigns may target it again. Used when a suppression turns out to have been applied to the wrong record.
Reporting
1- List Interactions Returns time-bucketed interaction counters for the workspace covering connections sent and accepted, messages, InMails, replies, profile views, likes and endorsements, grouped hourly or daily and optionally narrowed to specific accounts or one campaign. This is what turns a configured weekly ceiling into a live capacity number.
Triggers
1 triggersEvent Triggers
1- On Aimfox Event Fires when a chosen workspace event occurs, including a connection request accepted, a campaign reply, a lead labelled, a campaign started or ended, and an account session change. Aimfox registers a webhook on the workspace and delivers each event as it happens, retrying failed deliveries with exponential backoff. Every payload carries an event id, the event type, workspace details and an event object whose shape depends on the type, so one trigger can drive several branches. Use it to push acceptances into a CRM the moment they happen, to route replies to the owning rep, or to raise an alert when a sending account loses its session mid-campaign.
Frequently Asked Questions
What can FlowRunner do with Aimfox?
FlowRunner agents can run List Workspaces, List Accounts, and Get Account Limits in Aimfox, plus 28 more actions.
Does connecting Aimfox to FlowRunner require OAuth?
No. Aimfox connects to FlowRunner with an API key, no OAuth flow required.
Can Aimfox trigger a FlowRunner workflow automatically?
Yes. Aimfox supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with Aimfox
$100 in credits. No card required. Connect in minutes.