idibu integration for Atlas
The idibu integration connects Atlas to idibu’s multi job board posting. A recruiter advertises a role to every board on the account from inside the job record. Applicants come back into the Atlas ATS automatically rather than into a mailbox, where AI screening ranks them against the spec. It is available now, alongside the rest of the Atlas integrations.
Live · Reviewed September 2026
What idibu does
idibu is job distribution and response management software built for recruitment agencies. One login posts an advert to the boards an agency already pays for. Responses land in one place rather than across several board inboxes. A traffic light system handles shortlisting, and auto responses cover applications and rejections. Reporting measures advert performance board by board. The company reports that more than three quarters of its support tickets are handled within two hours. idibu connects to most of the major recruitment CRMs, and Atlas is one of them.
What changes in your day
A consultant finishes writing the spec on a new live role. The idibu button sits on the job description itself. The advert goes out to the boards on the list from that screen. Nobody logs into a second system to re-type a job title that the posting tool will disagree with anyway. A role that used to wait until the end of the day goes out while the brief is still fresh.
Applications arrive as candidate records, filed against the job they applied for. The shared applications mailbox, which everyone checks and nobody owns, stops being part of the process. The board the application came from stays on the record. A consultant picking the job up on Monday sees the full applicant list without asking anyone to forward it.
By mid morning a volume role has collected more applications than anyone is going to read in order. Atlas screens each one as it arrives and ranks it against the job spec. The spec the role was posted with is the spec the ranking uses. The top of the list is the part worth opening first. The consultant reviews a shortlist rather than assembling one.
At renewal time somebody has to say which board contracts are worth keeping. Every application carries its board into Atlas. Placements trace back to a source, by client and by desk. A desk running two boards for the same client can see which one actually fills. That turns a renewal decision into a reporting question.
A candidate applies for two roles in the same week. The second application attaches to the record that already exists instead of creating a new one. Nobody merges anything by hand. The history stays in one place, including what was sent and who spoke to them last. On a volume desk that is the difference between one record with context and four thin ones.
How to turn it on
Setup starts in the apps section of the Atlas settings page, where the idibu card has an Authenticate button. An App ID and App Secret come from a new app created on the idibu developer page. An OAuth access token is generated there too. Those go into Atlas, and the new app is then activated in idibu under Manage plugins and Addons. The second half is the webhook. Atlas issues a payload URL and a secret, which go into idibu under System Settings. The content type is set to application/json and the candidate event selected. After that the idibu button appears on the job description. Admin access to both systems is needed. The full sequence is in the guide to enabling multi posting by idibu.
There are pages on Broadbean and Xero that answer the same questions about those tools.
idibu FAQ
Do I still need an idibu subscription?
Yes. idibu supplies the job distribution and the board connections, and Atlas connects to your existing idibu account. The integration authenticates against that account, so your boards and your posting rules stay where they are.
Where do applicants end up?
In the Atlas ATS, as candidate records attached to the job they applied for. idibu sends them through a webhook to Atlas. Nothing depends on a recruiter forwarding an email out of a board inbox.
Which job boards does this cover?
Whichever boards sit on your idibu account. idibu handles the distribution, so the integration posts to the same board list you use today. Adding or removing a board is done on the idibu side, not in Atlas.
What do I need before connecting it?
An idibu account with developer access, and admin rights in Atlas. The connection uses credentials generated on the idibu developer page, plus a payload URL and secret issued by Atlas. The steps are done once, in order, by someone with access to both systems.
Does the integration cost extra?
Job board access and distribution are billed by idibu and by the boards themselves. How the connection sits within your Atlas plan is worth covering on a demo. It can be answered there against your board list and user count.
What happens when the same person applies twice?
The second application attaches to the existing candidate record rather than creating a duplicate. One person keeps one record in the ATS, with every application and message against it, which keeps reporting clean.
