Aissist.io
  • Aissistant
  • Tutorial
    • Quick Start
    • Turn assets into AI
      • Domain/Subdomain
      • Web Page
      • Google Drive Doc
      • Documents
      • Asset Debugger
    • Create Sub Agents
    • Deploy Gateway
    • Tune Instructions
      • Tweak global instructions
      • Enhance with Sub Agents
      • Refine assets
    • Teach AI with Examples
    • Streamline with human team
    • Auto-Pilot, Auto-Draft, Co-Pilot
    • Managing Points
    • Instructions, Assets, and Sub Agents
    • Simulator
    • In-note command
    • Additional Aissistant Building Tips
  • Integrations
    • Shopify
    • Woocommerce
    • Adobe Commerce (Magento 2)
    • Restful API
    • AWS Lambda
    • Action Debugger
  • Gateways
    • Front
    • Gorgias
    • Intercom
    • Zendesk
      • Zendesk Conversation (messaging)
    • Hubspot
    • Salesforce
    • Kustomer
  • Use cases
    • Sales
    • Service
  • Success Metrics
  • FAQ
  • Release notes
Powered by GitBook
On this page
  1. Integrations

Action Debugger

PreviousAWS LambdaNextGateways

Last updated 1 month ago

Aissist provides an Action Debugger to help you easily test and fine-tune your Smart Actions. With just a few clicks, you can check whether your actions are triggered correctly and if the right information is being passed and returned.


πŸš€ How to Access the Action Debugger
  • Log into your Aissist.io console.

  • Go to Workspace β†’ Action.

  • Click the β€œDebug” button located in the top right corner.

πŸ” How to Use the Action Debugger
  • In the Action Debugger, simply input a test message β€” just like a user would during a real conversation.

  • The system will simulate the interaction and show:

    • Which action is triggered (if any)

    • The API endpoint being called

    • The parameters used

    • The response returned by the API

  • In the following example, when a user asks for their order status and provides their email, Aissistant first calls getCustomerOrders to retrieve the user's orders, and then follows up with getTrackingDetails to fetch detailed tracking information.

🧠 How to Troubleshoot and Adjust
  • If the action is not triggered: βž” Review and adjust the trigger scenarios defined for your action. (It may not recognize the message as matching the current setup.)

  • If the parameters are incorrect: βž” Update the description of the parameters in your action settings. (Clearer descriptions help Aissist extract the right values.)

  • If the returned response isn't ideal: βž” You can adjust your Smart Action’s post-processing instructions to better handle the information received.


⚑ Why Use the Action Debugger?

  • Quickly test your actions without needing live user interaction

  • See exactly what Aissist is sending and receiving

  • Spot errors early and fix them before going live

  • Fine-tune your instructions for better accuracy and performance


Tip: Use the Action Debugger every time you create or update a Smart Action β€” it saves time and ensures your integrations work exactly as you expect!