PayFit
Bring new starters, changes and leavers from PayFit into every system that needs them, with HR approving each change.
18 ways to read, 3 ways to write, each write switched on by you.
Quality checks
Built and tested with example responses.
- Ready to connect: doneEvery listed action is built in.
- Built and tested with example responses: doneEach action is built from the provider’s published API and tested against example responses, errors, rate limits and paging.
Connected, approved, proven.
The things teams do most with PayFit, an example flow with a person in the loop, and what Nexra keeps as proof.
Top actions
- Create validated absenceApproval by rule
- Create collaboratorApproval by rule
- List absencesRead
Example flow
- PayFit · List absencesDone
- PayFit · Create validated absenceNeeds approval
- Nexra · Record the decision and result in the evidence chainProven
Example workflow. Routine runs go through on their own. Only a change your rules flag, such as one over a limit you set, waits for the right person, who sees the exact change and the rule before it reaches PayFit.
What gets logged
- Whether it ran on its own or who approved it, and under which rule
- A fingerprint of the exact request sent to PayFit
- PayFit's reply: what it created or changed
- One entry in the evidence chain, linked to the one before
Try this in the sandbox
Run the whole flow with test data in your sandbox, then connect your own account when you are ready to go live.
For developers
Technical detail
PayFit collaborators, contracts, absences, worked time, payslip and document metadata, benefits and accounting entries, with collaborator, contract and absence creation.
PayFit API docs- Source actions
- 18
- Destination actions
- 3
- Data types
- 15
What you can map
Reads are always available. Writes are off until you switch them on for a connection, and governed writes follow your policies.
Absences2
- Create validated absenceDestinationNot retried automaticallyApproval before production
Records an approved absence for a contract, for example leave approved in another HR or scheduling system.
- List absencesSource
Absences overlapping a date range, optionally for one contract and by status.
Accounting entries1
- List payroll accounting entries (France)Source
Payroll journal lines for a month with accounts, debit, credit and analytic codes.
Auto enrolment documents1
- List auto-enrolment documents (UK)Source
Pension auto-enrolment letter metadata.
Collaborators3
- Create collaboratorDestinationNot retried automaticallyApproval before production
Creates an employee record for onboarding. Add a contract next; an admin completes the hire in PayFit.
- Get collaboratorSource
One employee with contact details and contract summaries.
- List collaboratorsSource
Employees with contact details, manager, team and contract summaries.
Companies1
- List CompaniesSource
List operation for Companies.
Company fr1
- Get company (France)Source
French company details with SIREN, SIRET and health-insurance proration method.
Contracts fr2
- Get contract (France)Source
One French contract with DSN codes.
- List contracts (France)Source
Active, pending and last year's archived contracts with DSN codes, IDCC and benefit contract links.
Contracts3
- Create contractDestinationNot retried automaticallyApproval before production
Creates a basic contract (job title and start date) for a collaborator; an admin completes it in PayFit.
- Get contractSource
One employment contract.
- List contractsSource
Employment contracts with job, dates, status, weekly hours and FTE.
Health insurance contracts1
- List health insurance contracts (France)Source
Mutuelle contracts with population, option, contribution rates and affiliated employment contracts.
Income tax documents1
- List income tax documents (UK)Source
P60, P45 and P11D document metadata.
Meal vouchers1
- List meal vouchersSource
Meal voucher counts and employer and employee amounts per collaborator for a month.
Payroll status1
- List Payroll StatusSource
List operation for Payroll Status.
Payslips1
- List payslipsSource
Payslip metadata (year, month, contract) for one collaborator.
Provident fund contracts1
- List provident fund contracts (France)Source
Prévoyance contracts with population, option and affiliated employment contracts.
Worked time1
- List worked timeSource
Effective and paid worked time per contract for a payroll month.
Access and limits
- Authentication
- Company API key with company ID
- Plans and access
- PayFit customers in France, Spain and the United Kingdom with API access. The company API key's scopes (collaborators:read, collaborators:write, collaborators:contracts:write, contracts:read, time:read, time:write, contracts:payslips:read, accounting:read, pension:read, health-insurance:read, collaborators:meal-vouchers:read) limit each operation.
- Test environment
- Partner test companies are available through PayFit's partner programme.
- Rate limits
- 50 reads and 20 writes per second per client; HTTP 429.
- Pagination
- maxResults (up to 50) with meta.nextPageToken.
- Provider events
- None documented for API-key integrations. Flows run on demand, on a schedule, or when a scheduled check finds new or changed records.
Before you build a flow
- Company detail and monthly payroll-status reads. Payroll mutations and accounting exports are not implemented; country-specific payroll endpoints require separate validation.
- PayFit's public API has no teams or custom-field endpoints; a collaborator's team name is returned on collaborator records.
- Social security numbers, IBAN and BIC are deliberately not mapped or written.
- Payslip and document PDFs, the legacy accounting file export and the payment file are not downloaded; metadata includes a PayFit API URL.
- Accounting entries, France contracts, health insurance and provident fund contracts are French-company endpoints; tax and auto-enrolment documents are UK.
- Created contracts are basic: an admin finishes them in PayFit and they take 2-5 minutes to appear. PayFit returns no ID for a created contract.
- Created absences are validated immediately. Cancelling absences, partner declarations and health-insurance affiliation writes are deliberately not implemented.
- PayFit documents no idempotency key; an uncertain create is never repeated automatically.
Developer reference
- Create the PayFit credentials described above with the narrowest permissions your flows need.
- In Nexra, open Connect, then Connections, then New connection, choose PayFit, enter its settings and credentials, and tick only the write actions you need. Connection guide
- Test the connection, then use its actions as flow sources and destinations. Flow guide
Machine-readable detail: GET /api/public/connect/connectors/payfit and the Connections API.
