Webhook Data Push Troubleshooting Guide

Webhook Data Push Troubleshooting Guide

Overview

If your webhook is not pushing data as expected, certain JSON keys are returning blank values, or the data push is delayed, follow this step-by-step troubleshooting guide to identify and resolve the most common issues.
This guide helps you quickly determine whether the issue lies in the webhook configuration, data logic, or vendor-side validations.

Data Is Not Being Pushed Based on Webhook Configuration

The data will not be pushed through a webhook in the following scenarios:

1. Incorrect Trigger Selection

  1. Example: If the webhook trigger is set to Application Submit, but the candidate has only initiated the application (not submitted it yet), the webhook will not push any data.
  2. Action to Take: Verify whether the selected trigger matches the client or vendor requirement. If not, correct the trigger in the webhook configuration.
Steps to Verify:
  1. Navigate to Webhook → Edit and open the concerned webhook configuration.
  2. Review the Trigger (Step 1) and Conditional Filters (Step 3).
  3. Go to API/Integration Logs, locate the vendor configured in Step 1, and open the relevant log entry to check for errors or failed pushes.

2. Conditional Filters in Step 3

  1. Example: If a conditional filter is applied in Step 3 such as Course = MBA, only records with “MBA” in the course field will be pushed. Any other course data will be skipped.
  2. Action to Take: Review the conditional logic defined in Step 3. Ensure that it does not contradict the data that needs to be pushed via the webhook.
Steps to Verify:
  1. Navigate to Webhook → Edit and open the concerned webhook configuration.
  2. Review the Trigger (Step 1) and Conditional Filters (Step 3).
  3. Go to API/Integration Logs, locate the vendor configured in Step 1, and open the relevant log entry to check for errors or failed pushes.

3rd Party Vendor Error or Internal Validation Failure

1. Data has been Pushed but error is received 

Examples:
  1. Validation Error: Data is successfully pushed from Meritto, but the 3rd-party API returns an error (for instance, due to invalid parameters or authentication failure).
  2. Wrong Configuration: Wrong value has been set in the success marking configuration and due to this system is marking all the success entries failed. 
Actions to Take:
  1. Check the API/Integration Logs to identify any error messages linked to the specific Lead, Application, or Opportunity, check the error and convey the same to the 3rd party vendor based on the input from their side, check and correct the configuration, data or advance settings inside webhook. 
  2. After the correction of configuration or candidate data , the data can be manually pushed via the single or bulk push to webhook options in Lead, Opportunity or Application Manager. 
  3. Also this failed data will be retired once a day by the systems fallback mechanism which is triggered at 2AM everyday.
Steps to Verify:
  1. Navigate to Webhook → Edit and open the concerned webhook configuration.
  2. Review the Trigger (Step 1) and Conditional Filters (Step 3).
  3. Go to API/Integration Logs, locate the vendor configured in Step 1, and open the relevant log entry to check for errors or failed pushes.

Data Is Being Pushed With a Delay

The data push may happen with a delay in the following cases:

1. Queue-Based Delay

How to Identify the delay:
  1. If the Last webhook data push entry in the API logs is significantly earlier than the current time, then data push might be delayed by webhooks queuing system 
  2. If the candidate has completed the trigger and the data is not yet pushed , then data push might be delayed by webhooks queuing system 
Data push can be delayed due to Meritto’s internal queuing system, which ensures requests are processed in the order they are generated.

Steps to Verify:
  1. Navigate to Webhook → Edit and open the concerned webhook configuration.
  2. Review the Trigger (Step 1) and Conditional Filters (Step 3).
  3. Go to API/Integration Logs, locate the vendor configured in Step 1, and open the relevant log entry to check for errors or failed pushes.

2. Incorrect Configuration Placed

Example:
  1. If a webhook is configured with the trigger Application Initiate, but has a condition based on a form field (such as “Program = MBA”), the webhook won’t trigger in real time. This is because, at the time of application initiation, the form field is usually empty.
  2. As a result, the webhook will not fire instantly but will be handled later through the fallback mechanism.
Steps to Verify:
  1. Navigate to Webhook → Edit and open the concerned webhook configuration.
  2. Review the Trigger (Step 1) and Conditional Filters (Step 3).
  3. Go to API/Integration Logs, locate the vendor configured in Step 1, and open the relevant log entry to check for errors or failed pushes.
 

Contact Meritto Support

If all the above points have been verified and the issue still persists, please reach out to Meritto Support with the following details. Providing complete information helps us resolve your issue faster.

Details to Share:
  1. Webhook Name
  2. Trigger Type
  3. Lead, Opportunity, or Application Identifier
  4. Proof that the trigger condition has been met (e.g., screenshot or record reference)
  5. Any error logs from the API/Integration Logs
Support Email: support@meritto.com
Or, raise a ticket directly via the Help & Support section in your Meritto account.

Conclusion

By following the above troubleshooting steps, most webhook-related issues can be identified and resolved quickly. Ensuring that triggers, conditional filters, and required fields are configured correctly will help maintain real-time, reliable data flow between Meritto and your connected systems.