Actions
Let your organization's AI call configured HTTPS endpoints during conversations
Actions register HTTPS endpoints as tools for the organization’s AI. During a conversation, the AI uses an active Action’s name and description to decide whether it is relevant, calls the endpoint, and receives the response as tool output.
Actions are available on Starter and Pro. Free organizations cannot create an Action. Starter can keep up to 2 Actions active at once, and Pro up to 10; drafts and inactive Actions do not consume an active slot. See Billing and usage for the other plan limits.
Create an action
Open Harness → Actions and select New action. The current form contains these settings:
| Field | What it controls |
|---|---|
| Name | The tool name the AI sees. Start with a lowercase letter and use only lowercase letters, numbers, and underscores, such as check_service_status. The maximum length is 50 characters. |
| Description | A short explanation of when the AI should use the Action, up to 200 characters. |
| Method | The outbound HTTP method: GET or POST. |
| HTTPS URL template | The public target URL. Use a placeholder such as {order_id} to send a matching Param in the path. Other Params are sent in the query string. |
| Authentication | No authentication, a Bearer token, or an API key header. Saved secrets are encrypted and cannot be viewed again. |
| Params and JSON Body | Dynamic string, number, or boolean inputs that the AI collects before calling the endpoint. JSON Body fields are available for POST. |
Select Save draft after completing the required name and URL. Saving new or changed configuration leaves the Action disabled until that exact version passes a test.
Test and enable an action
Select the saved Action, enter values for any configured inputs, and choose Run test. A test makes a real request and writes a redacted execution record. After a successful test, turn on Enable this action. The organization’s plan controls how many Actions can be active at once.
If the organization uses a custom AI provider, its connection test must also confirm tool-calling support before an Action can remain active. See AI providers.
Enable, disable, edit, or delete
Select an action to view its method, URL, and description. From the action header you can:
- Turn Enable this action on or off
- Edit the settings listed above
- Open the call logs
- Delete the action
Only Actions that are active, not plan-locked, and successfully tested at their current configuration version are exposed to the organization’s AI. The available-Action list is cached for up to 60 seconds, so an activation or configuration change may take that long to reach a new AI turn.
Runtime limit
Every outbound Action request has a hard timeout of 5 seconds and accepts at most 20 KB of response data. Only HTTP 200 is treated as a successful call. A failure is returned to the AI as tool output so the conversation can continue, and the attempt is written to the call log.
Call logs
Open Call logs on a selected Action to inspect matching entries from the organization’s latest 50 Action calls. Each row shows:
- HTTP status or a failure code
- Duration in milliseconds
- Call source
- Relative call time
- A link to the conversation when the call came from one
Successful and failed outbound requests are both recorded.
To test an Action in its real conversation path, first install the widget, ask a question that matches the action description, and then inspect the action’s logs.