You are here:
Create a Custom HTTP Integration in Agentforce Operations
Create a Custom HTTP integration to connect Agentforce Operations to an external API. Use Custom HTTP integrations to send or retrieve data during workflow execution.
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. |
| Role or Access Needed | |
|---|---|
| To manage integrations in Agentforce Operations: | Admin role or Integration Admin role |
To create a Custom HTTP integration, configure the request settings, configure how to extract data from the response, and then test the connection. After you create the integration, it's available to use in blueprints as an automation task.
- In the navigation sidebar, click Admin.
- Click the Integrations tab.
- Click + Add integration.
- Select Custom HTTP and click Next.
- Enter a name for the integration.
-
Optionally, for Type, select an authentication type and provide credentials.
- Bearer Token
- OAuth 2.0
- For Base URL, enter the root URL of the API. For example, https://example.com.
-
For Method, select the HTTP method that represents the action you want to take.
- To get data, select GET.
- To submit data and create a resource, select POST.
- To replace a resource with new data, select PUT.
- To update specific fields in a resource, select PATCH.
- To remove a resource, select DELETE.
- For Path, enter the path to the specific API endpoint. For example, /api/suppliers.
-
Optionally, for Headers, click + Add header and enter a key and
value for each header required by the API. For each value, select Field
to map to a workflow field or Text to enter a static value.
For example, enter Content-Type as the key and application/json as the value. Agentforce Operations automatically includes metadata headers that identify the originating workflow, stage, and task with every request.
-
Optionally, for Query parameters, click + Add parameter and enter a
key and value for each parameter to append to the request URL. For each value, select
Field to map to a workflow field or Text to
enter a static value.
For example, enter status as the key and active as the value to send
?status=active. -
Optionally, configure the request body.
- For Body (form-data), click + Add value
and enter a key and value for each field to include in the request body. For each value,
select Field to map to a workflow field or Text
to enter a static value.
Note Use Body (form-data) or Body (JSON), not both. - For Body (JSON), click + Add value and
enter a key and value for each field to include in the request body. For each value, select
Field to map to a workflow field or Text to
enter a static value. To create nested JSON, prefix the key with a period. For example,
.order.supplierIdproduces{"order": {"supplierId": "value"}}.
Note Use Body (form-data) or Body (JSON), not both.
- For Body (form-data), click + Add value
and enter a key and value for each field to include in the request body. For each value,
select Field to map to a workflow field or Text
to enter a static value.
-
For HTTP Response, click + Add value and configure each value to
extract from the API response.
-
Enter a JSON Path expression describing where the value is in the
response payload.
For example, to extract a city name from a postal code lookup response, use:
.places[0]["place name"]. To extract the state abbreviation, use:.places[0]["state abbreviation"]. -
Select the Agentforce Operations field to map the extracted value to.
Select a field that matches the data type being extracted. For example, map an array of strings to a multi-select field.
-
Enter a JSON Path expression describing where the value is in the
response payload.
- Optionally, to automatically invite users returned in the response who aren't yet workspace users, select Invite new people if they don't already exist in this workspace .
- Click Next.
-
For Health check, select how often Agentforce Operations should check that the integration
is still connected.
- Disabled
- Daily
- Hourly
- If you selected Daily, for Repeats at, configure the time of day to run the check.
-
If you selected Daily or Hourly, for Health check path, enter the relative path of a health
or status endpoint that the service provides, such as /health or
/status.
Agentforce Operations combines the path with the base URL and sends an unauthenticated GET request on your schedule. The endpoint must return a 200 response. Check the service's API documentation for its health endpoint. If it doesn't have one, select Disabled instead.
- If you selected Daily or Hourly, select who to notify if the health check fails.
-
Click Create.
The integration configuration panel closes.
- In the integration list, find your new integration.
-
Click the three-dot dropdown list next to the integration and select
Edit.
The integration configuration panel opens.
- Open the Test HTTP request section and click Test.
-
Check that the test results match your expectations.
- If the test meets your expectations, close the integration configuration window.
- If the test doesn't work as expected, modify the integration, and save your changes.
The integration is available to use in blueprints. To add the integration to a blueprint, create an automation task and select the Custom HTTP integration.

