Webhook automation succeeded, but nothing arrived

Updated

Applies to: Super Admins, Creators, and Integrators

The log shows a check mark, but nothing reached the system on the other end. We'll take it one step at a time, starting with what the check mark means.

Why it happens

On a callWebhook or sendAllTaskAnswers row, a check mark in Success means OnRamp queued the call to your webhook. It doesn't show whether the receiving system got the call or accepted it. So the row gets a check mark even when the address or credentials are wrong, or the receiving system has a problem.

Fix it

  1. On the project, open the Automations tab and select Logs. Find the row and note its Timestamp.

  2. In Payload, select View to see the data OnRamp prepared for the webhook.

  3. Optional: To compare against what the receiving system expects, open the automation's Call webhook step and expand Click for Example Data.

  4. In the receiving system, look for a request from around that time, and check how the system responded.

  5. Go to Settings > API & webhooks, and then select the Webhooks tab.

  6. Find the webhook. Its name shows under the automation's Call webhook or Send all task answers step.

  7. At the end of the webhook's row, select the three-dot Actions button, and then select Edit.

  8. Check that Webhook URL is the exact address the receiving system expects.

  9. Check that Authorizations shows the authorization your endpoint requires. If it's empty, select it. To change the credentials themselves, use the Authorizations tab, as described in Set Up Webhooks and Authentication in OnRamp.

  10. If you changed anything, select Save changes.

  11. Repeat the event on the project, and then select Refresh in Logs. Check the receiving system again.

Still stuck?

Contact support with the project's name and link, the webhook's name, the row's Timestamp and Action, the text from Payload, and what the receiving system shows for that time.

More in Getting Unstuck Fast