Actions

Actions enable agents and workflows to interact with external applications such as Gmail, Jira, Slack, GitHub, Salesforce, and many others. Instead of creating custom HTTP integrations, you can create reusable action tools using the platform’s prebuilt integrations. An action tool combines an integration, one of its supported actions, an authentication profile, and optional default parameter values. Once created, the tool can be used across multiple agents and workflows.

​

How Actions Work

• Configure an integration for the external application you want to connect to.
• Create an action tool using the configured integration.
• Select the action to expose and associate an authentication profile.
• Add the configured action as a tool to an agent or workflow.
• At runtime, the agent invokes the action to interact with the external application and uses the returned response to continue execution.

​

Prerequisite

Before you create an action:

• Integate the external application (for example, Gmail, Jira, Slack, or Salesforce) with Agent Platform.
• Configure a valid authentication profile if the integration requires authentication to work.

​

Create an Action

To create an action tool:

1. Log in to the platform and go to Tools.
2. Click New Tool and select Action.
3. Select an Integration. The integration catalog displays all supported providers grouped into categories such as:AI & Development, Communication, CRM & Sales, and others. Use the search box or browse the categories to locate the required integration.
4. Click Continue. T
5. Next, configure the Action by providing the required information. Basic Information: Provide a unique name to identify the tool and an explanatory description that helps an agent to determine when to invoke this tool. Integration & Action Select the connector action that the tool executes. The supported actions are available in the menu.

   Field	Description
   Integration	The selected provider.
   Action	The operation to execute, such as Send Email, Create Issue, or Post Message.
   Auth Profile	Credentials used when the tool executes.

   Some integrations require authentication before the available actions can be retrieved. Authentication Profile
   • Authentication profiles contain the credentials required to access the selected integration.
   • Select an existing authentication profile or create one if necessary.
   • The selected credentials are automatically used whenever the tool runs.
   Input Parameters After an action is selected, the platform automatically loads its required input schema. Configure the parameters as required. Each parameter displays:
   • Parameter name
   • Data type
   • Required or optional status
   • Description
   • Default value
   You can optionally provide default values for any parameter.
   • If the agent supplies a value during execution, that value overrides the configured default.
   • Leave a parameter empty if you want the agent to determine its value at runtime.
   Output Parameters Choose how the connector response should be returned. You can:
   • Return the complete connector response.
   • Return only selected fields by defining a custom output. Use custom output when your agent needs only a subset of the connector response.
   Variable Namespaces Variable namespaces determine which runtime variables are available to the tool during execution. Select the namespaces that the tool should be able to access. Scenario Fixtures Scenario fixtures provide deterministic responses during testing and evaluations. Use fixtures when you want repeatable tool behavior without invoking the external service.
6. Save the Action. Click Save to add the action to the project.

The action appears under the Actions tab in the Tools library and can now be assigned to agents or used within workflows.

​

Edit an Action

To modify an existing action:

1. Log in to the platform and go to Tools.
2. Open the required action.
3. Select the Configuration tab and update as required.

​

Test an Action

Use the Testing tab to verify that the configured action executes successfully before assigning it to an agent. Testing validates:

• Authentication.
• Required parameters.
• Connector execution.
• Response returned by the external application.

Use testing to ensure the action behaves as expected before deploying it in production.

​

Assign an Action to an Agent

After creating an action:

1. Open the required agent.
2. Navigate to Tools.
3. Add the required action.

The agent can invoke the action whenever it determines that the action is appropriate to answer a user’s request. For example:

​

Use an Action in a Workflow

Actions can also be used from workflow Tool steps. When used in a workflow:

• The integration is inherited from the action tool.
• The selected action is reused.
• Authentication is reused.
• Input parameters can be mapped to workflow variables.
• Output can be consumed by subsequent workflow steps.