Avionté

Integrate Alex with Avionté BOLD

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.

How it works

Once Avionté has enabled the integration for your tenant and your Alex account team has linked it, this is the typical path:

1. A job is created in Avionté BOLD. Alex imports it and runs your job workflow, generating an interview from the job title and description.
2. Talent applies, is added to a pipeline, or moves stage in Avionté. Alex creates the candidate (name, email, phone, resume) and runs your application workflow — usually an interview invite by email or SMS.
3. The candidate completes the Alex interview. Your workflow can upload the interview report PDF to the talent record, add the talent to a pipeline stage, and update talent fields.
4. A recruiter records a decision in Alex. If ATS Sync mappings exist, Alex moves the talent to the mapped Avionté pipeline stage.

What the Integration Reads from Avionté

Events Alex responds to

Avionté event	What Alex does
Talent applied for a job	Reads the talent’s name, email, and phone, creates the candidate in Alex, and starts your application workflow (for example, an interview invite by email or SMS). Talent without a name or email are skipped.
Talent added to a pipeline	Starts your application workflow, optionally only for the pipeline stages you choose.
Talent pipeline updated	Starts your application workflow, optionally only for the pipeline stages you choose.
Talent stage updated	Starts your application workflow, optionally only for the stages you choose, and keeps the candidate’s status in Alex in step with Avionté where an ATS Sync mapping exists.
Job created	Imports the job and runs your job workflow, generating an interview from the job title and description. Requires a job workflow to be configured in Alex.
Job updated	Updates the job’s owner, title, description, and status in Alex where job field mappings are configured.

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é

Write	How it’s triggered
Add talent to a pipeline stage	The Add Talent To Pipeline Stage workflow action, or automatically when a recruiter records an interview decision in Alex and a matching ATS Sync mapping exists.
Update a talent field	The Update Talent Field workflow action. Supported fields: first, middle, and last name; primary and secondary email; mobile, home, and work phone; and referred by. The value can be fixed text or extracted from the interview transcript.
Upload a document to the talent	The Upload Talent Attachment workflow action. The document can be the Alex interview report PDF, the candidate’s resume, or the identity verification report.

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 (Candidate Owner (ATS)).

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

No Avionté credentials are entered in Alex by your team. Avionté enables the integration on their side; Alex links the tenant.

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. Use Avionté support. Avionté enables the integration and its events for your tenant.
3. Tell your Alex account team once Avionté confirms the connection. They link your Avionté front-office tenant to your Alex company.
4. In Alex, go to Settings → Integrations → Connect your ATS and select Avionté. Your account team verifies the connection from there.

The Avionté card in Settings does not take an API key. If the page still asks you to submit an Avionté ticket after your account team has linked the tenant, contact [e-mail].

Configure ATS Sync

ATS Sync is how interview decisions and job fields stay aligned between Alex and Avionté. Avionté supports both Interview Sync and Job Sync through the direct integration (not Kombo). Full reference: ATS Sync.

1. In Alex, go to Settings → ATS Sync.
2. On Interview Sync, map each Alex decision (Accepted, Rejected, Placed, Submitted, Hired, and so on) to one or more Avionté pipeline stages.
3. If a decision maps to more than one stage, star the default value — that is the stage Alex writes when a recruiter records the decision in Alex.

4. Set sync direction per mapping:
   • Inward (Avionté → Alex): a stage change in Avionté updates the interview decision in Alex.
   • Outward (Alex → Avionté): a decision in Alex adds the talent to the mapped pipeline stage.
   • Two-way: both.
5. On Job Sync, map Avionté job status values to Active / Inactive, and optionally sync job owner, title, and description into Alex.

Hired and Started in Avionté often have no webhook. The 15-minute stage poll is what brings those moves into Alex — Interview Sync still needs a mapping for the hired/started stage.

Configure workflows

Workflows are where you choose which Avionté events start an interview and what Alex writes back. Open Workflows in Alex after the tenant is linked.

Job workflow

1. Open your job workflow and add the New Job from ATS trigger. Avionté delivers new jobs over its own events — do not use New Job from ATS (Webhook) for Avionté.

