Skip to main content

When to Enable Webhook Monitoring

The decision to enable webhook monitoring depends on whether your webhook endpoint is synchronous or asynchronous:

Asynchronous endpoints accept the webhook request and immediately return a response, but this response only indicates that the request was received—not whether the actual job completed successfully. The real work happens in the background after the response is sent.

Examples of asynchronous endpoints:

  • Databricks workflows - The webhook triggers a workflow run, but the API responds immediately while the workflow executes separately
  • Apache Airflow jobs - The webhook triggers a DAG run, but the response comes back before the DAG completes
  • AWS Step Functions - The webhook starts a state machine execution that runs asynchronously
  • Kubernetes Jobs - The webhook creates a job that runs in the background
  • Make or Zapier workflows - The webhook triggers an automation that may involve multiple steps and external API calls

For these endpoints, webhook monitoring is recommended because:

  • The immediate HTTP response only tells you the job was queued or started
  • You need a way to know when the actual job completes and whether it succeeded
  • Monitoring provides end-to-end visibility of your workflow

Synchronous endpoints process the entire task before returning a response. The HTTP response status and body directly indicate whether the operation succeeded or failed.

Examples of synchronous endpoints:

  • REST API endpoints - most HTTP/HTTPS endpoints wait for processing to complete
  • AWS Lambda functions, Azure Functions, Google Cloud Functions - The function executes completely and returns the result

For these endpoints, webhook monitoring is not recommended because:

  • The HTTP response already provides success/failure information
  • You can see response statuses in the Monitoring tab without additional setup
  • The response time in the Monitoring tab reflects the actual processing time

Without Monitoring Enabled​

If you choose not to enable monitoring (regardless of endpoint type), the Monitoring tab will show:

  • Whether the webhook request was successfully sent
  • The HTTP response status code from your endpoint
  • The response time for the HTTP request
  • Any error messages from failed HTTP requests

This basic monitoring is sufficient for synchronous endpoints but provides limited insight for asynchronous workflows.