Test and edit custom actions

Use the Test button to run a real call, read the response, and adjust, enable, or delete the action without affecting the conversation.

Jun 26, 2026

Watch this step in the video · Custom actions: parameters, variables and testing

Why test first

Before letting the agent use an action in front of a customer, it's worth testing it. The Test button runs a real call to your API and shows the response as-is, so you can confirm that the URL, headers, and mapping work.

Requirement

The Test button is only enabled after you save the action at least once. If you're creating a new action, click Save action first.

Steps to test

  1. Open AI Agents, enter the agent, and go to the Custom actions tab.
  2. Click the pencil (Edit) on the action you want to test.
  3. At the bottom of the form, click Test.
  4. Wait for the result: the button shows Testing... and then a panel with the response appears.

How to read the result

  • A green dot and Response OK mean your API responded successfully (HTTP 2xx).
  • A red dot and Failed mean an error: the panel shows the HTTP code or the failure message.
  • The full JSON body is displayed. Compare it with the Field to extract you configured to confirm it points to the right value.

The Test button is limited to 10 runs per minute per user. If you exceed it, wait a few seconds before retrying.

Edit an action

  1. In the list, click the pencil (Edit).
  2. Change whatever you need: identity, method, URL, headers, body, parameters, or the field to extract.
  3. Click Save action. Changes apply immediately to the next conversations.

Enable, disable, or delete

  • Enable/disable: use the switch on each row. A Disabled action is still saved but the agent won't use it — ideal for pausing without losing the setup.
  • Delete: click the trash icon. It asks for confirmation because it cannot be undone.

If it doesn't work

  • The Test button is disabled: you haven't saved the action yet; click Save action.
  • Failed with a 401 or 403: check the Authorization header and that the token is valid.
  • Failed with a timeout: your API took longer than the configured Timeout (s); raise it (up to 60 s) or check the endpoint's performance.
  • Response OK but the agent doesn't use the data: adjust the Field to extract or the action's Description.

Tip: test with real contact data to catch formatting issues (e.g. phone numbers or emails) before going live.

Tip: if you're making big changes, disable the action while you adjust it so the agent doesn't use it half-configured.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp