Setting up an HTTP Action

Last updated: February 25, 2026

An HTTP Action is a specific API call your AI Agent can make to an external system — for example, retrieving an order's status, initiating a return, or looking up a customer's subscription. Actions are defined inside an Integration Group and unlocked inside Policy steps.

Before creating an Action, you need to have an HTTP Integration set up. See Setting up an HTTP Integration for how to connect Engaige to an external API.

The # symbol — dynamic parameters

Use #parameter_name anywhere in a URL path or request body to mark a value as dynamic. When the agent calls the action, it fills in these values from the conversation context — for example, the customer's order number or email address.

Example: if your endpoint path is /orders/#order_id/cancel, the agent will substitute #order_id with the actual order number at runtime.

Step 1 — Create the Action

  1. From the Integration Group page, click + New action. Alternatively, go to Actions in the left nav and click New action → HTTP Request.

  2. Select the Integration Group this action belongs to.

  3. On the API Connection page, configure the request:

    • Choose the HTTP method (GET, POST, PATCH, etc.).

    • Enter the endpoint path — this is appended to the Integration's base URL. Use # for dynamic path segments (e.g. /orders/#order_id).

    • Add any required static headers or request body fields. Use # for dynamic body values too.

  4. On the Action Input page, write a clear description for each #parameter. These descriptions are what the AI agent reads to understand what value to fill in — be specific. For example: "The customer's order number, typically provided in the conversation."

  5. On the Test page, enter sample values and run a live test to confirm the endpoint returns the expected response.

The endpoint path is appended to the Integration's base URL. If your Integration base is https://api.mystore.com and your Action path is /orders/#order_id, the full request URL will be https://api.mystore.com/orders/#order_id.

Step 2 — Unlock the Action in a Policy Step

HTTP Actions are not available to the agent by default — they must be explicitly unlocked inside a Policy step. The agent can only call an action when it is actively in a step that lists that action.

See 📄 Mastering Policies: Steps, Scenarios & Logicfor how to assign an action to a policy step.

Tips

  • Keep Action names short and action-oriented (e.g. get_order_details, cancel_order) — the agent uses the name to decide when to call it.

  • Write parameter descriptions from the agent's point of view: the more specific, the more reliably the agent will fill in the right value.

  • Use the Test page to catch authentication errors or wrong endpoint paths before adding the action to a policy.