AxiaForce

Integrations

Works with your stack. Writes back to it.

AxiaForce runs alongside the stack you already pay for.

  • Your CRM, ATS, email, calendar, ERP, documents, repos and website stay the systems of record
  • AI employees act through adapters, with only the scopes you grant
  • Every write-back carries the work-object id — so every action is traceable
CRM
two-way
SalesforceHubSpotZoho CRMAttioPipedrive
ATS
two-way
Zoho RecruitGreenhouseLeverBullhornAshbyLinkedIn Recruiter (RSC)
Email
send + read
Outlook / M365GmailSMTP
Calendar & scheduling
two-way
Microsoft 365Google CalendarMicrosoft BookingsCalendlyCal.com
Comms
two-way
TeamsSlackTwilio SMS / voice
Enrichment
read
ZoomInfoClayApolloLinkedIn (compliant)Clearbit
Assessments
assign + results
Language proficiency (CEFR)Competency & skills testsTechnical screensCustom assessments
ERP & finance
read/write
NetSuiteSAPDynamics 365QuickBooks
Document storage
read/write
SharePoint / OneDriveGoogle DriveBoxDropbox
Code & CI/CD
read · gated write
GitHubGitLabGitHub ActionsVercel
Cloud & observability
read · gated write
AWSAzureSentryDatadogPagerDutyJiraLinear
Marketing & social
publish · listen
LinkedIn PagesInstagramFacebookTikTokXReddit
Website / CMS
read/write
WordPressWebflowNext.js sites
Analytics
emit
PostHogGA4Segment
Workflow
trigger
Zapiern8nMakeWebhooks
Data & APIs
read/write
PostgresSupabaseSnowflakeBigQueryREST / MCP

Marks and names are trademarks of their respective owners, shown to indicate compatibility only; no endorsement implied.

Examples by category · the launch list is confirmed per customer during onboarding

How an adapter works

Four steps, the same for every system.

Every adapter implements the same contract.

  • Custom adapters stay just as straightforward
  • Same security story whether it's Salesforce or an internal tool
01

Authorise

You connect a system and see the exact scopes the workflow needs before you grant them. Nothing broader is requested.

02

Read

Workers read what a work object needs — a contact, a candidate, a calendar — at run time. No bulk copy of your data into a second system.

03

Act

Gated actions wait for approval. Everything else runs within policy: send windows, rate limits, recipient rules.

04

Write back & log

Activity, stage changes and outcomes are written to the system of record. The same event lands in the ledger with the work-object id.

Custom adapters

Anything with an API or an MCP server.

Internal tools, legacy systems, a vendor nobody has heard of.

  • Declares its capabilities and scopes against the same contract
  • The platform treats it exactly like a first-party adapter
  • Including in the ledger — same evidence, same trail
adapter manifest · example
adapter: internal-ats
kind: ats
auth: oauth2            # or api-key, mcp
scopes:
  - candidates:read
  - candidates:stage:write
  - notes:write
capabilities:
  read.candidate:   GET /v2/candidates/{id}
  write.stage:      POST /v2/candidates/{id}/stage
  write.note:       POST /v2/candidates/{id}/notes
ledger:
  correlate_by: work_object_id
  emit: [read, write, error]
limits:
  rate: 60/min
  window: recipient_local 08:00-18:00

Have a system we didn't list?

Tell us what it is. If it has an API, we'll show you the adapter on the call.