Djinni integration with PeopleForce: job publishing

Integration capabilities

Once connected, every Djinni application becomes an application in the vacancy pipeline, and the Djinni account is needed only for what lives on its side: the job ad itself.

Automatic candidate import from Djinni

Every three hours, PeopleForce collects new applications from the ad and creates them at the first pipeline stage. Each application comes with contacts, Telegram, salary expectation in dollars, English level and resume file, and stage automations run right away.

Database search by resume content

The resume from a Djinni application is attached to the card and parsed, so its text is included in database search. A year later, you can find the candidate by a framework or a previous employer that never appeared in the card fields.

Duplicate check on import

Before creating a card, the system looks for a match by the candidate's Djinni ID, email and the same resume file, and by phone if that check is enabled. When the person is already in your database, an application for this vacancy is added to their existing card.

Source performance analysis

Every new candidate created from a Djinni application gets the “Djinni” source. The source report shows how many candidates the platform brings, and pipeline reports filtered by source show which stage they reach. That lets you compare Djinni with other channels before paying a fee for anyone.

How it works

Data exchange

The job ad goes to Djinni at the moment you publish from PeopleForce. In the other direction, PeopleForce calls Djinni every three hours, on the hour, and collects new applications to that ad.

What is transferred	Direction	When	Data
Job ad Vacancy → job ad in your Djinni employer account	PeopleForce Djinni	at the moment of publishing	title, description, category, domain, countries, work format, experience, English level, salary range in $, recruiter
Candidate application Application on Djinni → application in the vacancy pipeline	Djinni PeopleForce	every three hours on the hour	name, email, phone, Telegram, job title, salary expectation in $, city, skills, languages and English level, cover letter, links to profile, LinkedIn, GitHub and portfolio, resume file

PeopleForce receives candidates who applied to the ad themselves and shared their contacts. Conversations a recruiter started with an offer on Djinni, and applications with hidden contacts, stay in the Djinni account. A repeat application from the same person to the same vacancy is merged into the existing one.

Publishing

Two publishing modes on Djinni

First, you choose where the ad comes from: PeopleForce creates it on Djinni or connects to the one you have already posted.

Mode 1

New publication

The ad is not on Djinni yet. PeopleForce creates it from the vacancy fields and Djinni reference lists.

Title and description come from the vacancy; for Djinni, the description needs at least 300 characters
Category, domain, work format, experience and English level are selected from Djinni reference lists
The salary range is filled in from the vacancy when it is in dollars and the publication author has permission to see vacancy salaries
The ad is posted with no expiry date and goes through moderation on the Djinni side

Mode 2

Existing job ad

The ad is already live in your Djinni account. PeopleForce links it to the vacancy and collects applications from it.

The ad is taken from the active ads of the account whose key is set in the publication
The ad on Djinni stays exactly as it is, with no republishing
Collect all applications from the ad or only those received from a chosen date
Applications received before connecting also reach the pipeline when “all candidates” is selected

Publication fields

What you set up in a publication

These Djinni parameters are filled in in the publication on the vacancy card; the platform uses them to show the ad to the right candidates and decide who can apply.

Parameter	Value
Category and domain	Specialization and company industry from Djinni lists, both fields required
Work format and countries	Remote, hybrid, office or candidate's choice; up to five countries with company offices, by default the vacancy country or Ukraine
Salary range, $	From and to per month, with a difference of up to $5,000. A public range accepts applications within the allowed deviation; with a private range, anyone can apply
Experience and English level	Minimum experience is required, English is optional; an allowed deviation is set for both
Recruiter	From the list of recruiters in your Djinni account; by default, the publication author or the vacancy owner
Details	Part-time, test task, cover letter required: three flags passed to the ad

Integration conditions

What to know before connecting: who pays for what, whose key the connection uses, and what data stays on each side.

Publishing on Djinni is free, the hiring fee is on the Djinni side

Posting ads on Djinni is free; the platform charges a fee only for a hired candidate, under its own rules (see the Djinni pricing page for current terms). The integration is included in the Recruit module at no extra cost.

Access goes through your employer account API key

The API key provided by Djinni is entered in Settings → Integrations → Djinni, and PeopleForce verifies it on the platform when saving. You can connect several accounts. Djinni opens API access for your account on request.

All candidate work stays in PeopleForce

Djinni delivers the application, and from there stages, ratings, emails and automations live in the PeopleForce pipeline. In the other direction, the connection sends only the ad and its status; candidate card data and hiring details stay in PeopleForce.

The ad follows Djinni rules

An ad created from PeopleForce goes through Djinni moderation and, once approved, stays live with no time limit. As soon as the vacancy in PeopleForce leaves the “Open” status or the campaign goes offline, the ad on Djinni is deactivated.