All Collections
Best Practice Guides
Setting up Third-Party Webhooks for Ashby
Setting up Third-Party Webhooks for Ashby

How to set up Third-Party Webhooks for Ashby

Pritak Patel avatar
Written by Pritak Patel
Updated over a week ago


Third-Party Webhooks: When an event occurs in a third-party platform, such as a change to end-user data, that platform can be configured to send Merge a webhook with a data payload.

Third-party webhooks are a powerful tool, but setting up Ashby to send webhooks is an intricate process.

We highly recommend these steps be performed together in real-time.

Steps for End-Users

  1. After logging into Ashby, go to the Admin tab. Then click Integrations and Webhooks.

  2. Hit "+ New" in the top right corner to create a new webhook.

  3. A screen will slide open with 3 selections:

    • Webhook Type: this should be provided by your vendor. Merge currently supports the following options:

      • offerDelete

      • offerUpdate

      • jobPostingDelete

      • offerCreate

      • candidateStageChange

      • candidateDelete

    • Request URL: this should be provided by your vendor

    • Secret Token: type in a password/secret here. We recommend using a random UUID generator. Remember what you enter here, as you'll need to give this to your vendor.

  4. Before hitting "Add", have your vendor confirm they have everything set up on their end. DO NOT hit "Add" until they have finished all the steps in their section below!

  5. Repeat the process for any additional webhooks you need to set up.

Steps for Merge customers

  1. In your Merge dashboard, go to the Linked Accounts page and select the Ashby linked account you'd like to add webhooks for.

  2. Select the Webhooks tab at the top.

  3. Select one of the rows to open the settings for that particular webhook. Now, we'll need to exchange some of the information on this screen with your end user:

    1. Merge Receiver URL: this will need to be given to your end user to add to their webhook configuration in Ashby

    2. Signature Key: your end user will create this within Ashby as they set up the webhook and will need to share this with you to enter in the Merge dashboard. This is the same as the "Secret Token" in Ashby.

  4. Once the Signature Key is entered, hit "Enabled" to enable the webhook.

  5. After enabling the webhook, you can have your end-user hit "Add" within the Ashby dashboard. This will send over a sample webhook payload to test if the connection worked. If everything was successful, you should see the "Last Received" column in the table update.

  6. Repeat the process for any additional webhooks you need to set up.

Did this answer your question?