JobAdder AI integration · Early access
Put AI agents to work on your JobAdder records
This page explains how that works so your JobAdder administrator can judge the integration before anyone relies on it. The records enabled for your account are agreed with you during early access.
In short
FluxHire puts AI agents to work on your JobAdder records. Its sync is built for candidates, contacts, companies, jobs, job applications, placements and notes, confirmed for your account during onboarding. Consultants send the people the agents research into JobAdder, and field write-back is set up with your administrator during onboarding.
Teal marks a decision your team makes.
- Built to sync
- Candidates, contacts, companies, jobs, job applications, placements and notes.
- Your consultant decides
- The consultant picks who is imported, and whether each person becomes a contact or a candidate.
- Set up at onboarding
- Write-back is set up with your administrator during onboarding and controlled centrally, not per user.
- Last reviewed
- 19 October 2026
01What syncs
What comes across from JobAdder
FluxHire works from a synced copy of your JobAdder records, and also has a native integration with Jobli.
Built to sync
Candidates
With their activities and attachments.
Contacts
Companies
Jobs
Job applications
Placements
Notes
On each of these record types, collected on a schedule.
Confirmed during onboarding
The sync is built for all of these record types. Which ones are switched on for your account is confirmed during onboarding.
Syncing JobAdder user tasks is being developed.
02How updates arrive
How updates reach FluxHire
Changes in JobAdder reach FluxHire through webhook events and a scheduled catch-up sync.
Webhook events
When a record is updated or changes status, JobAdder sends a webhook event, and FluxHire processes it as it arrives.
Scheduled catch-up
A scheduled catch-up sync also runs, collecting new records and anything a webhook missed. Notes are collected on a schedule too. Records that have not changed are skipped.
Deleted records are marked, not erased
When someone deletes a record in JobAdder, FluxHire marks it as deleted at the next daily check instead of erasing it, retaining a deletion marker for review. This does not promise a restoration workflow.
A deliberately paced first import
The first import is deliberately paced to avoid overloading JobAdder’s API, which means a long history can take some time to arrive in full.
03What goes back
JobAdder stays your system of record
AI agents find the people, your consultants decide who goes into JobAdder, and field write-back is set up with your administrator during onboarding, with checks that protect your data.
Today
AI-researched people, straight into JobAdder
AI research
Contact Finder researches hiring contacts and target companies through the FluxHire Neural Engine and FluxHire Talent Signal.
Your consultant decides
The consultant picks who is imported, and whether each person becomes a contact or a candidate.
In JobAdder
They appear in JobAdder as the record type the consultant chose.
Consultants check researched details before import, because sources can be incomplete or out of date.
Set up at onboarding
Write-back built to protect your data
Once write-back is set up, an edit to a supported field goes back to JobAdder with five safeguards.
Write-back is set up with your administrator during onboarding and controlled centrally, not per user.
Only what changed
Only the edited field changes. FluxHire merges it into JobAdder’s current record, so every other value stays as JobAdder holds it.
Stops before overwriting
FluxHire reads JobAdder first. If someone changed that field in the meantime, the write stops instead of overwriting their edit.
Confirmed, not assumed
A queued change is pending. After writing, FluxHire reads the record again and records confirmation only when JobAdder holds the expected value.
Scoped to the fields that matter
Names and contact details on candidates and contacts, a candidate’s current role and salary expectations, a contact’s job title, company names, job titles and descriptions, and application rating. Everything else stays read-only in FluxHire.
Failures stay visible
Retryable failures remain pending while the sync retries. Conflicts and exhausted retries require review; a queued or retried change is not confirmed delivery.
04The AI
What the AI does with your JobAdder data
Once your records have synced, the suggestion engine and the assistant work on them inside FluxHire.
Suggested follow-ups
FluxHire’s suggestion engine proposes follow-ups from your records, such as a live job still without applications after five days or an application that has just changed stage. Each suggestion is assigned to a consultant, who takes it on as a task or dismisses it.
Questions in plain English
Ask the assistant about your jobs, candidates or pipeline. People and records in its answers link back to the underlying record, so the consultant can check the source.
Proposed changes wait
The assistant prepares record changes and holds them for approval. During early access, record edits are made by people holding the records editor permission, and approved changes are saved in FluxHire.
AI output can be wrong, and the consultant who acts on it is still responsible for the outcome. That is why each of these ends with a person.
05Connecting
Connecting JobAdder
- Step 01
One connection
A FluxHire administrator connects your agency’s JobAdder account once, for the whole organisation.
- Step 02
JobAdder sign-in
The connection goes through JobAdder’s own sign-in and consent screen, so FluxHire never sees the JobAdder password. FluxHire attempts to refresh access; expired or revoked authorisation can require an administrator to reconnect.
- Step 03
Reconnect banner
If the connection lapses, every FluxHire user sees a banner asking for it to be reconnected, instead of the sync quietly stopping.
06Where it sits
Where FluxHire sits among JobAdder integrations
JobAdder connects to many other tools through its own integrations.
An AI agent framework over your JobAdder records
FluxHire is a different kind of integration: an AI agent framework over your JobAdder records, not a single-purpose add-on. It does not replace those tools, and they keep running inside JobAdder as before.
FluxHire is an independent product, not made by JobAdder.
JobAdder publishes information about its API and integrations for anyone evaluating a connection.
JobAdder integration informationWho this integration is for
It suits agencies that:
- Run JobAdder
- Want AI help with research, follow-up and outreach
- Do not want a migration project to get it
If you are weighing a change of system instead, see how the AI agent framework works.
07First week
A first-week checklist for your JobAdder administrator
Pick a small group of consultants, and check that their records arrive showing the owner recorded in JobAdder.
Edit a test candidate in JobAdder, and confirm that the change reaches FluxHire.
Import a test contact from Contact Finder, and confirm that it appears in JobAdder as the record type the consultant chose.
Delete a test record in JobAdder, and confirm that FluxHire shows it as deleted after the next daily check.
Revoke access and reconnect, and note what consultants see while the connection is down.
Keep a dated log of each test and its result.
08Questions
JobAdder integration questions
Which JobAdder records does FluxHire sync?
The sync is built for candidates, with their activities and attachments, and for contacts, companies, jobs, job applications, placements and notes. Which ones are switched on for your account is confirmed during onboarding. Syncing JobAdder user tasks is being developed.
How do changes in JobAdder reach FluxHire?
When a record is updated or changes status, JobAdder sends a webhook event, and FluxHire processes it as it arrives. A scheduled catch-up sync also runs, collecting new records and anything a webhook missed. Notes are collected on a schedule, and records that have not changed are skipped.
Does FluxHire write changes back to JobAdder?
Contact Finder imports reach JobAdder when a consultant chooses them, deciding who is imported and as which record type. Field write-back is set up with your administrator during onboarding, with a conflict check and a confirmation read, and it is controlled centrally, not per user.
Who connects JobAdder, and does FluxHire see our password?
A FluxHire administrator connects your agency’s JobAdder account once, for the whole organisation, through JobAdder’s own sign-in and consent screen, so FluxHire never sees the JobAdder password. FluxHire attempts to refresh access; expired or revoked authorisation can require an administrator to reconnect. If the connection lapses, every FluxHire user sees a banner asking for it to be reconnected.
What happens when a record is deleted in JobAdder?
FluxHire marks the record as deleted at the next daily check instead of erasing it, retaining a deletion marker for review. This does not promise a restoration workflow. The first-week checklist includes a test of this: delete a test record in JobAdder, and confirm that FluxHire shows it as deleted after the next daily check.
How does field write-back work?
Only the edited field changes. FluxHire merges it into JobAdder’s current record, so every other value stays as JobAdder holds it. FluxHire reads the current value in JobAdder first and stops if someone has changed that field in the meantime, then reads the record again to confirm the new value. Retryable failures remain pending; conflicts and exhausted retries need administrator review. Queue acceptance is not confirmed delivery. It is set up with your administrator during onboarding.
Does FluxHire replace our other JobAdder integrations?
No. JobAdder connects to many other tools through its own integrations. FluxHire is a different kind of integration: an AI agent framework over your JobAdder records, not a single-purpose add-on. It does not replace those tools, and they keep running inside JobAdder as before.
Is FluxHire made by JobAdder?
No. FluxHire is an independent product, not made by JobAdder. JobAdder publishes information about its API and integrations for anyone evaluating a connection, and the sources at the end of this page link to it.
What does the AI do with our JobAdder data?
Once records have synced, the suggestion engine proposes follow-ups from your records, and the assistant answers plain-English questions with links back to the records. The assistant prepares record changes and holds them for approval; during early access, record edits are made by people holding the records editor permission, and approved changes are saved in FluxHire. AI output can be wrong, and the consultant stays responsible.
Not covered here?
Tell us how your JobAdder account is set up, and we will confirm which records and sync directions apply before your team uses them.
Request early access