Webhook automation failed: webhook off or deleted

Updated

Applies to: Super Admins, Creators, and Integrators

A webhook action sends only while its webhook exists and is turned on. We'll work out which case you have and get the action sending again.

Why it happens

The webhook the action uses was turned off or deleted in Settings > Webhooks, so OnRamp skipped the call. This applies to both Call webhook and Send all task answers actions. The action's row in Logs (callWebhook or sendAllTaskAnswers) has an X in Success. In Error, select View to see which case you have:

  • The webhook no longer exists means the webhook was deleted.

  • A message with the webhook's name and is inactive means the webhook is turned off.

Any other message has a different cause. For example, The user who triggered this automation could not be found also skips the call, but the webhook is fine. For those messages, see Project automation didn't run or failed or contact support.

Fix it

If the webhook is turned off

  1. Go to Settings > Webhooks.

  2. Optional: To see which projects and playbooks will start sending again, select the webhook's uses button (for example, 3 uses). The Webhook Usages page lists the projects that use it, and the playbooks you can see that use it.

  3. Open the action menu at the end of the webhook's row.

  4. Select Edit.

  5. Turn on Enabled.

  6. If Authorizations is empty and your endpoint needs credentials, select the authorization.

  7. Select Save changes.

If the webhook was deleted

A deleted webhook can't be restored, so set up a replacement.

  1. In Settings > Webhooks, select New webhook.

  2. Enter the Webhook Name and Webhook URL.

  3. If your endpoint needs credentials, select its authorization in Authorizations.

  4. Leave Global webhook off. A project automation can only use a webhook that isn't tied to an event.

  5. Select Create webhook. New webhooks start turned on.

  6. On the project's Automations tab, select the automation.

  7. Select its Call webhook or Send all task answers step.

  8. In Webhook, select the new webhook.

  9. Select Save. Save appears only for people who can update the project's settings. Anyone else sees the automation read-only.

  10. If the project's playbook has the same automation, select the new webhook there too. A new project copies its playbook's automations when it's created.

OnRamp doesn't resend calls it skipped. To test the fix, repeat the event on the project, and then select Refresh in Logs.

Still stuck?

Contact support with the project's name and link, the automation's trigger and action, the webhook's name, the row's Timestamp, and the text from Error.

More in Getting Unstuck Fast