RECRU connector
Back to the connector overview, authentication methods, and actions.
12 Oct 2026
new-actions data-sync webhooks docsAdded webhook support for job offer publish and unpublish events, delivered through RECRU’s Site API Listener. Documented the shape of the paging, search, specialFilter, profilePhoto, filesPreview and CV data objects, corrected action descriptions that named parameters the API does not accept, added list_project_close_reasons, and replaced account-specific code lists on project type, phases and close reason with pointers to the actions that resolve them. Allowed search values to be arrays for the in and notIn conditions, documented that notLike compares the value as given so a substring negation needs %value%, and documented the fields the provider truncates, overrides or does not store. Added validation so a request that would be silently ignored is rejected instead — jobseeker_source and source_name are now mutually exclusive, status_closed_reason is required when a project is closed, and the candidate tag actions require the candidate and tag ids. Added length limits on the department postal code and NACE fields so an over-long value is rejected instead of silently truncated, documented which fields the project-candidate list can be ordered by, recorded that a rejection phase requires a rejection reason, and removed the candidate status field, which the API accepts but never stores. Removing a candidate from a project now reports the real outcome — the provider commits the removal and then fails on a follow-up query, so the result is verified before being returned. Constrained the sortable columns on the project-candidate list, and removed the event id and the project-phase filter, which the API accepts but ignores. Documented that a project needs a type set before its pipeline can be used — without one, phase events and candidate removals fail with a database error. Corrected the file attachment fields — department files use isLogo, documentType now carries its real id list, and the stored name is the supplied filename with a unique prefix rather than a replacement.