Skip to main content

Troubleshooting Custom Webhook Actions in Workflows

This guide explains how to identify and fix common issues with Custom Webhook actions in Kyrios workflows, including failed requests, incorrect data mapping, authentication errors, and skipped executions.

Updated over 3 months ago

Who this is for / When to use

This article is for users building workflows with Custom Webhook actions who see failures, missing data, skipped steps, or unexpected behavior when sending data to external systems.


What a Custom Webhook action does

A Custom Webhook action sends data from Kyrios to an external endpoint using a configurable HTTP request, including method, URL, headers, query parameters, authorization, and a custom request body.


Why a webhook action is marked as “Failed”

A webhook action is marked as failed when the receiving server returns an error response or cannot be reached.

How to fix

  • Verify the webhook URL is correct and reachable

  • Confirm the external server is online

  • Ensure the selected HTTP method is supported by the endpoint

Steps

  1. Copy the webhook URL and test it using a request testing tool.

  2. Open Workflow History and review the error message returned.

  3. Confirm the method (POST, GET, PUT, DELETE) matches the external API requirements.


Why the webhook is not sending the correct data

Incorrect or missing custom values cause payloads to be incomplete or incorrect.

How to fix

  • Review all mapped fields in headers, query parameters, and body

  • Use the Custom Values selector to insert valid variables

Steps

  1. Open the webhook action in the workflow.

  2. Expand the Raw Body, Headers, or Query Parameters section.

  3. Insert values using the Custom Values picker instead of typing manually.


Why headers or query parameters are not recognized

Headers or query parameters fail when keys or values are missing, incorrectly formatted, or unsupported by the receiving system.

How to fix

  • Confirm required keys and values match the external API documentation

  • Remove extra spaces or empty fields

Steps

  1. Expand Headers or Query Parameters in the webhook action.

  2. Ensure every row has both a key and a value.

  3. Save the workflow and retest with a test contact.


Why authentication errors occur

Authentication fails when authorization type, token, or API key is incorrect or expired.

How to fix

  • Confirm the correct authorization type is selected

  • Regenerate or re-enter credentials if needed

Steps

  1. Open the Authorization dropdown in the webhook action.

  2. Select the required method (None, Basic Auth, Bearer Token, or API Key).

  3. Re-enter or refresh the token or key.


Why the webhook appears to be skipped

A webhook may be skipped when retries fail silently or the external system rejects the request without a visible error.

How to fix

  • Check workflow execution logs for retry attempts

  • Validate authentication and endpoint availability

Steps

  1. Open the contact’s Workflow History.

  2. Review response codes and retry behavior.

  3. Fix configuration issues and re-add the contact to the workflow.


Why the external system receives data but takes no action

The payload structure does not match what the receiving system expects.

How to fix

  • Match request structure, headers, and format exactly to the external API requirements

Steps

  1. Verify Content-Type and other required headers.

  2. Confirm whether data should be sent as JSON, query parameters, or headers.

  3. Send a test payload using a known working sample.


Why webhooks fail after previously working

Changes to custom fields or values used in the webhook mapping can break newer executions.

How to fix

  • Review recent field or custom value changes

  • Re-map fields that no longer exist

Steps

  1. Open the webhook action and review all dynamic fields.

  2. Confirm the referenced fields still exist and contain data.

  3. Save the webhook and retest.


How to test a webhook before going live

Testing with controlled data confirms the webhook configuration is valid.

How to test

  • Use a test contact with known values

  • Send payloads to a mock or request listener endpoint

Steps

  1. Create a test contact.

  2. Manually add the contact to the workflow.

  3. Monitor execution logs and payload output.


Custom Webhook vs standard integrations

A Custom Webhook provides full control over request structure, while standard integrations use pre-built connections.

  • Standard integrations: Preconfigured connections with minimal setup

  • Custom Webhooks: Fully customizable requests for any API-enabled system


Common issues and quick fixes

  • Webhook fails immediately: Check URL and HTTP method

  • Missing data: Reinsert values using Custom Values picker

  • Authentication error: Refresh tokens or API keys

  • No response from server: Confirm endpoint availability

Did this answer your question?