Aimfox MCP integration for AI agents.
Connect AI agents to Aimfox through 11 structured actions, including get campaign, add profile to campaign, and remove profile from campaign. Review authenti…
- ACTION CONTRACTS
- 11
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Aimfox integration exposes
The Aimfox Agent App exposes 11 provider-backed actions for marketing and communication work. Its current contract lets an authorized agent fetch one aimfox campaign by campaign id, add one linkedin profile url to an aimfox campaign audience, and remove one linkedin profile from an aimfox campaign audience by urn or public id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Aimfox account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Aimfox capabilities.
Showing 11 of 11 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_campaignREADFetch one Aimfox campaign by campaign ID.
INPUTS: campaign_id
add_profile_to_campaignWRITEAdd one LinkedIn profile URL to an Aimfox campaign audience.
INPUTS: campaign_id / profile_url
remove_profile_from_campaignHIGH IMPACTRemove one LinkedIn profile from an Aimfox campaign audience by URN or public ID.
INPUTS: campaign_id / urn
get_campaign_metricsREADFetch interaction metrics for one Aimfox campaign.
INPUTS: campaign_id
get_leadREADFetch one Aimfox lead by lead ID.
INPUTS: lead_id
get_total_leads_countREADCount Aimfox leads that match the documented lead search filters.
INPUTS: keywords / current_companies / past_companies / education / interests
list_campaignsREADList Aimfox campaigns, optionally filtering by outreach type or profile inserts.
INPUTS: outreach_type / accepts_profiles
list_interactionsREADList Aimfox interaction buckets for a timestamp range.
INPUTS: bucket / from / to / account_ids / campaign_id
list_recent_leadsREADList recent Aimfox lead transition events for the workspace.
list_workspace_labelsREADList labels configured in the Aimfox workspace.
search_leadsREADSearch Aimfox leads with documented facet filters and offset pagination.
INPUTS: keywords / current_companies / past_companies / education / interests
INPUT CONTRACTS
Know what the action needs before it runs.
get_campaign
campaign_idREQUIRED- The Aimfox campaign ID.
add_profile_to_campaign
campaign_idREQUIRED- The Aimfox campaign ID.
profile_urlREQUIRED- The LinkedIn profile URL to add to the campaign audience.
remove_profile_from_campaign
campaign_idREQUIRED- The Aimfox campaign ID.
urnREQUIRED- The LinkedIn profile URN or public identifier to remove.
get_campaign_metrics
campaign_idREQUIRED- The Aimfox campaign ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Campaign
Fetch one Aimfox campaign by campaign ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_campaignControl Add Profile To Campaign
Add one LinkedIn profile URL to an Aimfox campaign audience. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_profile_to_campaignVerify with Get Campaign Metrics
Fetch interaction metrics for one Aimfox campaign. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_campaign_metricsSAFETY BOUNDARY
Operate Aimfox with explicit limits
- Authorize Aimfox with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `remove_profile_from_campaign` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Aimfox rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Aimfox task completed successfully.
CONNECTION MODEL
API key
Aimfox API key sent with the Authorization Bearer header. Create it from Workspace Settings > Integrations in your Aimfox dashboard: https://docs.aimfox.com/.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 9
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Aimfox.