diff --git a/docs/versioned_docs/version-2.50.0-LTS/workflows/logs.md b/docs/versioned_docs/version-2.50.0-LTS/workflows/logs.md index b372b577fa..3b495d44aa 100644 --- a/docs/versioned_docs/version-2.50.0-LTS/workflows/logs.md +++ b/docs/versioned_docs/version-2.50.0-LTS/workflows/logs.md @@ -3,6 +3,14 @@ id: logs title: Logs --- +
+ +
+ Self Hosted +
+ +
+ Once you execute the workflow by clicking on the **Run** button, the logs panel will reflect the execution details of each node. Logs let you easily track the order of execution and check whether the execution of individual nodes is successful. You can click on the top bar of the logs panel to expand or minimize it.
diff --git a/docs/versioned_docs/version-2.50.0-LTS/workflows/nodes.md b/docs/versioned_docs/version-2.50.0-LTS/workflows/nodes.md index 3bad3d7e51..f932151c48 100644 --- a/docs/versioned_docs/version-2.50.0-LTS/workflows/nodes.md +++ b/docs/versioned_docs/version-2.50.0-LTS/workflows/nodes.md @@ -3,6 +3,14 @@ id: nodes title: Types of Nodes --- +
+ +
+ Self Hosted +
+ +
+ Nodes are a graphical representation of each process in a workflow. Each node in the workflow passes over the result to the next node. Every new workflow will have two nodes - **Start Trigger** and **Result**. The **Start Trigger** node triggers the workflow to run. Once the workflow execution is completed, the resulting data is stored in the **Result** node type. Apart from the default **Start Trigger** and **Result** nodes, there are an array of nodes that you can add to the canvas. They can be broadly divided into four types - **JavaScript**, **If condition**, **Data sources** and **REST API**. Let's take a closer look at each node. diff --git a/docs/versioned_docs/version-2.50.0-LTS/workflows/overview.md b/docs/versioned_docs/version-2.50.0-LTS/workflows/overview.md index a4c8adc732..caeda5fe7d 100644 --- a/docs/versioned_docs/version-2.50.0-LTS/workflows/overview.md +++ b/docs/versioned_docs/version-2.50.0-LTS/workflows/overview.md @@ -3,17 +3,13 @@ id: overview title: Overview --- -
- Icon - Paid feature +
+ +
+ Self Hosted
-
+
ToolJet Workflows is a visual, node-based platform tailored for data-centric automation tasks. With its intuitive design, users can create detailed queries across diverse data sources, manage conditional flows, and execute custom JavaScript code while making the processes presentable and easy to manage. diff --git a/docs/versioned_docs/version-2.50.0-LTS/workflows/permissions.md b/docs/versioned_docs/version-2.50.0-LTS/workflows/permissions.md index b7c58b62a4..c114c15c28 100644 --- a/docs/versioned_docs/version-2.50.0-LTS/workflows/permissions.md +++ b/docs/versioned_docs/version-2.50.0-LTS/workflows/permissions.md @@ -3,6 +3,14 @@ id: permissions title: Permissions --- +
+ +
+ Self Hosted +
+ +
+ Permissions in **ToolJet Workflows** provide a structured approach to access control, ensuring precise management of who can view, edit, or execute workflows. The below table gives a detailed summary of permissions in context of ToolJet Workflows. | User Group | Workflows Dashboard Access | Create/Edit Workflows | Execute Workflows | Using Workflows in ToolJet App Builder | Enable/Disable Workflows | diff --git a/docs/versioned_docs/version-2.50.0-LTS/workflows/results.md b/docs/versioned_docs/version-2.50.0-LTS/workflows/results.md index 4b103e9020..c883da1782 100644 --- a/docs/versioned_docs/version-2.50.0-LTS/workflows/results.md +++ b/docs/versioned_docs/version-2.50.0-LTS/workflows/results.md @@ -3,6 +3,14 @@ id: results title: Configuring Results --- +
+ +
+ Self Hosted +
+ +
+ Users have the flexibility to customize the results returned by workflows. The **Result** node enables configuration of your output through JavaScript code. ## Return Data from a Single Node diff --git a/docs/versioned_docs/version-2.50.0-LTS/workflows/triggers.md b/docs/versioned_docs/version-2.50.0-LTS/workflows/triggers.md index d19f2caf07..5e9fb93004 100644 --- a/docs/versioned_docs/version-2.50.0-LTS/workflows/triggers.md +++ b/docs/versioned_docs/version-2.50.0-LTS/workflows/triggers.md @@ -3,6 +3,14 @@ id: workflow-triggers title: Triggers --- +
+ +
+ Self Hosted +
+ +
+ Triggers can be used to execute a workflow. Currently, ToolJet supports two types of triggers: [Webhooks](#webhooks) and [Manual](#manual).
diff --git a/docs/versioned_docs/version-3.0.0-LTS/workflows/logs.md b/docs/versioned_docs/version-3.0.0-LTS/workflows/logs.md index b372b577fa..3b495d44aa 100644 --- a/docs/versioned_docs/version-3.0.0-LTS/workflows/logs.md +++ b/docs/versioned_docs/version-3.0.0-LTS/workflows/logs.md @@ -3,6 +3,14 @@ id: logs title: Logs --- +
+ +
+ Self Hosted +
+ +
+ Once you execute the workflow by clicking on the **Run** button, the logs panel will reflect the execution details of each node. Logs let you easily track the order of execution and check whether the execution of individual nodes is successful. You can click on the top bar of the logs panel to expand or minimize it.
diff --git a/docs/versioned_docs/version-3.0.0-LTS/workflows/nodes.md b/docs/versioned_docs/version-3.0.0-LTS/workflows/nodes.md index 25e2f0b9f9..f806f31e90 100644 --- a/docs/versioned_docs/version-3.0.0-LTS/workflows/nodes.md +++ b/docs/versioned_docs/version-3.0.0-LTS/workflows/nodes.md @@ -3,6 +3,14 @@ id: nodes title: Types of Nodes --- +
+ +
+ Self Hosted +
+ +
+ Nodes are graphical representations of each process in a workflow. Each node can access the data from the nodes that were executed earlier. Every workflow contains key node types that help orchestrate the flow of data and logic. ## Start Trigger Node diff --git a/docs/versioned_docs/version-3.0.0-LTS/workflows/overview.md b/docs/versioned_docs/version-3.0.0-LTS/workflows/overview.md index 3c893c5f6b..ce742a2d0f 100644 --- a/docs/versioned_docs/version-3.0.0-LTS/workflows/overview.md +++ b/docs/versioned_docs/version-3.0.0-LTS/workflows/overview.md @@ -3,9 +3,13 @@ id: overview title: Overview --- -
Available on: Paid plans
+
-
+
+ Self Hosted +
+ +
## Introduction diff --git a/docs/versioned_docs/version-3.0.0-LTS/workflows/permissions.md b/docs/versioned_docs/version-3.0.0-LTS/workflows/permissions.md index 9da32520f7..fec47b64e5 100644 --- a/docs/versioned_docs/version-3.0.0-LTS/workflows/permissions.md +++ b/docs/versioned_docs/version-3.0.0-LTS/workflows/permissions.md @@ -3,6 +3,14 @@ id: permissions title: Permissions --- +
+ +
+ Self Hosted +
+ +
+ Permissions in **ToolJet Workflows** provide a structured approach to access control, ensuring precise management of who can view, edit, or execute workflows. The below table gives a detailed summary of permissions in context of ToolJet Workflows. | User Group | Workflows Dashboard Access | Create/Edit Workflows | Execute Workflows | Using Workflows in Tooljet App Builder | Enable/Disable Workflows | diff --git a/docs/versioned_docs/version-3.0.0-LTS/workflows/results.md b/docs/versioned_docs/version-3.0.0-LTS/workflows/results.md index 11e9ccfc9e..df70260d6a 100644 --- a/docs/versioned_docs/version-3.0.0-LTS/workflows/results.md +++ b/docs/versioned_docs/version-3.0.0-LTS/workflows/results.md @@ -3,6 +3,14 @@ id: results title: Configuring Response --- +
+ +
+ Self Hosted +
+ +
+ Users have the flexibility to customize the response returned by workflows. The **Response** node enables configuration of your output through JavaScript code. Each workflow can have multiple response nodes. ## Return Data from a Single Node diff --git a/docs/versioned_docs/version-3.0.0-LTS/workflows/trigger-from-app.md b/docs/versioned_docs/version-3.0.0-LTS/workflows/trigger-from-app.md index 1bb89563af..9140c7c51e 100644 --- a/docs/versioned_docs/version-3.0.0-LTS/workflows/trigger-from-app.md +++ b/docs/versioned_docs/version-3.0.0-LTS/workflows/trigger-from-app.md @@ -3,6 +3,14 @@ id: trigger-workflow-from-app title: Trigger Workflows Within ToolJet --- +
+ +
+ Self Hosted +
+ +
+ This guide will show you how to set up a workflow and trigger it from a ToolJet application.
diff --git a/docs/versioned_docs/version-3.0.0-LTS/workflows/trigger-using-webhook.md b/docs/versioned_docs/version-3.0.0-LTS/workflows/trigger-using-webhook.md index da668299db..9a128f0a21 100644 --- a/docs/versioned_docs/version-3.0.0-LTS/workflows/trigger-using-webhook.md +++ b/docs/versioned_docs/version-3.0.0-LTS/workflows/trigger-using-webhook.md @@ -3,6 +3,14 @@ id: trigger-using-webhook title: Trigger Workflows Using Webhooks --- +
+ +
+ Self Hosted +
+ +
+ This guide demonstrates how to trigger workflows using webhooks.
diff --git a/docs/versioned_docs/version-3.0.0-LTS/workflows/triggers.md b/docs/versioned_docs/version-3.0.0-LTS/workflows/triggers.md index 6548eb6b33..e5b04c69cc 100644 --- a/docs/versioned_docs/version-3.0.0-LTS/workflows/triggers.md +++ b/docs/versioned_docs/version-3.0.0-LTS/workflows/triggers.md @@ -3,6 +3,14 @@ id: workflow-triggers title: Triggers --- +
+ +
+ Self Hosted +
+ +
+ Triggers can be used to execute a workflow. Currently, ToolJet supports two types of triggers: [Webhooks](#webhooks) and [Manual](#manual).
diff --git a/docs/versioned_docs/version-3.16.0-LTS/workflows/how-to/import-export.md b/docs/versioned_docs/version-3.16.0-LTS/workflows/how-to/import-export.md new file mode 100644 index 0000000000..9d21a4cb08 --- /dev/null +++ b/docs/versioned_docs/version-3.16.0-LTS/workflows/how-to/import-export.md @@ -0,0 +1,36 @@ +--- +id: import-export +title: Import or Export Workflows +--- + +
+ +
+ Self Hosted +
+ +
+ +ToolJet supports exporting workflows as JSON files and importing them into any ToolJet workspace. + +## Exporting Workflows + +To export a workflow from your ToolJet workspace: +1. Navigate to the **Workflows** tab from the dashboard. +2. Click on the kebab menu (three vertical dots) at the top-right corner of the workflow you want to export. +3. Select **Export Workflow** from the menu. A `.json` file containing the workflow configuration will be downloaded to your system. + Navigate to Workflow Section + +This file can later be imported into any ToolJet workspace to replicate the same workflow setup. + +## Importing Workflows + +To import a workflow from your ToolJet workspace: +1. Navigate to the **Workflows** tab from the dashboard. +2. Click on the kebab menu (three vertical dots) next to the **Create new workflow** button and select **Import from device**. + Navigate to Workflow Section +3. Choose the `.json` file of the workflow you want to import from your local system. +4. Click **Import workflow** button to complete the import process. + Navigate to Workflow Section + +Once imported, the workflow will appear in your workspace and can be edited or triggered like any other workflow. \ No newline at end of file diff --git a/docs/versioned_docs/version-3.16.0-LTS/workflows/how-to/trigger-from-app.md b/docs/versioned_docs/version-3.16.0-LTS/workflows/how-to/trigger-from-app.md index b05e16d65f..eda7e3d9e4 100644 --- a/docs/versioned_docs/version-3.16.0-LTS/workflows/how-to/trigger-from-app.md +++ b/docs/versioned_docs/version-3.16.0-LTS/workflows/how-to/trigger-from-app.md @@ -3,6 +3,16 @@ id: trigger-workflow-from-app title: Trigger Workflows Within ToolJet --- + +
+ +
+ Self Hosted +
+ +
+ + This guide will show you how to set up a workflow and trigger it from a ToolJet application.
diff --git a/docs/versioned_docs/version-3.16.0-LTS/workflows/how-to/trigger-using-scheduler.md b/docs/versioned_docs/version-3.16.0-LTS/workflows/how-to/trigger-using-scheduler.md index ba25859a6b..0422b26835 100644 --- a/docs/versioned_docs/version-3.16.0-LTS/workflows/how-to/trigger-using-scheduler.md +++ b/docs/versioned_docs/version-3.16.0-LTS/workflows/how-to/trigger-using-scheduler.md @@ -3,6 +3,14 @@ id: trigger-workflow-using-scheduler title: Trigger Workflows Using Scheduler --- +
+ +
+ Self Hosted +
+ +
+ ToolJet allows workflows to be triggered automatically at regular intervals or at specific scheduled times. Users can also specify the timezone to ensure that schedules align with local time. ## Running Workflow at Schedule Intervals diff --git a/docs/versioned_docs/version-3.16.0-LTS/workflows/how-to/trigger-using-webhook.md b/docs/versioned_docs/version-3.16.0-LTS/workflows/how-to/trigger-using-webhook.md index 2025307b67..58d3f8b07f 100644 --- a/docs/versioned_docs/version-3.16.0-LTS/workflows/how-to/trigger-using-webhook.md +++ b/docs/versioned_docs/version-3.16.0-LTS/workflows/how-to/trigger-using-webhook.md @@ -3,6 +3,14 @@ id: trigger-using-webhook title: Trigger Workflows Using Webhooks --- +
+ +
+ Self Hosted +
+ +
+ This guide demonstrates how to trigger workflows using webhooks.
diff --git a/docs/versioned_docs/version-3.16.0-LTS/workflows/logs.md b/docs/versioned_docs/version-3.16.0-LTS/workflows/logs.md index b372b577fa..3b495d44aa 100644 --- a/docs/versioned_docs/version-3.16.0-LTS/workflows/logs.md +++ b/docs/versioned_docs/version-3.16.0-LTS/workflows/logs.md @@ -3,6 +3,14 @@ id: logs title: Logs --- +
+ +
+ Self Hosted +
+ +
+ Once you execute the workflow by clicking on the **Run** button, the logs panel will reflect the execution details of each node. Logs let you easily track the order of execution and check whether the execution of individual nodes is successful. You can click on the top bar of the logs panel to expand or minimize it.
diff --git a/docs/versioned_docs/version-3.16.0-LTS/workflows/nodes.md b/docs/versioned_docs/version-3.16.0-LTS/workflows/nodes.md index 25e2f0b9f9..f806f31e90 100644 --- a/docs/versioned_docs/version-3.16.0-LTS/workflows/nodes.md +++ b/docs/versioned_docs/version-3.16.0-LTS/workflows/nodes.md @@ -3,6 +3,14 @@ id: nodes title: Types of Nodes --- +
+ +
+ Self Hosted +
+ +
+ Nodes are graphical representations of each process in a workflow. Each node can access the data from the nodes that were executed earlier. Every workflow contains key node types that help orchestrate the flow of data and logic. ## Start Trigger Node diff --git a/docs/versioned_docs/version-3.16.0-LTS/workflows/overview.md b/docs/versioned_docs/version-3.16.0-LTS/workflows/overview.md index 9711bacd11..c7604f910f 100644 --- a/docs/versioned_docs/version-3.16.0-LTS/workflows/overview.md +++ b/docs/versioned_docs/version-3.16.0-LTS/workflows/overview.md @@ -3,17 +3,13 @@ id: overview title: Overview --- -
- Icon - Paid feature +
+ +
+ Self Hosted
-
+
ToolJet Workflows enable users to create complex, data-centric automations using a visual, node-based interface. It extends ToolJet's capabilities beyond building user interfaces, allowing developers and business users to automate processes, integrate data from various sources, and execute custom logic without writing extensive code. diff --git a/docs/versioned_docs/version-3.16.0-LTS/workflows/permissions.md b/docs/versioned_docs/version-3.16.0-LTS/workflows/permissions.md index f989cd7817..37e8a1e155 100644 --- a/docs/versioned_docs/version-3.16.0-LTS/workflows/permissions.md +++ b/docs/versioned_docs/version-3.16.0-LTS/workflows/permissions.md @@ -3,6 +3,14 @@ id: permissions title: Permissions --- +
+ +
+ Self Hosted +
+ +
+ Permissions in **ToolJet Workflows** provide a structured approach to access control, ensuring precise management of who can view, edit, or execute workflows. The below table gives a detailed summary of permissions in context of ToolJet Workflows. | Permission | Admins | Builders | End Users | Custom Groups | diff --git a/docs/versioned_docs/version-3.16.0-LTS/workflows/results.md b/docs/versioned_docs/version-3.16.0-LTS/workflows/results.md index 11e9ccfc9e..df70260d6a 100644 --- a/docs/versioned_docs/version-3.16.0-LTS/workflows/results.md +++ b/docs/versioned_docs/version-3.16.0-LTS/workflows/results.md @@ -3,6 +3,14 @@ id: results title: Configuring Response --- +
+ +
+ Self Hosted +
+ +
+ Users have the flexibility to customize the response returned by workflows. The **Response** node enables configuration of your output through JavaScript code. Each workflow can have multiple response nodes. ## Return Data from a Single Node diff --git a/docs/versioned_docs/version-3.16.0-LTS/workflows/triggers.md b/docs/versioned_docs/version-3.16.0-LTS/workflows/triggers.md index 10e38caa4a..2cba87fa73 100644 --- a/docs/versioned_docs/version-3.16.0-LTS/workflows/triggers.md +++ b/docs/versioned_docs/version-3.16.0-LTS/workflows/triggers.md @@ -3,6 +3,14 @@ id: workflow-triggers title: Triggers --- +
+ +
+ Self Hosted +
+ +
+ Triggers can be used to execute a workflow. Currently, ToolJet supports three types of triggers: webhooks, scheduled triggers, and manual triggers. Triggers @@ -12,21 +20,22 @@ Triggers can be used to execute a workflow. Currently, ToolJet supports three ty A webhook trigger allows you to run the workflow when a webhook is received. You can configure the webhook trigger from the Triggers tab. The webhook URL is unique for each workflow. #### Creating a Webhook Trigger + - Click on the **Triggers** option in the left panel to open the Triggers tab. - Triggers + Triggers - Click on the **Webhooks** option. - Triggers + Triggers - By default, the webhook trigger is disabled. Toggle the switch to **enable** the webhook trigger. - Triggers + Triggers - Once enabled, you can choose the **Environment** to modify the webhook endpoint URL to be copied for that specific environment. For example, if you choose the **Production** environment, you can `Copy URL` or `Copy as cURL` which can then be used to trigger for **Production** environment accordingly. - Triggers + Triggers - Find the API endpoint URL in the **Endpoint** field. You can use this URL to send a POST request to trigger the workflow. You can also click on the **Copy** button to copy the URL to the clipboard. You can either select `Copy URL` or `Copy as cURL` from the dropdown menu. The `Copy as cURL` option copies the URL as a cURL command which will include details such as the `API token` and `Environment`. An example of the Endpoint URL is as follows: ``` http://{TOOLJET_HOST}/api/v2/webhooks/workflows/:id/trigger ``` - Triggers + Triggers - The API token is used to authenticate the request. You can find the API token in the **API Token** field. You can also click on the **Copy** button to copy the API token to the clipboard. - Triggers + Triggers :::info Currently, authentication is mandatory for webhooks. Use a bearer token in the `Authorization` header for authentication.
**Format:** @@ -39,7 +48,7 @@ A webhook trigger allows you to run the workflow when a webhook is received. You "name": "string", "age": "number" ``` - Triggers + Triggers - The **Test JSON parameters** field can be used to test the webhook trigger. You can enter the parameter values in the **Test JSON parameters** field and click on the **Run** button to test the webhook trigger. The workflow will be executed with the parameter values specified in the **Test JSON parameters** field. ```json { @@ -47,8 +56,12 @@ A webhook trigger allows you to run the workflow when a webhook is received. You "age": 30 } ``` - These parameters can be accessed in the workflow using the `startTrigger.params`. - Triggers + +### Accessing Webhook Parameters + +These parameters can be accessed in the workflow using the `startTrigger.params.`. + +Triggers ### Async Workflow Query Execution diff --git a/docs/versioned_docs/version-3.5.0-LTS/workflows/how-to/import-export.md b/docs/versioned_docs/version-3.5.0-LTS/workflows/how-to/import-export.md index e4012845d5..9d21a4cb08 100644 --- a/docs/versioned_docs/version-3.5.0-LTS/workflows/how-to/import-export.md +++ b/docs/versioned_docs/version-3.5.0-LTS/workflows/how-to/import-export.md @@ -3,6 +3,14 @@ id: import-export title: Import or Export Workflows --- +
+ +
+ Self Hosted +
+ +
+ ToolJet supports exporting workflows as JSON files and importing them into any ToolJet workspace. ## Exporting Workflows diff --git a/docs/versioned_docs/version-3.5.0-LTS/workflows/how-to/trigger-from-app.md b/docs/versioned_docs/version-3.5.0-LTS/workflows/how-to/trigger-from-app.md index 1bb89563af..9140c7c51e 100644 --- a/docs/versioned_docs/version-3.5.0-LTS/workflows/how-to/trigger-from-app.md +++ b/docs/versioned_docs/version-3.5.0-LTS/workflows/how-to/trigger-from-app.md @@ -3,6 +3,14 @@ id: trigger-workflow-from-app title: Trigger Workflows Within ToolJet --- +
+ +
+ Self Hosted +
+ +
+ This guide will show you how to set up a workflow and trigger it from a ToolJet application.
diff --git a/docs/versioned_docs/version-3.5.0-LTS/workflows/how-to/trigger-using-webhook.md b/docs/versioned_docs/version-3.5.0-LTS/workflows/how-to/trigger-using-webhook.md index 7aeb1a155f..e90b38b0fe 100644 --- a/docs/versioned_docs/version-3.5.0-LTS/workflows/how-to/trigger-using-webhook.md +++ b/docs/versioned_docs/version-3.5.0-LTS/workflows/how-to/trigger-using-webhook.md @@ -3,6 +3,14 @@ id: trigger-using-webhook title: Trigger Workflows Using Webhooks --- +
+ +
+ Self Hosted +
+ +
+ This guide demonstrates how to trigger workflows using webhooks.
diff --git a/docs/versioned_docs/version-3.5.0-LTS/workflows/logs.md b/docs/versioned_docs/version-3.5.0-LTS/workflows/logs.md index b372b577fa..3b495d44aa 100644 --- a/docs/versioned_docs/version-3.5.0-LTS/workflows/logs.md +++ b/docs/versioned_docs/version-3.5.0-LTS/workflows/logs.md @@ -3,6 +3,14 @@ id: logs title: Logs --- +
+ +
+ Self Hosted +
+ +
+ Once you execute the workflow by clicking on the **Run** button, the logs panel will reflect the execution details of each node. Logs let you easily track the order of execution and check whether the execution of individual nodes is successful. You can click on the top bar of the logs panel to expand or minimize it.
diff --git a/docs/versioned_docs/version-3.5.0-LTS/workflows/nodes.md b/docs/versioned_docs/version-3.5.0-LTS/workflows/nodes.md index a47a4949f2..7f818a6ca5 100644 --- a/docs/versioned_docs/version-3.5.0-LTS/workflows/nodes.md +++ b/docs/versioned_docs/version-3.5.0-LTS/workflows/nodes.md @@ -3,6 +3,14 @@ id: nodes title: Types of Nodes --- +
+ +
+ Self Hosted +
+ +
+ Nodes are graphical representations of each process in a workflow. Each node can access the data from the nodes that were executed earlier. Every workflow contains key node types that help orchestrate the flow of data and logic. ## Start Trigger Node diff --git a/docs/versioned_docs/version-3.5.0-LTS/workflows/overview.md b/docs/versioned_docs/version-3.5.0-LTS/workflows/overview.md index 1ef9792658..38abe87313 100644 --- a/docs/versioned_docs/version-3.5.0-LTS/workflows/overview.md +++ b/docs/versioned_docs/version-3.5.0-LTS/workflows/overview.md @@ -4,15 +4,6 @@ title: Overview ---
-
- Icon - Paid feature -
Self Hosted diff --git a/docs/versioned_docs/version-3.5.0-LTS/workflows/permissions.md b/docs/versioned_docs/version-3.5.0-LTS/workflows/permissions.md index 9da32520f7..fec47b64e5 100644 --- a/docs/versioned_docs/version-3.5.0-LTS/workflows/permissions.md +++ b/docs/versioned_docs/version-3.5.0-LTS/workflows/permissions.md @@ -3,6 +3,14 @@ id: permissions title: Permissions --- +
+ +
+ Self Hosted +
+ +
+ Permissions in **ToolJet Workflows** provide a structured approach to access control, ensuring precise management of who can view, edit, or execute workflows. The below table gives a detailed summary of permissions in context of ToolJet Workflows. | User Group | Workflows Dashboard Access | Create/Edit Workflows | Execute Workflows | Using Workflows in Tooljet App Builder | Enable/Disable Workflows | diff --git a/docs/versioned_docs/version-3.5.0-LTS/workflows/results.md b/docs/versioned_docs/version-3.5.0-LTS/workflows/results.md index 11e9ccfc9e..df70260d6a 100644 --- a/docs/versioned_docs/version-3.5.0-LTS/workflows/results.md +++ b/docs/versioned_docs/version-3.5.0-LTS/workflows/results.md @@ -3,6 +3,14 @@ id: results title: Configuring Response --- +
+ +
+ Self Hosted +
+ +
+ Users have the flexibility to customize the response returned by workflows. The **Response** node enables configuration of your output through JavaScript code. Each workflow can have multiple response nodes. ## Return Data from a Single Node diff --git a/docs/versioned_docs/version-3.5.0-LTS/workflows/triggers.md b/docs/versioned_docs/version-3.5.0-LTS/workflows/triggers.md index 174164befc..9dbb877f49 100644 --- a/docs/versioned_docs/version-3.5.0-LTS/workflows/triggers.md +++ b/docs/versioned_docs/version-3.5.0-LTS/workflows/triggers.md @@ -3,6 +3,14 @@ id: workflow-triggers title: Triggers --- +
+ +
+ Self Hosted +
+ +
+ Triggers can be used to execute a workflow. Currently, ToolJet supports three types of triggers: webhooks, scheduled triggers, and manual triggers. Triggers @@ -47,8 +55,12 @@ A webhook trigger allows you to run the workflow when a webhook is received. You "age": 30 } ``` - These parameters can be accessed in the workflow using the `startTrigger.params`. - Triggers + +### Accessing Webhook Parameters + +These parameters can be accessed in the workflow using the `startTrigger.params.`. + +Triggers ### Async Workflow Query Execution diff --git a/docs/versioned_sidebars/version-3.16.0-LTS-sidebars.json b/docs/versioned_sidebars/version-3.16.0-LTS-sidebars.json index 1b381bb354..584ce42960 100644 --- a/docs/versioned_sidebars/version-3.16.0-LTS-sidebars.json +++ b/docs/versioned_sidebars/version-3.16.0-LTS-sidebars.json @@ -475,7 +475,8 @@ "items": [ "workflows/how-to/trigger-using-webhook", "workflows/how-to/trigger-workflow-from-app", - "workflows/how-to/trigger-workflow-using-scheduler" + "workflows/how-to/trigger-workflow-using-scheduler", + "workflows/how-to/import-export" ] } ]