Execute Custom API
Executes custom code by invoking a custom API. This activity executes custom APIs registered within the Conga RLM system.
Prerequisite: A custom code to be executed must exist within the Conga RLM system and be registered as an API resource
Use Case: Sending a Custom Notification After Contract Termination
When the contract is terminated, the workflow will execute the custom code and use the Custom API to notify legal and compliance teams immediately.
Properties, Entry Criteria and activity information
Properties represent the values used to perform the operations of an activity and Entry Criteria serve as conditions that determine whether an activity should be executed.
Field |
Description |
---|---|
Details | |
Display Name | Enter the name of the activity. |
Reference Name | Enter the technical name of the activity. If left blank, the system automatically generates it based on the value in the Display Name field. The generated name removes special characters, eliminates spaces, avoids consecutive underscores, and joins words with a single underscore. |
Description | Provide a description that is relevant to the activity. |
Properties | |
Custom API |
Select the custom API you want to execute. |
Route |
Select the route for the custom API. (.e.g., /notifications/contractTermination) |
Method |
Select the configured method of the custom API (e.g., GET, POST). |
Request Body |
Enter the request body for the API call if required. |
Query Params |
Add optional parameters to send with the request. (.e.g., status=active) To add multiple parameters, click Add. To remove all parameters, click Remove All. |
Entry Criteria | |
Entry Criteria |
Specify fields and their values:
To add more conditions, click Add Criteria. To remove all conditions, click Remove All. |
Switch to New Entry Criteria | |
Filter Expression |
By default, the application applies AND logic to all criteria. You can adjust this to create more complex logical expressions if needed. You can customize your logic using parentheses, AND, OR, and NOT. For example, if you enter “(1 AND 2 AND 3) OR 4”, the system will evaluate whether all three of the first conditions are true, or if the fourth condition is true. |
Output | |
Activity Output | Specifies the variable that stores the API response for use in later workflow activities.
|
Is Collection | Select this checkbox if the variable contains a collection of values, such as a list or array. Leave it unchecked if the variable holds a single value. This helps the system determine how to process the data, especially during transformations or when passing data between activities. |
Variable Data Type | Use this dropdown to specify the format or structure of the variable's data. Currently, only JSON is supported. Ensures the system interprets and processes the data correctly based on its structure. |