Integrations connect Agentforce Operations to external systems and run automatically
during workflow execution. Use integrations to send workflow data to an external system, get data
from an API, or save files to cloud storage without any user interaction.
Required Editions
License Required
This feature is a workspace that’s external to your Salesforce org and requires
an Agentforce Operations license.
To purchase an Agentforce Operations license, contact your Salesforce account
executive.
How Integrations Work
Workspace admins configure integrations from the Admin page and then blueprint builders add
those integrations to blueprints as automation tasks. When a workflow reaches an automation task,
Agentforce Operations runs the integration automatically by calling an API, saving a file, or
exchanging data. Then Agentforce Operations passes the result forward to the next task.
Integrations run in the background and don't require users to act. All requests include
automatic metadata headers that identify the originating workflow, stage, and task.
Available Integrations
SharePoint
Save files from a workflow directly to a SharePoint folder. Agentforce Operations connects
to SharePoint by using OAuth 2.0 via an Azure app registration. To set up, see Set Up a SharePoint Integration in Agentforce Operations.
Custom HTTP
Call any HTTP API to send or get data during workflow execution. Supports GET, POST, PUT,
PATCH, and DELETE methods, OAuth 2.0 and bearer token authentication, JSON and Form Data
payloads, and jq syntax for response extraction. To set up, see Custom HTTP Integrations in Agentforce Operations.
Custom HTTP Integrations in Agentforce Operations With Custom HTTP integrations Agentforce Operations can call HTTP APIs to exchange data with external systems during workflow execution. Use them to send workflow data to an API, get data from an API for use in a workflow, or search external datasets based on workflow parameters.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.