#Hey my Post-Call Webhook stopped working, I think I overwrote the webhook node to not have the righ

1 messages · Page 1 of 1 (latest)

split sedgeBOT
#
AI-generated Answer for charidanizard

If your Post-Call Webhook is still not working despite creating a new one and ensuring the HMAC setup is correct, here are a few steps to troubleshoot:

  1. Webhook Delivery Status: Webhooks that fail to deliver successfully 10 times in a row and haven’t had a successful delivery in over 7 days are automatically disabled. Double-check that your webhook is still enabled in the settings.

  2. Server Logs: Review your server logs around the time the call ended to see if there were any incoming requests from ElevenLabs. If there are no logs, it might indicate that the webhook wasn’t triggered or the request didn’t reach your server.

  3. HMAC Validation: Ensure the HMAC secret in your system matches exactly with what’s set in ElevenLabs. Even small mismatches can cause authentication issues.

  4. Webhook Assignment: Verify that the webhook is properly assigned to the agent in the Post-Call Webhook section of the Conversational AI settings. Without this assignment, the webhook won’t trigger.

  5. Test Event: If available, use the "Send test event" button in the webhook settings to confirm the connection and validate the setup.

If none of these steps resolve the issue, it may require deeper technical investigation. You can reach out to the customer support team for further assistance.

worthy elk
#

I just made a powershell request to the webhook with the wsec secret and it triggered the workflow but the agent still isn't even with a new webhook made

split sedgeBOT
#
AI-generated Answer for charidanizard

If your Post-Call Webhook is still not working despite creating a new one and ensuring the HMAC is set up correctly, here are a few steps to verify and troubleshoot:

  1. Webhook Assignment: Double-check that the new webhook is properly assigned to the agent in the Conversational AI settings. Simply creating the webhook isn’t enough—it must be explicitly linked to the Post-Call Webhook section for the agent.

  2. Webhook Event Configuration: Ensure that the webhook is subscribed to the correct event type (e.g., post_call_transcription) in the webhook settings. Without this, the webhook won’t trigger.

  3. Webhook Delivery Logs: While webhook delivery logs aren’t visible in the dashboard, you can test the webhook connection using the "Send test event" button in the webhook settings. This can help confirm if the webhook is reachable.

  4. HMAC Validation: Since your manual PowerShell request worked, it suggests the HMAC setup is correct. However, ensure the HMAC secret in your webhook matches exactly with what’s set in ElevenLabs.

  5. Agent Configuration Timing: If the webhook wasn’t assigned to the agent before the calls were made, the webhook wouldn’t trigger for those calls. Ensure the webhook is assigned before initiating new calls.

  6. Auto-Disable Check: Webhooks are automatically disabled if they fail 10 times in a row and haven’t had a successful delivery in over 7 days. Confirm that the webhook is still enabled in the settings.

If you’ve verified all of the above and the issue persists, it may require deeper investigation. You can reach out to the support team with the following details to help them investigate:

  • The Agent ID
  • The Conversation ID of a recent call where the webhook didn’t trigger
  • Confirmation of the webhook assignment and event configuration

Let me know if you need further clarification!

worthy elk
#

In N8N when setting up the auth, what settings should I use? Header Auth? set up a new Auth and in Connections set it to x-elevenlabs-signature?

split sedgeBOT
#
AI-generated Answer for charidanizard

The content provided does not include specific details about setting up authentication in n8n for your webhook integration. However, here are some general suggestions based on your description:

  1. Header Authentication: If you're using HMAC authentication, you would typically include the x-elevenlabs-signature header in your webhook request. Ensure that the secret key used to generate the HMAC matches the one configured in your ElevenLabs webhook settings.

  2. Connections in n8n: If n8n requires you to define a connection or authentication method, you may need to create a new authentication setup that matches the expected headers and values. Ensure that the x-elevenlabs-signature header is properly configured to validate the incoming requests.

  3. Testing the Webhook: Since your PowerShell request successfully triggered the workflow, it suggests that the webhook itself is functional. Double-check the agent's configuration and ensure that the webhook URL is correctly set in the ElevenLabs tool.

If the issue persists, you might want to:

  • Verify the webhook configuration in ElevenLabs to ensure it points to the correct n8n URL.
  • Check the dynamic variable descriptions in your agent setup to ensure all required data (like full name) is being sent.
  • Review the tool's trigger settings and agent prompt for any misconfigurations.

For further assistance, you can also consult the n8n or ElevenLabs community for integration-specific guidance.

worthy elk
#

I mean it's clearly in the Post-Call Webhook section of the agent. I don't believe I need to prompt it