2. Optionally add Filter by Job so only the jobs you want generate interviews. Standard fields:

   Field	Type
   Title, Description, Status, Job Type	text
   City, State, Postal Code	text
   Pay Rate, Bill Rate	number
   Start Date, End Date	date
   Job custom details	text, number, date, or Yes/No, matching the field in Avionté

3. Add Configure Job and generate the interview from the Avionté title and description.

Application workflow

Add one or more Avionté triggers, depending on when you want Alex to invite talent:

Trigger	Fires when
New Application	Talent applied for a job in Avionté. The job in Alex must use a workflow that includes this trigger.
Pipeline Talent Added	Talent is added to a job pipeline.
Pipeline Talent Updated	Talent’s pipeline assignment is updated.
Talent Stage Updated	Talent’s stage changes.

On the three pipeline/stage triggers, set Target stages if the workflow should run only for certain Avionté stages. Leave it empty to run on every stage change.

A typical application workflow:

1. New Application (and/or a stage trigger) → Filter by Job if you want to limit which jobs invite.
2. Invite the candidate by email or SMS.
3. On Interview Completed, add Avionté write-backs from the Actions palette:

• Add Talent To Pipeline Stage — pick the pipeline stage from your tenant’s catalog.
• Update Talent Field — write first/middle/last name, primary or secondary email, mobile/home/work phone, or referred by.
• Upload Talent Attachment — attach the Alex interview report PDF (or the resume / identity verification report) to the talent record. Set the destination file name; you can also set an optional Avionté document type.

4. Optionally Send Email to Candidate Owner (ATS) — the talent’s Avionté representative.

Talent without a first name, last name, or email are skipped and never invited. The job must already exist in Alex (from the job workflow) before an application for it will run.

Test the integration

Use a test job and test talent in Avionté BOLD before going live.

1. Create a test job in Avionté. Confirm it appears in Alex and that an interview was generated.
2. Apply a test talent (with name and email) to that job, or add them to a pipeline stage your workflow targets.
3. Confirm the candidate is created in Alex and the invite is sent.
4. Complete the interview. Confirm the report PDF is on the talent record and the talent is in the configured pipeline stage.
5. Record a decision in Alex. Confirm ATS Sync moved the talent to the mapped stage.
6. In Avionté, move the talent to a hired or started stage. Within about 15 minutes, the decision in Alex should update if Interview Sync is mapped.

Troubleshooting

Symptom	Likely cause
Jobs not importing	No job workflow with New Job from ATS, or Avionté has not enabled JOB_CREATED events for the tenant.
Applicants not invited	The job’s application workflow has no New Application trigger; the talent is missing name or email; or a pipeline/stage trigger’s Target stages list excludes this stage.
Report PDF missing on the talent	No Upload Talent Attachment node on Interview Completed, or the interview has no report yet.
Stage in Avionté does not change after a decision in Alex	Interview Sync has no outward mapping for that decision, or no default (starred) stage when multiple values are mapped.
Hired / Started in Avionté does not show in Alex	No Interview Sync mapping for that stage. Wait for the 15-minute poll after adding one.
Settings still says to file an Avionté ticket	The front-office tenant is not linked to the Alex company — ask your Alex account 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.

Timeline	Players Involved	Task Description
Day 1	Alex account team, customer project lead	Kickoff: Align on goals, scope, jobs and pipelines in scope, and timeline. Identify stakeholders on each side.
Day 1–3	Customer Avionté admin, Avionté support	API access: Confirm the API subscription and MOU; submit the Avionté ticket to connect the account to Alex.
Day 3–5	Alex implementation team	Connection: Link the Avionté tenant to the Alex company and verify the connection.
Day 5–7	Alex implementation team, customer recruiting lead	Configuration: Map Avionté stages and job fields in ATS Sync; build the job and application workflows, interview templates, and write-back actions.
Day 7–9	Alex implementation team, customer recruiting lead	Testing: Create a test job and test applicant in Avionté; confirm the interview invite, the report upload, and the stage move.
Day 10	Alex customer success, customer recruiters	Training and go-live: Train recruiters on reviewing interview results and recording decisions; switch the workflows on for live jobs.
Day 11–30	Alex customer success	Post-go-live support: Weekly check-ins, monitoring, and workflow adjustments.

Support and escalation: Contact your Alex account team or [e-mail]. 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 20, 2026