Skip to main content

​
Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the RECRU connector page.

​
Send RECRU job offer events to StackOne

RECRU delivers job offer events to a single tenant-wide endpoint called the Site API Listener. There is no event picker in RECRU — once the URL is set, RECRU sends every job offer event to it, and StackOne routes each one to its handler.

1

Retrieve StackOne Native Webhook URL

The Native Webhook URL is generated once an account has been linked.

  • Open the linked account in StackOne.
  • Copy the value from Native Webhook URL.
2

Open Settings in RECRU

Sign in to your RECRU backoffice at https://{tenant}.recru.eu and open the settings area.

  • In the left navigation, click Settings.
  • The COMPANY SETTINGS panel opens on the Basic tab.
The RECRU backoffice with Settings highlighted in the left navigation.
3

Open the External services tab

The webhook endpoint lives on the External services tab of the company settings panel.

  • At the top right of the COMPANY SETTINGS panel, click External services.
  • In the services list on the left, select Company web page.
The COMPANY SETTINGS panel with the External services tab highlighted.
4

Paste the Native Webhook URL and save

The COMPANY WEB PAGE panel holds a single URL field that RECRU posts every job offer event to.

  • Paste the Native Webhook URL you copied from StackOne into Site API Listener.
  • Click SAVE.
  • Note: the value must be pasted complete, including everything after the question mark — StackOne uses that part to match events to this account.
The COMPANY WEB PAGE panel with the Site API Listener field and the SAVE button highlighted.
5

Confirm your tenant on this connection

Inbound events are matched to this account using the Tenant value on the connection. It is set when the account is linked — confirm it matches the RECRU subdomain you signed in to.

​
Available webhook events

RECRU sends both of the following events to the Site API Listener. RECRU itself has no subscription picker, so the endpoint always receives both — only the events you enable in StackOne are forwarded on to you.

1

Job offer events

Events covering job offers published to your company website. RECRU has no candidate, application, or interview webhooks.

  • Job Offer Published (offer.published) — Fired when a job offer is published to the company website, and again each time a published offer is edited. RECRU sends this as action=offer.
  • Job Offer Unpublished (offer.unpublished) — Fired when a published job offer is withdrawn, and also when a published job offer is deleted. RECRU sends this as action=offer-unpublish.

​
Delivery format

How RECRU delivers job offer events, and the behavior worth knowing when you build on them.

1

One event per request

RECRU posts each event on its own — there is no batching. The request body is form-encoded rather than JSON, with arrays and nested objects in bracket notation such as project[id]. StackOne parses this for you and delivers the event with its payload already structured.

2

Publication depends on the response

RECRU reads the response to every delivery and marks a job offer as published only when it receives a valid acknowledgement. StackOne returns the acknowledgement RECRU expects, so offers continue to publish normally once the Native Webhook URL is in place.

3

Withdrawing and deleting look the same

RECRU sends the same unpublish event whether a job offer is withdrawn or deleted, and that payload carries only the job offer identifier. Use the Get Job Offer action if you need to tell the two apart.

​
Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.