Connect and configure agent tools

Tools let a Fast Line Pro agent use external capabilities (for example APIs or bundled integrations) according to the catalog available in your environment. This guide covers the Tools section on the agent card and the Publish step so changes apply to live conversations.

When Needed

  • You want the agent to call external data or services from the tools catalog.
  • You need to disable a tool temporarily without removing it from the list.
  • You must fill in tool parameters when the catalog exposes fields for that tool.

What's Important to Know

  • Available tools come from the Tools catalog in the Fast Line Pro module.
  • Adding, disabling, or removing tools first updates only the agent card in the UI.
  • To apply changes to real agent behavior in bots, click Publish at the top of the agent card.
  • When parameters exist, use actions such as Configure parameters or the Parameters & settings dialog — complete required fields before publishing.

Prerequisites

  • You are logged in with integrator permissions.
  • Fast Line Pro is open (Apps → Fast Line Pro) and you are on the relevant agent card.

Step-by-Step Instructions

  1. On the agent card, open the Tools section.
  2. Open Tools catalog.
  3. Find the tool you need and add it to the agent (items already connected are usually marked Connected).
  4. If shown, open Configure parameters or Parameters & settings and fill in the fields.
  5. In the connected tools list, use the enable/disable switch to control whether each tool is active.
  6. To remove a tool, use the remove action and confirm in the dialog.
  7. Click Publish to save the configuration on the Fast Line Pro side and apply it to subsequent agent calls from scenarios.

What Happens After

After a successful publish, the agent uses the updated tool configuration. If you skip publish, dialogs keep using the last published configuration.

How to Verify It Worked

  • The Tools section shows the expected list and on/off states.
  • After Publish, you see a success confirmation when the UI provides one.
  • Run a test message through your scenario to confirm the agent behaves as expected with the tools.