Webhook and API data push

Q. I get an error every time I manually push data to our ERP. Why?

Answer: An earlier Bulk Push ERP request is still in progress. A new manual push is blocked until that request finishes or is cancelled.

1. Go to Download Requests.
2. Find the earlier entry with the action Bulk Push ERP that is still in progress.
3. Click the three dots against that entry and select Cancel Request.
4. Run the manual push again.

If there is no request in progress and the error continues, contact Meritto Support.

Q. The API logs show an endpoint we no longer use. Is data going to the wrong place?

Answer: No. The endpoint shown in the API logs list is the one set when the webhook logic was first created. If you change the endpoint later in the same logic, that label stays the same. Open the detailed log of any request to see the endpoint that was actually called.

If the detailed log also shows an endpoint you did not configure, contact Meritto Support.

Duplicate or unexpected pushes

Q. Our webhook is pushing old leads. Why?

Answer: A webhook pushes every record that meets its trigger point and conditions, including older records. A condition on stage alone, such as Re-enquired, also picks up historical leads that are in that stage.

• Add a date condition to the webhook so only recent records qualify.
• Keep the webhook conditions in line with the automation that sets the stage.

Q. The same lead is pushed more than once. Why?

Answer: The most common causes are:

• Several trigger points are active. Each trigger point (for example, Lead Verified, Lead Unverified and On Request) pushes the lead on its own. Keep only the trigger points you need.
• Several automations or webhooks overlap. Two automations setting the same stage, or two webhooks to the same destination, each send the lead. Combine them into one automation with OR conditions and one webhook.
• Retries after an unrecognised response. Failed On Request pushes are retried every 30 minutes. If your system's success reply (for example, Updated Successfully) is not set up as a success response, a successful push is treated as failed and retried. Make sure the webhook recognises the success replies for both create and update.

Records not pushed or rejected

Q. Some applicants were not pushed at the trigger point. Why?

Answer: A webhook does not push the same applicant again under the same configuration and trigger, even if the applicant's status changes later. Applicants pushed in an earlier session are skipped. If you need them pushed again, you are required to push data manually.

Q. A record is rejected because a dropdown value is blank. Why?

Answer: Every dropdown or radio option needs a matching value in the receiving system. If an option (for example, Prefer not to say) has no mapped value, it is sent empty and the record can be rejected. Map a value for every option in the field mapping.

Q. How are empty fields sent?

Answer: A field with no value is sent as an empty string (""), not as null. Make sure your system accepts empty strings for optional fields.