# Action Debugger

*Last updated: May 5, 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.

### Open the Action Debugger

1. Go to **Workspace → Action**.
2. 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`.

<figure><img src="/files/WkjutcifXNBcDHCzdv9w" alt=""><figcaption><p>Example Action Debugger view</p></figcaption></figure>

### Fix common issues

If the action does not trigger:

* review the action trigger scenario
* make sure the description matches the intended use case

If the parameters are wrong:

* improve the parameter names
* improve the parameter descriptions
* add clearer guidance about expected values

If the response is hard to use:

* update the action instructions
* refine any post-processing guidance

### 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.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://doc.aissist.io/integrations/action-debugger.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.