Testing Agents

    Before an agent goes live, you need to make sure it actually does what you built it to do. Testing is where you validate that, and deployment is how you put it to work.

    Testing an agent

    Before you start testing, it helps to understand how the test setup works.

    Your agent's tools need parameter values to function. For example, a tool that fetches a CRM record needs to know which module and which record ID to use. The testing flow asks you to decide two things: where each parameter value should come from, and what the actual values are for your test run.

    Where parameter values come from

    Each parameter can be sourced in one of three ways:

    • Model: The agent figures out the value on its own based on the instructions and conversation context. Use this when the parameter is something the agent can reasonably infer.
    • On-Trigger: The value gets passed dynamically when the agent is triggered. For example, if the agent is deployed as a button on a CRM record page, the record_id would be passed at trigger time. During testing, you'll need to provide these values manually since there's no actual trigger.
    • Constant: A fixed value you define upfront. Use this when the parameter is always the same. For instance, if the agent only works with the Deals module, you'd set module_api_name as a constant with the value "Deals."

    Some parameters are optional. You can uncheck them if they're not needed for your test scenario.

    Testing steps

    1. From the agent details page, click Test Agent in the top right.
    2. Configure the necessary connections.
    3. The Tools Param Mapping panel opens.
    4. For each parameter listed, select its source: Model, On-Trigger, or Constant.
    5. Click Edit Parameters at the top of the test window.

    For any parameters set to On-Trigger, enter the test values here (e.g., a real record_id from your CRM).

    1. Type a prompt in the chat and click Generate.

    Make sure the prompt aligns with the tools and role you've configured.

    1. Review the agent's response.

    If something's off, adjust the instructions, tweak parameter mapping, or try a different prompt.

    1. Use Clear Chat to wipe the conversation and test different scenarios without previous context carrying over.

    Iterate until the outputs are consistently reliable. That's your sign the agent is ready to deploy.

    The Copy Parameters button in the Edit Parameters panel copies the tool names, parameters, and values in a format you can use as systemArgs in the request body when deploying the agent via API.

    Testing connections

    If the agent's tools need connections to services (like CRM or Desk), those connections need to be in place before testing. You can set these up in two ways:

    • From the agent details page: Click Manage Connections next to the Tools section to associate connections with the agent's tools.
    • From Settings > Connections: Create connections ahead of time and they'll be available when you test.

    See Connections for the full walkthrough.

    PREVIOUS

    UP NEXT