Aimfox

The Corma and Aimfox integration shows IT who works in your Aimfox workspaces, in which role, and how many Outreach seats you pay for. Aimfox is LinkedIn automation software that helps users grow and manage their LinkedIn network, through outreach campaigns run from connected LinkedIn accounts. Its model mixes company and personal assets: the workspace runs campaigns for the company, while a connected account can be a rep's own LinkedIn profile.

Key takeaways

• Aimfox bills per Outreach seat, and each seat lets one connected LinkedIn account run campaigns at a time.
• Adding Aimfox teammates is free and member seats are unlimited, so the number of people in a workspace is not capped by the bill.
• A LinkedIn account connected to an Aimfox workspace is available to every workspace member in Campaigns, Leads and Unibox.
• Aimfox's terms make the customer solely responsible for complying with LinkedIn's rules and guidelines.

Who controls a LinkedIn profile once it is in Aimfox?

In Aimfox, people and LinkedIn accounts are separate. A connected account is available to every workspace member, and removing a member cuts their access immediately while workspace data and campaigns remain unaffected. Aimfox does not say what happens to the LinkedIn account a removed member connected, and deleting a LinkedIn account from the workspace also deletes every campaign tied to it. Offboarding a rep therefore needs an explicit decision about their profile and its campaigns, not just about a login.

Ownership and credentials need the same care. The Owner role cannot be transferred, and billing stays tied to the owner's email address. Aimfox API keys never expire, and there is no limit to how many can be created. Finally, LinkedIn's User Agreement prohibits bots and other unauthorized automated methods to add contacts or send messages, so which profiles run campaigns is a decision the company should make and record.

How Corma governs Aimfox

• Members and roles in review: Corma keeps track of who has Aimfox access and in which role, Owner, Admin or Member, and brings that access into automated access reviews.
• Approved before access: reps request Aimfox through the self-service app store, and a manager approves, so every Aimfox access has an approval on record.
• Leavers with a handover: a leaver workflow in the IT workflow builder removes the person's Aimfox access and asks the workspace owner what happens to the profile they connected and its campaigns.
• Seats and spend: Outreach seats and their monthly cost sit in SaaS subscription management, next to your other subscriptions and renewals.

Frequently asked questions

Does Aimfox support SSO or SCIM?

Aimfox's help center does not document SSO or SCIM. Teammates are invited by email, and only company-domain addresses are accepted. Where no API covers a step, Corma's browser-based agents carry it out in the Aimfox interface, in an isolated browser session.

Do Aimfox teammates cost extra?

No. Adding teammates is free and member seats are unlimited. You pay for Outreach seats, each running campaigns from one LinkedIn account at a time, so the figure to follow is seats in use against active campaigns, a core part of software license management.

Where is Corma data hosted?

Corma runs on AWS, with web servers and databases in data centers inside the European Union. Data is encrypted in transit and at rest, and Corma is ISO/IEC 27001:2022 certified.

Want to know which LinkedIn profiles run campaigns for your company? Book a Corma demo.