Custom webhooks let you push data from Recruiterflow to any external endpoint — a Zapier webhook, an internal tool, or your own API — on demand, from any entity page.
Once configured, you trigger the webhook manually using the Send to... option on a candidate, contact, job, company, or deal profile. Recruiterflow sends the entity's data as a payload to the URL you've set up.
How to Set It Up
Go to Settings → Integrations and click Add Integration.
In the popup, select Webhook Integration as the integration type.
Select the Entity you want to send data from — Candidate, Contact, Job, Company, or Deal. This determines which entity's data gets included in the webhook payload.
Give the webhook a Name. This is what appears in the Send to... menu on entity profiles, so name it something recognizable (e.g., "Send to Zapier" or "Push to Internal CRM").
Enter the Webhook URL and select the HTTP method (typically POST). Click Save.
How to Trigger the Webhook
Once your webhook is saved, open any profile for the entity type you configured. Click the three-dot menu (⋮) and select Send to...
Select the webhook you configured from the list. Recruiterflow immediately sends that entity's data as a JSON payload to your endpoint.
A Practical Example
Your agency uses an internal onboarding tool that accepts candidate data via API. Set up a Candidate webhook pointing to that tool's endpoint. When a recruiter clicks Send to... → Onboarding Tool on a placed candidate's profile, the candidate's details are pushed over automatically — no copy-pasting required.
Things to Know
Each webhook is tied to a single entity type. To send data from multiple entities (e.g., both Candidates and Jobs), create a separate webhook for each.
Webhooks are triggered manually via Send to... — there are no automatic event-based triggers in this integration.
The webhook name you set is what appears in the Send to... menu, visible to all users in the workspace. Keep names descriptive.
Only workspace admins can create or edit webhook integrations in Settings.
To test a webhook, use a service like webhook.site to inspect the payload before connecting it to your real endpoint.