Skip to main content

​
Overview

The Alex × Avionté integration connects your Avionté BOLD front office to Alex. Avionté sends Alex events as jobs and talent change; Alex reads the records it needs, runs your Alex workflows — inviting applicants to AI interviews, screening, and scoring — and writes results back to the talent record.
Avionté+ Certified IntegrationAvionté+ Certified Integration

​
What the Integration Reads from Avionté

​
Events Alex responds to

Alex also checks the stage of each in-process talent every 15 minutes, so that a move to a hired or started stage in Avionté is reflected in Alex even though Avionté sends no event for it.

​
Records Alex reads

  • Jobs — title, description, client company name, owner, entered-by and sales-rep users, status, and job custom fields.
  • Talent — name, email addresses, phone numbers, and representative. Workflow custom variables can read other standard talent fields; EEO and tax fields are never read.
  • Talent documents — the talent’s resume (PDF, DOCX, DOC, or TXT), used to screen and interview the candidate.
  • Users — name and email, to identify a job’s owner and a talent’s representative.
  • Reference lists — job activity (stage) types, job statuses, and job custom field definitions, used to populate settings and workflow dropdowns in Alex.

​
What the Integration Writes to Avionté

Alex workflows can also filter on Avionté job fields (Filter by Job, including job custom fields) and send email to or from a talent’s Avionté representative.

​
Not Supported

The following are out of scope for this revision:
  • Creating talent, jobs, or placements in Avionté.
  • Writing activities or notes to a talent.
  • Writing job status, or any job field, to Avionté.
  • Writing custom fields on talent or jobs.
  • Reading placements, branches, or talent custom field definitions.
  • Searching Avionté for existing talent by email.

​
Setup

  1. Confirm your Avionté BOLD contract includes an API subscription and that an MOU is in place (see the disclaimers below).
  2. Submit a ticket to Avionté asking them to connect your Avionté account to Alex. Avionté enables the integration and its events for your tenant.
  3. Your Alex account team links your Avionté tenant to your Alex company and verifies the connection in Settings → Integrations.
No Avionté credentials are entered in Alex by your team.

​
Standard Operating Procedure

The timeline below is typical. The actual timeline depends on how many resources and how much time your team can commit to the integration and onboarding.
Support and escalation: Contact your Alex account team or [email protected]. Issues with your Avionté API subscription, MOU, or tenant access go to Avionté support. To turn the integration off, notify both Alex and Avionté BOLD.

​
Disclaimers

MOU disclaimer. To utilize this integration, you need an API subscription as part of your Avionté BOLD contract. Additionally, a Memorandum of Understanding (MOU) is required, which serves as a reminder of current Avionté BOLD terms and conditions. Since there are no marketplace tiles or UI changes, and it operates through hidden APIs to perform its tasks, users won’t be able to see the integration is directly working. Since a user can’t see if the integration is on, and Avionté BOLD is not part of your agreement with the third-party, it is up to you, the client, to notify Avionté BOLD when the integration should be turned off.
API subscription and usage disclaimer. Only the functionality and data access explicitly documented herein are supported. Any capability not expressly shown here does not exist, is out of scope, and is unavailable, even if previously discussed verbally or implied. Customers and Integrators should treat this document as the single source of truth for the Alex × Avionté integration. Capabilities added in the future will be reflected by an updated revision of this document; the current revision date is stamped below.Current revision: October 7, 2026