Your Crelate Job Portal,
on your own website.
Redsun reads your Crelate jobs, contacts, companies and placements through the Crelate API, publishes the roles on your Crelate Job Portal to your website, and adds each applicant to that job's pipeline with their CV and a note of how they applied.
One API key, from a Crelate user with API access.
Crelate API keys belong to a person, so everything Redsun writes appears in Crelate's audit log as that user. Admins can always generate a key. Anyone else needs a Crelate admin to turn on API access for their role first.
- Jobs, contacts, companies and placements are read with Crelate's modified-after filter, so an hourly run fetches only what changed
- A role reaches your site once it is published to your Crelate Job Portal, which makes the portal your publish switch
- Crelate does not push changes, so updates arrive on the next scheduled run or when you press Sync now
What the Crelate adapter does.
Each item below maps to an endpoint in the Crelate API that the adapter calls.
Portal jobs as job pages
Each role on your Crelate Job Portal comes across with its portal title, advert, location, salary range and job type. Hidden, on-hold and closed roles stay off the site.
Applicants in the job pipeline
A website applicant is matched to an existing Crelate contact by email, or created as a candidate, then added to the job's pipeline at the earliest stage Crelate treats as New, or at a stage you choose.
CV and application note
The CV the candidate uploaded is attached to their Crelate contact, and a note records how they applied, with their phone, LinkedIn and cover letter.
Candidates and client contacts
Crelate contacts are split into candidates and client contacts on their own record type. Hiring managers from your employer wells are added as client contacts and linked to a matching company.
Companies, placements and leads
Companies, placements, your Crelate users and business development leads come across too, feeding consultant profiles and placement counts on your site.
Diversity data left in Crelate
Crelate keeps EEO and diversity answers on contact records. Redsun never requests those fields, so they never leave Crelate.
Crelate Integration FAQs
Common questions about connecting Crelate to a Redsun-powered recruitment website.
- How does Redsun connect to Crelate? +
- With an API key from a Crelate user who has API access, pasted on the Connections screen in Redsun. Crelate keys belong to a person, so applicants and notes Redsun creates appear in Crelate as that user's activity. The connection test tells you how many jobs are on your Crelate Job Portal.
- Why is one of my Crelate jobs missing from my website? +
- Redsun publishes a Crelate job when it is on your Crelate Job Portal with a portal title and description, is not hidden, and is not in a closed or on-hold stage. Open roles you have not published stay off your site. Publish the job to your portal in Crelate and it appears after the next sync.
- Does Crelate push changes to Redsun instantly? +
- No. Crelate does not offer webhooks, so Redsun polls: every hour on schedule, or straight away when you press Sync now on the Connections screen. Once a day Redsun also reads every job in full and closes any role Crelate no longer returns.
Keep reading
See the Crelate integration in action.
Book a demo and we'll show you a role moving from Crelate onto your site, and an application landing back on the record.