Managing Webhooks

Managing Webhooks

This guide provides the steps necessary to modify your Webhooks within the Wamly platform.

Key Characteristics and Logic

Real-Time Data Transfer: Unlike standard APIs that require "polling" (repeatedly checking for updates), webhooks push information to a destination system the instant a chosen event is triggered.

Multi-System Integration: Wamly allows for multiple webhooks per event. This means you can simultaneously send candidate data to several external systems—such as your CRM, a secondary database, or a specialized HR tool—without needing to set up separate manual exports for each.

Agile Automation: By leveraging webhooks, organisations can automate downstream processes, such as triggering an internal Slack alert when a candidate completes an interview or automatically updating a third-party ATS.

Accessing the Webhook Configuration Panel

InfoPermissions: Access to view, create, and configure webhooks is restricted exclusively to System Managers.
  1. Begin by navigating through the system interface.
  2. To access your Webhook settings, navigate to the left-hand menu.
  3. Click on My Organization to open the settings view.
  4. Ensure that the Webhook tab is currently selected.
  5. Click on the “Add New” action button at the top right.
  6. Enter a name for your Webhook, the Webhook URL that the Webhook should call and select the Webhook Event Type that should be used to trigger the Webhook:
    1. Project Creation webhook is triggered when a new project is created.
    2. A New Interview event is triggered when a candidate completes an interview.
    3. A New Rating event is triggered when a new rating is given to a Candidate.
    4. A Project Edit event is triggered when the project has been edited.
    5. An event is triggered when a Candidate's interview Status is changed.
    6. An event is triggered when a Psychometric Assessment Status is Updated.
    7. An event is triggered when a Background Check Status is Updated.
    8. An event is triggered when a Candidate is assigned to a Rater.
    9. An event is triggered when a Candidate’s Tag(s) change.
  7. Once done, click on “Create” at the top right of the menu screen.
  8. Webhooks can be edited, deactivated or deleted from this menu.

Use case example of webhook

When a candidate is moved to the “Hired” stage, push the candidate info into an employee management system like  SAP SuccessFactors or Zoho People.

Example using Make.com & Zoho People

  1. Step 1:  Create a new scenario in Make and use the incoming webhooks module. Copy the URL this module provides
  2. Step 2: In Wamly , Navigate to My Organisation >> Webhooks >> and create new.
  3. Step 3: Give the webhook a name, copy the URL from Step 1 into the Webhook URL field and choose the event “Candidate interview status change”.
  4. Step 4: Go back into your scenario in make.com and add the Zoho People “add record” module with a filter that checks the webhook and only allows records where stage is “Hired” through.


    • Related Articles

    • Managing Organisation Structure

      This guide provides the steps necessary to review and modify your organisation structure details within the platform. There are two sections namely Departments & Cost Centers. Key Impacts of Using Departments Segmentation: The main intention behind ...

    • Lesson 8: Webhooks

    • Managing Integrations

      Integrations in Wamly are designed to consolidate fragmented hiring tools into a single, automated ecosystem, enabling organisations to manage the entire candidate journey—from attraction to background verification—within one platform. Accessing the ...

    • Managing Branding

      This guide provides the steps necessary to review and modify your organization’s Branding within the Wamly platform. Key Impacts of Using Branding Candidate-Centric Design: Built for teams who care deeply about the candidate journey. Custom Branding: ...

    • Managing Security

      At Wamly, security is integrated into every layer of the hiring process to ensure that sensitive organisational and candidate data remains protected. Our security framework relies on a combination of industry-standard authentication ...