Action Debugger
Last updated: May 15, 2026
Use the Action Debugger to test whether actions trigger correctly and return the right data.
It helps you inspect the full action flow before you use it in live conversations.
Use Action Debugger to test action trigger logic and API output.
Use Simulator to test the full conversation flow around those actions.
Open the Action Debugger
Go to Workspace → Integrations.
Click Debug.
What to test
Enter a message that should trigger an action.
Use realistic examples from your workflow, such as:
checking order status
finding a customer record
looking up shipment details
canceling an order
What to inspect
The Action Debugger shows:
which action triggered
the API endpoint that was called
the parameters sent
the response returned by the API
In the example below, Aissist first calls getCustomerOrders, then calls getTrackingDetails.
Fix common issues
If the action does not trigger:
review the action trigger scenario
make sure the action name and description match the intended use case
make sure the action is linked to the right sub agent, if applicable
make sure the test input matches the expected trigger pattern
If the parameters are wrong:
improve the parameter names
improve the parameter descriptions
add clearer guidance about expected values
include exact formats, examples, or allowed values when needed
If the response is hard to use:
update the action instructions
define summarization in Response Processing to summarize the response
refine any Response Processing instructions
return only the fields Aissist needs when possible
When to use it
Use the Action Debugger whenever you:
create a new action
update an existing action
change an integration
troubleshoot unexpected action behavior
Best practice
Test each action with multiple realistic inputs.
Verify both the trigger and the returned data before you move into live workflows.
Once the action works here, test the full workflow in Simulator.
Last updated