Skip to main content

Workflow Functions

Business

Workflow functions are in-built framework functions that enables you to interact with different entities like datasources, queries, external systems, and human-in-the-loop interactions. This page provides information about the workflow functions available in Appsmith, including their signatures, parameters, and usage examples.

executeWorkflow()​

The executeWorkflow() function serves as a central control unit for executing workflows and marks the starting point of the workflow execution within Appsmith. This function allows you to create a workflow logic for execution of tasks.

Signature​

executeWorkflow(data: JSON): Promise<boolean>

Parameters​

Below are the parameters required by the executeWorkflow() function to execute:

data JSON​

The parameter data holds the data passed from your App to trigger and process the workflow. For example, consider the following data passed to the workflow where data holds the body of the post request when triggered via webhook, and holds Trigger Data property of the Trigger Workflow query when workflow is executed from an Appsmith app.

  {
    "userId": 123,
    "action": "updateProfile",
    "data": {
      "firstName": "John",
      "lastName": "Doe",
      "email": "john.doe@example.com"
    }
  }

In your workflow, you can access properties within the data object like userId using dot notation. To access the userId, use data.userId.

Return type​

The executeWorkflow() returns a Promise that resolves to a boolean value, either true or false, indicating the success or failure of the workflow execution.

assignRequest()​

The assignRequest() function is part of the workflows object within the global appsmith object in Appsmith. It allows you to create a decision point in a workflow that require users intervention. The decision point is created as a pending request in the workflow and can be accessed later in your apps to enable users to take action by using Get requests workflow query. Once you create pending requests, the workflow pauses and awaits for user action.

Signature​

assignRequest({requestName: string, message: string, resolutions: string[], metadata:{key: string, value: any}, requestToUsers: string[], requestToGroups: string[] }) : Promise<JSON>

Parameters​

Below are the parameters required by the assignRequest() function to execute:

requestName String​

The name of the request, which serves as its identifier within the workflow. Give a unique name to the request, and use it to filter requests as part of Get requests workflow query by adding it in the Request name attribute.

message String Optional​

A descriptive message associated with the request, providing more context for users. For example, when creating a refund request, you might include a message like "Refund request raised by User 1".

resolutions String[]​

Represents the possible actions a user can take on the request. The applicable resolution passed to the Resolve requests workflow query to apply the selected resolution. For example, ['Approve', 'Reject'].

metadata JSON Optional​

Add data that may be needed to process the request or display more information to the user in your app. For example, you can include a unique identifier for the record associated with the request. Use the identifier in your app to fetch and show the details to user.

requestToUsers String[]​

The requestToUsers parameter allows for targeted assignment of requests to specific Appsmith users. It specifies an array of emails for users to whom the pending requests will be assigned. The users specified here will be able to take action and resolve the pending request. These users need to be a part of the Appsmith instance for assigning the request to them. It's mandatory to supply either requestToUsers or requestToGroups atribute for request assignment.

requestToGroups String[] Optional​

The requestToGroups parameter allows for targeted assignment of requests to specific User groups in Appsmith. If specifies the user group names to which the request will be assigned for resolution. When specified, the request will be assigned to all the users belonging to the groups. Each group name must be configured in your app and have appropriate permissions to perform actions. It's mandatory to supply either requestToUsers or requestToGroups atribute for request assignment. The workflow restarts upon the first action taken by any user within the assigned group.

Return type​

The assignRequest() function returns a Promise in a JSON format representing the generated response. The response includes the following data:

workflowInstanceId String​

Represents the unique identifier for the workflow instance.

resolution String​

Indicates the resolution applied to the request based on the user action.

payload JSON​

It holds the data from the metadata attribute used during the processing of the Resolve Requests workflow query.