Integration Definition Actions

Perform the asynchronous operation configured in an Integration Definition without blocking the invoking flow. The results of the asynchronous operation are published in a platform event. The calling flow can wait for the Platform Event using a pause step if required. The asynchronous operation is typically an API call.

These actions are available in API version 57.0 and later.

Supported REST HTTP Methods 

URI: /services/data/vXX.X/actions/standard/industriesSendApexAsyncRequest

Where XX.X is the latest API version.

Formats: JSON, XML

HTTP Methods: POST

Authentication: Authorization: Bearer TOKEN

Where TOKEN is a variable.

Industries: Send Apex Async Request 

Perform an asynchronous operation that calls an Apex class on the backend. This class must implement the ServiceIntegrationProvider interface.

Inputs

InputTypeDescription
RequestGuidStringA unique identifier for the request. The value can be any string.
In the Integration Definition in Setup, setting the RequestGuid to this value is recommended:
{!$Flow.InterviewGuid}
This creates an automatically generated ID based on the flow that calls the action.
IntegrationDefinitionDevNameStringThe Developer Name of the Integration Definition in Setup that specifies the Apex class to call.
ContextRecordIdStringThe ID of the record that provides input data for the Apex class. This is the ID of an object of the type that the Apex class accepts. The default Apex class accepts a SvcCatalogRequest object.

Sample Input

1{
2   "RequestGuid": "1d926919bc721ceea1bde0918184795922c0-7f5f",
3   "IntegrationDefinition": "Account Lookup",
4   "ServiceProcessId": "001RO0000045yv4YAA"
5}

Outputs

This action has no outputs.

Error Scenarios

Error ScenarioAPI Error CodeError Message
A parameter is missing a value.REQUIRED_FIELD_MISSINGYou must specify a value for the {0} parameter.
Input parameters have incorrect data types.INVALID_TYPEThe value specified for the {0} parameter is the wrong data type. Specify a value with a {1} data type and try again.
More than one request is sent to the invocable action.TOO_MANY_REQUESTSThis action can process only one record at a time. Provide a single {0} for the {1} parameter and try again.
An input parameter is incorrect.INVALID_INPUTThe value “{0}” for the {1} parameter is invalid.
The ID specified for a field is invalid.INVALID_INPUTSomething’s not right with the ID “{0}” specified for the {1} parameter. Check it and try again.

Industries: Send External Async Request 

Perform an asynchronous operation that calls an external service via a REST API. It can also use an Integration Procedure for preprocessing, postprocessing, or both.

Inputs

InputTypeDescription
InputProcessorContextIdStringThe ID of the record that provides payload data for the external service when the input configuration defined in the Integration Definition runs.
OutputProcessorContextIdStringThe optional ID for the record updated after the output configuration defined in the Integration Definition runs.
RequestGuidStringA unique identifier for the request. The value can be any string.
In the Integration Definition in Setup, setting the RequestGuid to this value is recommended:
{!$Flow.InterviewGuid}
This creates an automatically generated ID based on the flow that calls the action.
IntegrationDefinitionDevNameStringThe Developer Name of the Integration Definition in Setup that specifies the external service to call.

Sample Input

1{
2   "InputDataContextId": "001RO0000045yv4YAA",
3   "OutputDataContextId": "001RO0000045yv4YAA",
4   "RequestGuid": "1d926919bc721ceea1bde0918184795922c0-7f5f",
5   "IntegrationDefinition": "Onfido- IDV Application ID generation"
6}

Outputs

This action has no outputs.

Error Scenarios

Error ScenarioAPI Error CodeError Message
An unexpected exception occurs while the program process runs.UNKNOWN_EXCEPTIONSomething went wrong when running the “{0}” external service. Try again later.
Input parameters have incorrect data types.INVALID_TYPEThe value specified for the {0} parameter is the wrong data type. Specify a value with a {1} data type and try again.
More than one request is sent to the invocable action.TOO_MANY_REQUESTSThis action can process only one record at a time. Provide a single record ID for the {0} parameter and try again.
An input parameter is incorrect.INVALID_INPUTThe value “{0}” for the {1} parameter is invalid.
The external service is incorrect.INVALID_INPUTThe “{0}” value specified for the integrationDefinition isn’t a valid external service developer name. Check it and try again.