Custom API Action
Make a custom, authenticated HTTP call to the Salesforce API.
Options
Field | Definition | Type | Required |
---|---|---|---|
Request Type |
These are the supported HTTP request methods, or HTTP verbs, in a custom API call (see HTTP request methods).
|
Dropdown |
TRUE |
Input
Field | Definition | Type | Required |
---|---|---|---|
Relative URL |
The URL address of the web server that you're attempting to call. Specify the relative URL as /{insert_remaining_URL}. You can specify query parameters in the relative URL using "?", or specify the query parameters as an object key pair in the Query input. For example, for the Salesforce API endpoint, https://b6g000001zzq9eag-instance-aa.my.salesforce.com/services/data/v51.0/sobjects/User, the relative URL is /services/data/v51.0/sobjects/User. |
Text |
TRUE |
Query |
The JSON object that determines the action taken at the URL. Example: {"name":"something-urgent"} |
Object or String |
FALSE |
Headers |
The JSON object that determines the content type of the request. This will usually be similar to the following: Example: {"Content-type":"application/json"} |
Object |
FALSE |
Output
Field | Definition | Type |
---|---|---|
Response |
||
Status Code |
Result of the operation. The connector returns an HTTP status code that indicates whether the action taken by the card succeeded or failed. For example:
For a full list of possible status codes, see HTTP status codes. |
Number |
Headers |
Detailed context for the status code, unrelated to the output body. Response headers depend on your selected HTTP request option. Not all headers are response headers. This is similar to {"Content-type":"application/json"}. |
Object |
Body |
Data returned from your selected HTTP request. For example, the data from a GET request. |
Object |