📚 0.135.1 and 0.135.0 changelog (#610)

This commit is contained in:
Gabriel 2021-08-23 13:59:10 +03:00 committed by GitHub
parent db25febc9a
commit 2ac8a0dd35
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
11 changed files with 244 additions and 1 deletions

View File

@ -0,0 +1,23 @@
---
permalink: /credentials/formIoTrigger
description: Learn to configure credentials for the Form.io Trigger node in n8n
---
# Form.io Trigger
You can use these credentials to authenticate the following nodes:
- [Form.io Trigger](../../nodes-library/trigger-nodes/FormIoTrigger/README.md)
## Prerequisites
Create a [Form.io](https://www.form.io/) account.
## Using Basic auth
After creating your Form.io account, from n8n:
1. Enter a descriptive ***Credentials Name***.
2. Select whether your ***Environment*** is **Cloud-hosted** or **Self-hosted**.
3. Enter your Form.io account ***Email***.
4. Enter your Form.io account ***Password***.
5. Click **Create** to save your new credentials.

View File

@ -0,0 +1,57 @@
---
permalink: /credentials/formstackTrigger
description: Learn to configure credentials for the Formstack Trigger node in n8n
---
# Formstack Trigger
You can use these credentials to authenticate the following nodes:
- [Formstack Trigger](../../nodes-library/trigger-nodes/formstackTrigger/README.md)
## Prerequisites
Create a [Formstack](https://www.formstack.com/) account.
## Using Access token
After creating your Formstack account:
1. From the user menu select **API**.
2. Select **New Application**.
3. In the *Create Application* window enter the following:
* *Application Name*: Provide a descriptive name.
* *Redirect URI*: Enter the OAuth callback URL for your n8n instance in the format `http://<n8n_url>/rest/oauth2-credential/callback`. For example `http://localhost:5678/rest/oauth2-credential/callback`.
* *Description*: Enter a brief description.
* *Platform*: Select **Website**.
4. Click **Create Application**.
5. Copy the *Access Token* for your new application.
From n8n:
6. Enter a descriptive ***Credentials Name***.
7. Enter your Formstack ***Access Token***.
8. Click **Create** to save your new credentials.
## Using OAuth2
After creating your Formstack account:
1. From the user menu select **API**.
2. Select **New Application**.
3. In the *Create Application* window enter the following:
* *Application Name*: Provide a descriptive name.
* *Redirect URI*: Enter the OAuth callback URL for your n8n instance in the format `http://<n8n_url>/rest/oauth2-credential/callback`. For example `http://localhost:5678/rest/oauth2-credential/callback`.
* *Description*: Enter a brief description.
* *Platform*: Select **Website**.
4. Click **Create Application**.
5. Select your new application to view the *Application Details*.
6. Copy the *Client ID* and *Client Secret*.
From n8n:
7. Enter a descriptive ***Credentials Name***.
8. Enter your Formstack ***Client ID***.
9. Enter your Formstack ***Client Secret***.
10. Click the circle button to initiate the OAuth2 flow.
11. In the modal window select **Authorize**.
12. Click **Create** to save your new credentials.

View File

@ -0,0 +1,61 @@
---
permalink: /nodes/n8n-nodes-base.wait
description: Learn how to use the Wait node in n8n
---
# Wait
The Wait node is used to create a pause of any desired duration in your workflows. When the workflow is paused the execution data is offloaded to the database, and when the resume condition is met it is reloaded and the execution continues.
The Wait node can be be set to resume on the following conditions:
* [**After time interval**](#time-interval)
* [**At specified time**](#specified-time)
* [**On webhook call**](#webhook-call)
::: tip 💡 Keep in mind
For the time-based resume operations, note that:
* For wait times less than 65 seconds, execution data is not offloaded to the database to resume later but rather the process continues to run and execution resumes after the specified interval passes.
* The n8n server time is always used regardless of the timezone setting. Workflow timezone settings, and any changes made to them, do not affect the Wait node interval or specified time.
:::
## Time interval
Use the ***After time interval*** resume operation to set a desired interval after which the execution will resume.
Set the desired *Amount* and the corresponding *Unit* for the Wait operation. Decimals can be used for fractional units, for example `1.5` minutes instead of `90` seconds.
To automatically resume workflow execution after 15 minutes, the Wait node configuration would look like this:
![Wait node time interval](./wait_time_interval.png)
## Specified time
Use the ***At specified time*** resume operation to set a particular date and time in the future when the workflow execution should resume.
For example, if you want the workflow execution to continue at midnight of New Year's Day 2022 the Wait node configuration would look like this:
![Wait node specified time](./wait_specific_time.png)
## Webhook call
Use the **On webhook call** resume operation to configure your workflow execution to resume when an HTTP call is received.
::: tip 💡 Keep in mind
The Wait node cannot be used to stop a workflow execution, it will wait indefinitely for the restart webhook URL to be called. To stop the execution an [IF node](./If/README.md) can be used to check if the `headers` or `response` variables are empty (meaning no webhook call was received).
:::
The webhook URL that needs to be called to trigger the execution resumption is available by referencing the `$resumeWebhookUrl` variable wherever needed (e.g. expressions). The URL itself will be generated when the workflow executes.
This generated URL is unique to each execution, meaning that your workflow can contain multiple Wait nodes and as the webhook URL is called it will resume each Wait node sequentially.
### Reference
See the [Webhook node](./Webhook/README.md) documentation to learn more about the Authentication, Method, and Response parameters when configuring the Wait node to resume on a webhook call.
In addition to the parameters shared with the Webhook mode, the Wait node has the following additional configuration options:
* **Limit wait time**: Set the maximum amount of time to wait before the execution is resumed by default (i.e. even with no webhook call received).
* **Add Option** > **Webhook Suffix**: Provide a suffix that you want to appended to the restart URL.
**Note**: The generated `$resumeWebhookUrl` will not automatically include this suffix, you must manually append it to the webhook URL before exposing it.

Binary file not shown.

After

Width:  |  Height:  |  Size: 59 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 61 KiB

View File

@ -0,0 +1,34 @@
---
permalink: /nodes/n8n-nodes-base.formIoTrigger
description: Learn how to use the Form.io Trigger node in n8n
---
# Form.io Trigger
[Form.io](https://www.form.io/) is an enterprise class combined form and API data management platform for building complex form-based business process applications.
::: tip 🔑 Credentials
You can find authentication information for this node [here](../../../credentials/FormIo/README.md).
:::
## Example Usage
This workflow allows you to receive updates for newly created submissions in Form.io. This example workflow uses the following node:
- [Form.io Trigger]()
The final workflow should look like the following image.
![A workflow with the Form.io Trigger node](./workflow.png)
### 1. Form.io Trigger node
1. First enter credentials for the Form.io Trigger node. You can find out how to do that [here](../../../credentials/FormIo/README.md).
2. Select the project you want to receive updates for using the *Project Name/ID* dropdown list.
3. Select the form you want to receive updates for using the *Form Name/ID* dropdown list.
4. Select **Submission Created** from the *Trigger Events* dropdown list.
5. Click on **Execute Node** to run the workflow.
::: tip 💡 Activate workflow for production
You'll need to save the workflow and then click on the Activate toggle on the top right of the screen to activate the workflow. Your workflow will then be triggered as specified by the settings in the Form.io Trigger node.
:::

Binary file not shown.

After

Width:  |  Height:  |  Size: 45 KiB

View File

@ -0,0 +1,32 @@
---
permalink: /nodes/n8n-nodes-base.formstackTrigger
description: Learn how to use the Formstack Trigger node in n8n
---
# Formstack Trigger
[Formstack](https://www.formstack.com/) is a workplace productivity platform that helps organizations streamline digital work through no-code online forms, documents, and signatures.
::: tip 🔑 Credentials
You can find authentication information for this node [here](../../../credentials/formstack/README.md).
:::
## Example Usage
This workflow allows you to receive updates for newly created submissions in Formstack forms. This example workflow uses the following node:
- [Formstack Trigger]()
The final workflow should look like the following image.
![A workflow with the Formstack Trigger node](./workflow.png)
### 1. Formstack Trigger node
1. First enter credentials for the Formstack Trigger node. You can find out how to do that [here](../../../credentials/Formstack/README.md).
2. Enter the form you want to receive updates for using the *Form Name/ID* field.
3. Click on **Execute Node** to run the workflow.
::: tip 💡 Activate workflow for production
You'll need to save the workflow and then click on the Activate toggle on the top right of the screen to activate the workflow. Your workflow will then be triggered as specified by the settings in the Form.io Trigger node.
:::

Binary file not shown.

After

Width:  |  Height:  |  Size: 50 KiB

View File

@ -2,6 +2,42 @@
🛠 = Version contains a breaking change. Check out the list of all the breaking changes [here](https://github.com/n8n-io/n8n/blob/master/packages/cli/BREAKING-CHANGES.md).
## n8n@0.135.1
For a comprehensive list of changes, check out the [commits](https://github.com/n8n-io/n8n/compare/n8n%400.135.0...n8n@0.135.1) for this version.<br />
**Release date:** 2021-08-23
### Core Functionality ⚙️
- Fixed an issue resulting in 503 errors when upgrading to `v0.135.0`.
## n8n@0.135.0 🛠
For a comprehensive list of changes, check out the [commits](https://github.com/n8n-io/n8n/compare/n8n%400.134.0...n8n@0.135.0) for this version.<br />
**Release date:** 2021-08-22
::: warning ⚠️ Breaking changes
Please note that this version contains breaking changes. You can read more about it [here](https://github.com/n8n-io/n8n/blob/master/packages/cli/BREAKING-CHANGES.md#01350).
The features that introduced the breaking changes have been flagged below.
:::
### New nodes ✨
<br />
<Changelog node="n8n-nodes-base.formIoTrigger" title="Form.io Trigger"/>
<Changelog node="n8n-nodes-base.formstackTrigger" title="Formstack Trigger"/>
<Changelog node="n8n-nodes-base.wait" title="Wait"/>
### Core Functionality ⚙️
- In-node method for accessing binary data is now asynchronous and a helper function for this has been implemented. [🛠](https://github.com/n8n-io/n8n/blob/master/packages/cli/BREAKING-CHANGES.md#01350)
- Credentials are now loaded from the database on-demand. [🛠](https://github.com/n8n-io/n8n/blob/master/packages/cli/BREAKING-CHANGES.md#01350)
- Webhook UUIDs are automatically updated when duplicating a workflow.
- Fixed an issue when referencing values before loops.
### Bug fixes 🐛
<br />
<Changelog node="n8n-nodes-base.interval" title="Interval:" text="Fixed issue where entering too large a value (> 2147483647ms) resulted in an interval of 1sec being used rather than an error."/>
### Contributors 🙌
[Aniruddha Adhikary](https://github.com/aniruddha-adhikary), [lublak](https://github.com/lublak), [parthibanbalaji](https://github.com/parthibanbalaji)
## n8n@0.134.0
For a comprehensive list of changes, check out the [commits](https://github.com/n8n-io/n8n/compare/n8n%400.133.0...n8n@0.134.0) for this version.<br />
**Release date:** 2021-08-15

View File

@ -18,7 +18,7 @@
"@fortawesome/fontawesome-svg-core": "^1.2.35",
"@fortawesome/free-solid-svg-icons": "^5.15.3",
"@fortawesome/vue-fontawesome": "^2.0.2",
"n8n-nodes-base": "^0.131.0",
"n8n-nodes-base": "^0.132.0",
"vuepress-plugin-sitemap": "^2.3.1"
},
"devDependencies": {