Skip to main content

Troubleshooting

Quick Overview

Common integration errors and how to fix them, plus notes on workspace scoping, hidden test URLs, and webhook secrets.

Troubleshooting​

  • Name already exists: integration names must be unique within a workspace. Pick a different name.
  • Webhook returns 4xx: the delivery is logged as failed and is not retried. Fix the endpoint and use Send Test.
  • Webhook times out: the endpoint must respond within 10 seconds.
  • Meta CAPI Send Test fails: a Test Event Code is required for test events. Check the access token and dataset ID.
  • Meta CAPI lead not sent: check the per-integration block reason (channel not supported, inactive, already sent, in progress, no inbound message).
  • Yeastar test fails: verify the base URL and OpenAPI credentials.
  • N8N or WaaPY Bot not appearing: publish the flow in that tool first. The row is created by the backend.

Saving an integration whose name already exists in the workspace is rejected. WaaPY shows an error toast and keeps the wizard open on the review step.

Error toast when the integration name already exists

Delivery failures are recorded in Integration Logs. Open the clock icon on the integration card to see the status code and the error detail for each attempt.

Notes​

  • Integration data is scoped to the current workspace.
  • N8N test-mode webhook URLs (/webhook-test/) are hidden from the list.
  • Webhook secrets are 64 hexadecimal characters (32 random bytes) and are shown only once.