Integration capabilities
Dashboards read from PeopleForce directly, so the numbers in Power BI match the HR system on every refresh.
Live HR datasets over the REST API
Change events via webhooks
Scheduled report exports
Mechanics
Which data reaches your BI tool
Data flows from PeopleForce to your BI tool. The REST API returns the current state on every call, webhooks send a payload shortly after a record changes, and report exports arrive as files on schedule.
| What is sent | Where | When | Data |
|---|---|---|---|
People & org structure employees, structure, change history | PeopleForce BI tool | on every refresh BI model via REST API | employees, custom fields, employee tables, field history, departments, divisions, locations, teams, positions, legal entities, job profiles, audits |
Leave & absence requests, balances, policies | PeopleForce BI tool | on every refresh BI model via REST API | leave requests, leave balances, leave histories, leave types, leave policies, holidays, leave balances and working hours reports |
Recruiting vacancies, candidates, applications | PeopleForce BI tool | on every refresh BI model via REST API | vacancies, candidates, applications, stage movements, sources, pipelines, disqualify reasons |
Performance & time Perform and Time modules | PeopleForce BI tool | on every refresh BI model via REST API | objectives, KPIs, review cycles, reviews, participants, answers, timesheets, timesheet entries, projects, overtime requests |
Change events pushed webhook topics | PeopleForce BI tool | usually within seconds to your endpoint | employee create, start, update, terminate; position, job profile, salary and employment status changes; leave request approve, reject, withdraw; applicant, vacancy, application, offer accept and reject; survey start |
Compensation and candidate data are switched separately on a Company API key: people compensation, vacancy base compensation range, candidate desired base compensation and candidate sensitive fields default to None and move to View when a dashboard needs them. One Company key works across API v1, v2 and v3; v3 also serves every v2 and v1 endpoint.
Parameters
What can be configured
Everything below is set in PeopleForce by an administrator or a user with the matching permission; the BI tool keeps its own refresh schedule and credential store.
Parameter | Options |
|---|---|
API key | Settings → Security → API keys: Company type for reporting, Career type for a careers site; on Company keys, four sensitive-data toggles (None / View / Edit, default None) and an IP allowlist; the token is shown once at creation |
Webhook | Endpoint URL, topic, optional shared secret for the signature; a failed delivery can be resent from the delivery log |
Report schedule | Report, format XLSX or CSV, days and time, recipients, active toggle |
Report export | Any report → Export, XLSX or CSV, on demand |
Refresh in the BI tool | Power BI scheduled refresh, Looker Studio data freshness or the ETL cron; the API answers with the current state on each call |
How the integration works
Who gets access, how sensitive fields are handled, and how fresh the numbers are on each refresh.
Access — with the Professional package
Sensitive data — switched separately on the key
Freshness — chosen by the consumer
Frequently asked questions
What analysts and administrators ask when connecting a BI tool to PeopleForce for the first time.
API and webhooks in the help centerHow is recruiting analytics built in Power BI?
From the recruiting resources of the API: vacancies, candidates, applications with their pipeline stage, stage movements, sources and disqualify reasons. Movements carry timestamps, which gives time-to-hire and time-in-stage per vacancy; sources give the channel breakdown.
Which API version should a BI connection use?
v3. It also serves every v2 and v1 endpoint, so one base URL and one Company key cover people, leave, recruiting, performance and time data.
Is Perform data available through the API?
Yes. Objectives, KPIs, review cycles, reviews, participants, questions and answers are read through the performance resources of the API.
How is Pulse survey data brought into BI?
Survey results are exported from the survey itself as a file and loaded into the BI model alongside the API data. For anonymous surveys the file is anonymised and keeps department, division, employment type and tenure. The survey_start webhook marks the beginning of each survey run.
How does Power BI authenticate with PeopleForce?
With the X-API-KEY header on the Web connector: the key is added under advanced options as an HTTP request header. The key's sensitive-data toggles decide whether pay fields come back.
Can pay data stay out of the BI connection?
Yes. People compensation and the three other sensitive-data toggles on a Company key default to None, so a new key returns every other data area and none of these fields until View is set on the key.
