Managing Webhooks
Webhooks send information from Wamly to another system the moment something happens, such as a candidate completing an interview or a project being edited. This guide shows you where to find webhooks in Wamly and how to create, edit, deactivate and delete them.
How Webhooks Work
- Real-time data transfer: instead of another system repeatedly checking Wamly for updates, Wamly sends the data to your chosen URL as soon as the event happens.
- One event, several systems: you can set up more than one webhook for the same event, so the same data can go to your CRM, a database and an HR tool at once.
- Automation: webhooks let you start processes in other tools automatically, for example posting an alert when a candidate completes an interview or updating a third-party ATS.
Before You Start
Webhooks are part of the Wamly API and webhooks feature, which must be included in your subscription. If it is not, the Integrations tab shows a banner that lets you request an upgrade, and the webhook controls are locked.
You also need a role that includes the Webhooks permissions (view, create, edit and delete). Users without them see the Webhooks section as locked.
Webhooks used to be on their own Webhook tab and were limited to System Managers. They now sit in the Integrations tab, and access is controlled by role permissions.
Finding Your Webhooks
- In the left-hand menu, click My Organisation.
- Open the Integrations tab.
- Scroll to the Webhooks section, below Service Accounts.
The table lists each webhook by Name, with its event underneath, and its Status (Active or Inactive). For an overview of everything else on this tab, see Managing Integrations & Webhooks.
Creating a Webhook
Step 1: Open the Create Webhook Window
In the Webhooks section, click Create.
Step 2: Fill in the Details
- Name: a name that tells you what the webhook is for, such as "ATS sync". Each active webhook in your organisation needs a different name.
- URL: the full web address that should receive the data, for example https://example.com/webhook. It must be a valid, publicly reachable URL.
- Event: the event that triggers the webhook. See the list below.
The name and URL can each be up to 255 characters.
Step 3: Save the Webhook
Click Save. The webhook is added to the table as Active, and Wamly sends a POST request with the event data to your URL each time the event happens.
Available Events
- Project Creation: a new project is created.
- Project Edit: a project is edited.
- New Interview: a candidate completes an interview.
- New Rating: a candidate is given a new rating.
- Candidate interview status change: a candidate's interview status changes.
- Psychometric Assessment Status Update: a psychometric assessment status is updated.
- Background Check Status Update: a background check status is updated.
- Assign Candidate to Rater: a candidate is assigned to a rater.
- Candidate Tags change: a candidate's tags change.
Editing, Deactivating and Deleting a Webhook
Open the actions menu at the end of the webhook's row.
- Edit: change the name, URL or event, then click Save. You can also click the webhook's name to edit it.
- Deactivate: the webhook stops receiving events until you turn it back on. Click Deactivate again in the confirmation window.
- Activate: turns an inactive webhook back on so it starts receiving events again.
- Delete: removes the webhook. Click Delete again in the confirmation window.
Deleting a webhook removes it permanently. Any integration that relies on it stops receiving events. If you might need it again, deactivate it instead.
Example: Sending Hired Candidates to Zoho People
When a candidate is moved to the "Hired" stage, you can push their details into an employee management system such as SAP SuccessFactors or Zoho People. This example uses Make.com and Zoho People.
- In Make, create a new scenario and add the incoming webhooks module. Copy the URL the module gives you.
- In Wamly, go to My Organisation > Integrations > Webhooks and click Create.
- Give the webhook a name, paste the URL from step 1 into the URL field, choose the Candidate interview status change event and click Save.
- Back in your Make scenario, add the Zoho People "add record" module, with a filter that only lets through records where the stage is "Hired".
- Map the candidate information from the webhook into the Zoho People "add record" module.
- When a candidate's stage changes to Hired, the webhook triggers your Make scenario and the candidate's details appear in Zoho People.