Aimfox
When to use this guide: Use this guide when configuring Aimfox with OutboundSync — confirming what syncs, creating the source, choosing events, and mapping contact lookup.
OutboundSync connects Aimfox to HubSpot and Salesforce as a one-way sync, logging social campaign activity to the matching contact or lead record with proper isolation between accounts.
Aimfox runs B2B social outreach across multiple sending accounts — built for agencies and teams managing several clients or reps in parallel. Each Aimfox event carries the sender, campaign, and timestamp metadata needed to associate activity with the right CRM record and to spot multi-account patterns in reporting.
What syncs into your CRM
Section titled “What syncs into your CRM”OutboundSync processes these Aimfox social outreach webhook events:
- Connection requests sent and connection acceptances
- Direct messages, message requests, and replies received
- Premium message sends and replies
- Profile views
- Lead label / category updates when Aimfox emits them
- Campaign IDs, names, and timestamps on each activity
- Sending account context for multi-account routing
OutboundSync does not process Aimfox campaign lifecycle events (created / started / ended) or account connected / disconnected signals, even if you enable them in Aimfox. Exact Aimfox UI labels and which overlapping events to enable are covered in Which Aimfox events to enable below.
Where it syncs
Section titled “Where it syncs”- HubSpot — direct integration
- Salesforce — direct integration
- Close — supported during the current Close beta
- Attio — supported during the current Attio beta
Combo-specific landing pages and field mappings for Aimfox are not yet published. The Aimfox integration page covers current capabilities.
Before you start
Section titled “Before you start”- An OutboundSync account — create your account if needed.
- HubSpot or Salesforce connected — HubSpot setup guide or Salesforce setup guide.
- Access to the Aimfox workspace Settings → Webhooks tab (Aimfox webhook help).
Aimfox does not require an OutboundSync API key for activity sync. The webhook URL alone delivers events. CRM-driven block list sync is not available for Aimfox yet.
Guided onboarding and customer success support remain available — contact support.
Create the Aimfox source in OutboundSync
Section titled “Create the Aimfox source in OutboundSync”- Sign in at app.outboundsync.com.
- Open Sources and create a new source.
- Choose Aimfox as the platform and select your connected CRM (HubSpot or Salesforce).
- Configure source settings as you would for other social platforms:
- Select owner — Salesforce or HubSpot user who owns newly created records. See Identifying OutboundSync activity in Salesforce when auditing Created By vs Owner.
- Activity object (Salesforce) — most teams use Tasks for per-event reporting granularity.
- Contact / lead lookup — Aimfox uses the same Object Lookup Method options as HeyReach (Default social profile, Alternative, or Optional Alternative). Map the social profile URL field OutboundSync should match on (standard social/LinkedIn URL field or a custom property). When HubSpot contacts often lack an enriched profile URL but Aimfox leads include email, prefer Optional Alternative Property — see Lookup method options for social sync. URL format normalization is covered in Handling social profile URLs for matching.
- Save the source and copy the source URL OutboundSync generates.
If CRM field or permission pickers are empty, or you see a session-expired error while saving, sign out of OutboundSync, sign back in, and reopen the source form so Salesforce session data reloads.
Add the webhook in Aimfox
Section titled “Add the webhook in Aimfox”- In Aimfox, open Workspace settings → Webhooks.
- Click Add webhook.
- Enter a clear Name (for example
OutboundSync — production). - Paste the OutboundSync webhook URL into URL.
- Leave Authentication Header blank unless your team has a custom requirement — OutboundSync sources authenticate via the unique URL.
- Select events using the guidance below, then Save.
Aimfox applies webhooks at the workspace level. One OutboundSync source URL is enough for that workspace’s campaign activity.
Which Aimfox events to enable
Section titled “Which Aimfox events to enable”OutboundSync processes Aimfox social activity for connections, messages, premium messages, replies, profile views, and labels. Aimfox’s UI lists several connection, reply, and inbox events that sound alike — pick one clear path for each instead of enabling every overlapping option.
Recommended core events
Section titled “Recommended core events”Enable these for a typical OutboundSync setup:
| Aimfox event (UI label) | Why enable it |
|---|---|
| Connect Sent | Connection requests your campaigns send |
| Connect Request Accepted | Acceptances that establish a new connection |
| Message Sent | Standard messages sent to prospects |
| Message Request Sent | Message requests when that channel is in use |
| Inmail Sent | Premium message sends |
| New Reply | Replies across conversations (not only the first reply) |
| Inmail Reply | Premium message replies when you send premium messages |
| Lead Label Added | Labels / categories your team applies in Aimfox |
| Lead Viewed | Profile views, when you want that activity in CRM |
Overlapping connection events (avoid doubles)
Section titled “Overlapping connection events (avoid doubles)”Aimfox exposes more than one acceptance-related trigger. Enabling both for the same acceptance can create duplicate CRM activities.
| Event | Behavior | Recommendation |
|---|---|---|
| Connect Request Accepted | Connection acceptance from your outreach | Prefer this for acceptance sync |
| New Connection | New connection established (often overlaps with acceptance) | Skip when Connect Request Accepted is enabled |
Overlapping reply and inbox events (avoid doubles)
Section titled “Overlapping reply and inbox events (avoid doubles)”Aimfox exposes multiple reply-related triggers. Enabling several of them for the same conversations can create duplicate CRM activities.
| Event | Behavior | Recommendation |
|---|---|---|
| New Reply | Catches replies broadly (not limited to the first reply) | Prefer this for reply sync |
| Message Reply | First reply only for a lead / conversation start | Skip when New Reply is enabled |
| Campaign Reply | Reply in an Aimfox campaign context | Skip when New Reply (or inbox campaign reply) already covers it |
| Inbox Event | Broad inbox activity (sends and receives; type field distinguishes direction) | Optional catch-all. If you enable it and discrete Message Sent / New Reply events, watch for duplicates after go-live and trim if the same touch lands twice |
Practical rule: start with the recommended core table. Add Inbox Event only if you need a broader catch-all and are willing to review logs for duplicates. If live campaigns show the same reply twice in Salesforce or HubSpot, remove the overlapping reply/inbox options and keep New Reply (plus Inmail Reply when you use premium messages).
Skip — not synced by OutboundSync today
Section titled “Skip — not synced by OutboundSync today”These Aimfox events do not create CRM activities in OutboundSync, even if you enable them in Aimfox:
- Campaign Created
- Campaign Started
- Campaign Ended
- Account Connected
- Account Disconnected
Verify the connection
Section titled “Verify the connection”- In OutboundSync, open the Aimfox source and use Sending test webhook payloads to push a sample event.
- Confirm the test lands on the expected contact or lead, with the social profile match you configured.
- After live Aimfox campaigns start, check OutboundSync logs if expected activity is missing or duplicated.
Scope and current limitations
Section titled “Scope and current limitations”- One-way sync. Data flows Aimfox → CRM. Updates in HubSpot or Salesforce are not written back to Aimfox.
- Social channel only. Email and phone are out of scope.
- Beta. The integration is live as a direct Beta.
- One source URL per OutboundSync source. Do not reuse the same OutboundSync URL for unrelated Aimfox experiments if you need separate CRM routing.
- No Aimfox API key required for webhook activity sync.
- No CRM → Aimfox block list sync in OutboundSync today. Maintain Aimfox blacklists in Aimfox until product support lands.
- Event taxonomy may evolve. Aimfox can rename or add overlapping UI labels. If a label in your workspace differs slightly from this table, match on the description Aimfox shows next to the event (first reply vs every reply, inbox vs campaign).
