Your Firefish adverts,
on your own domain.
Redsun reads the live adverts behind your Firefish jobs and publishes them as job pages on your own site. Applications come back the other way as considerations against the right role, with the CV attached to the candidate record.
The published advert is the source of truth.
Firefish keeps two versions of a role: the internal job record your consultants work from, and the advert that feeds your careers site and XML job boards. Redsun reads the advert, so the page a candidate lands on carries the copy your team actually wrote for the market.
- Job pages are built from the advert's marketing content
- Contract type comes only from the job's JobType field or the advert's Type field. A title that mentions 'contract' changes nothing
- Remote and hybrid roles are flagged from the advert's RemoteWorking field, which only exists on the advert
- Payment bands map from the advert's minimum, maximum and payment rate into a salary range on the page
- A role whose advert is no longer live drops off your site on the next sync run
What the Firefish adapter does.
Each item below maps to a Firefish endpoint the adapter already calls.
Advert Sync
Redsun pairs each open Firefish job with its live advert, so the description, employment type and pay band on your site match the ones on your Firefish careers feed.
Considerations
A website application is submitted directly against the Firefish job as a consideration, and the candidate's CV is uploaded to their Firefish document record.
Market Context
Salary benchmarks and sector demand signals are attached to a lead before it reaches Firefish, so the consultant opening it has the market position already in front of them.
Engagement Notes
Firefish has no scorecard object, so Redsun writes website engagement onto the candidate or contact as a note rather than inventing a field your CRM does not have.
Incremental Sync
Firefish supports a from-date filter, so each scheduled run asks only for records changed since the last one. Runs hourly by default, plus on demand from the Connections screen.
Scoped Tokens
Every Firefish API scope gets its own token, read and write kept separate, and Redsun calls the API from a fixed egress address for accounts that restrict by IP.
Which way it syncs
What moves between Firefish and your site
Firefish to your site
- Open jobs, each paired with its live Firefish advert: description, employment type, remote flag and pay band
- Candidates, contacts, client companies, placements and consultants, read hourly with a from-date filter
Your site to Firefish
- Applications, submitted against the Firefish job as considerations
- The applicant's CV, on their Firefish document record
- Employer and contact enquiries: the contact is searched by email first, then created or updated, with a note
- Website engagement as a note, because Firefish has no scorecard object
- Empty fields on an existing candidate, filled from what they told your site; fields you have filled are left alone
Read only: Jobs. Redsun reads them from Firefish and never creates or edits a job there.
Firefish Integration FAQs
Common questions about connecting Firefish to your Redsun-powered recruitment website.
How does Redsun integrate with Firefish?+
What data syncs between Redsun and Firefish?+
Do I need a developer to connect Firefish to Redsun?+
Can I use Conversion Wells with Firefish?+
Is the Firefish integration included in all Redsun plans?+
Submissions from Conversion Wells (salary checkers, market intelligence tools and application funnels) reach Firefish through the same contact writeback path described above.
Keep reading
See how Firefish connects to your website.
Book a demo and we'll walk through the Firefish integration on your own data, from advert sync to considerations.