Updated August 26, 2024

In addition to using the Audit Logs in ZappyChat to monitor interactions and troubleshoot issues, there’s another important place where you can detect errors: the Execution Logs of Workflow 1, specifically the "Send Message to AI" workflow, in your GoHighLevel (GHL) subaccount. These logs can provide valuable insights when the AI is not responding or if the ZappyChat Audit Logs don’t show any errors.

Here’s how you can use the Execution Logs to troubleshoot potential issues:

When to Check the Execution Logs

If the AI is not replying, and the ZappyChat Audit Logs don’t provide any clues (e.g., there are no logs or no error messages in the ZappyChat app), the next step is to check the Execution Logs for Workflow 1 in GHL.

How to Access and Use Execution Logs

1. Navigate to Workflow 1:
   • Log in to your GHL account and go to the Automations section.
   • Locate and open Workflow 1 (typically named "Send Message to AI").
2. Access the Execution Logs:
   • Within Workflow 1, look for the Execution Logs tab. This tab contains records of all actions that the workflow has attempted to execute.
3. Search for Webhook Action Logs:
   • In the Execution Logs, focus on the logs related to the Webhook Action.
   • Look for the Event Status of these webhook actions to determine if they were executed successfully.

Interpreting the Logs

• Missing Contact Message:
  • If the Event Status does not show any error but the event message does not include the message sent by the contact, this indicates that the webhook failed to deliver the data to ZappyChat. This is often a sign of a missing Calendar ID or other required information.
  • Example: If the webhook does not show any specific error codes (like 400 or 401) but the contact’s message is not present in the logs, it’s likely that the Calendar ID is missing or incorrectly configured.
• Specific Error Codes:
  • If the webhook action shows a specific error code:
    • 400 Error: This typically indicates a bad request, which can happen if the data sent is incorrectly formatted or missing required fields.
    • 401 Error: This indicates an authentication issue, such as an invalid API key or lack of proper authorization.
  • Solution: If you see these or other error codes, the best course of action is to contact ZappyChat Support at [email protected] for assistance.

Example Scenario

• Scenario: The AI is not responding to messages, and there are no logs in ZappyChat.
• Steps to Diagnose:
  1. Check the Execution Logs in Workflow 1.
  2. Look at the Webhook Action logs and see if the contact’s message appears in the Event Status.
  3. If the message is missing, double-check the Calendar ID or other necessary fields to ensure they are correctly set.
  4. If an error code is present, contact ZappyChat Support for help.

Conclusion

The Execution Logs in GHL’s Workflow 1 are a crucial tool for diagnosing issues when the ZappyChat Audit Logs don’t show errors or when the AI fails to respond. By carefully examining the Webhook Action logs and Event Status, you can identify missing data or specific error codes, helping you to quickly resolve issues and ensure your bot operates smoothly. When in doubt or if the error persists, don’t hesitate to reach out to ZappyChat Support for further assistance.