Skip to main content
Redsun Platform
Atlas Integration

Atlas projects,
live on your own site.

Redsun reads your Atlas projects, people and companies through the Atlas API, publishes open roles to your website, and adds every applicant to the right project with their CV and a note of where they came from.

Atlas API
Projects published as jobs
Applicants added to the project
Closed roles taken down
Connecting

An API key and the email of the Atlas user it acts as.

Atlas attributes every write to a real user, so alongside the API key you give Redsun the email of the Atlas user applicants and notes should be recorded against. There is no separate service account to set up.

  • People and projects are read with an updated-since filter, so an hourly run fetches what changed instead of the whole database
  • Once a day the adapter reads every project in full and closes any role on your site that Atlas no longer has open
  • Register the Atlas webhook on the Connections screen and new people, projects, companies and placements reach your site within seconds, with the hourly run still catching anything a delivery missed
Scheduled syncHourly
Full read to close finished rolesDaily
Plus the Atlas user to act asAPI key
Record types synced7
What syncs

What the Atlas adapter does.

Each item below maps to an endpoint in the Atlas API that the adapter calls.

Projects as job pages

Open projects come across with the formatted advert, location, salary and currency, contract type and work mode, and become job pages on your site.

Applicants on the project

A website application is posted to the Atlas project's applicants, so the candidate appears in that project's pipeline rather than loose in the database.

CV upload

The CV the candidate uploaded on your site is attached to their Atlas person record.

Candidates and contacts

Atlas people are split into candidates and client contacts on the record's own contact flag, and hiring managers from your employer wells are created as contacts.

Companies and placements

Client companies, placements and your Atlas users come across too, feeding consultant profiles, sector pages and placement counts on the site.

Notes and custom attributes

Each application adds a note recording how the candidate applied, with their phone, LinkedIn and cover letter. Atlas custom attributes can be mapped onto Redsun fields from the Connections screen.

Which way it syncs

What moves between Atlas and your site

Atlas to your site

  • Open projects as job pages: advert, location, salary and currency, contract type and work mode
  • People, split into candidates and client contacts on Atlas's own contact flag
  • Client companies, placements and your Atlas users
  • Changes within seconds once the Atlas webhook is registered; otherwise hourly, with a full read of projects once a day

Your site to Atlas

  • Applications, added to the project's applicants so they sit in that project's pipeline
  • The applicant's CV, on their Atlas person record
  • A note saying how they applied, with phone, LinkedIn and cover letter
  • Hiring managers from your employer wells, created as Atlas contacts
  • With Signals, on the Grow plan: a personal link on each contact, written to a custom field you choose, so a Atlas email that merges it tells Redsun who clicked through

Read only: Projects. You create them in Atlas; Redsun publishes them and never creates or edits one.

Atlas Integration FAQs

Common questions about connecting Atlas to a Redsun-powered recruitment website.

How does Redsun connect to Atlas?
+
With an Atlas API key and the email of the Atlas user Redsun should act as. Atlas records every write against a named user, so applicants and notes Redsun creates appear as that person's activity. Both are entered on the Connections screen in Redsun.
Do roles closed in Atlas come off my website?
+
Yes. The hourly sync picks up projects that changed, and once a day Redsun reads every project in full and closes any role on the site that Atlas no longer returns as open. A role that closed because it was filled is marked closed rather than deleted, so your placement history keeps it.
What syncs between Atlas and Redsun, and in which direction?
+
From Atlas to your site: open projects as job pages, people split into candidates and client contacts, client companies, placements and your Atlas users. From your site to Atlas: applications added to the project's applicants, the CV on the person record, a note of how they applied, and hiring managers from employer wells created as contacts. Redsun never creates or edits a project in Atlas.
Does Atlas push changes to Redsun instantly?
+
Yes, once the webhook is registered from the Connections screen. Atlas signs each delivery, Redsun checks the signature and writes the change straight away. The hourly run still happens, so a delivery that failed is picked up on the next pass, and a role Atlas stops returning is closed by the daily full read.

See the Atlas integration in action.

Book a demo and we'll show you a role moving from Atlas onto your site, and an application landing back on the record.