mirror of
https://github.com/n8n-io/n8n.git
synced 2025-01-12 05:17:28 -08:00
fbf60199d9
* fixed Google Sheet 'Use Header Names as JSON Paths' issue when input data contains null values. https://community.n8n.io/t/error-cannot-read-properties-of-null-reading-tostring/14385/2 * ⚡ Update URLs to n8n.io API (#3391) * fix(core): Fix migrations on non-public Postgres schema (#3356) * 🐛 Fix UM migration * ⚡ Account for schema in `search_path` * 🔥 Remove unneeded schema refs * 🧪 Account for alt schema in DB testing * ⚡ Add schema to `IncreaseTypeVarcharLimit` * ⚡ Set `search_path` in every migration * ⚡ Set `search_path` in down migrations * refactor(core): Improve error message * feat(RabbitMQ Trigger Node): Make message acknowledgement and parallel processing configurable (#3385) * feat(RabbitMQ Trigger Node): Make message acknowledgement and concurrent processing configurable * ⚡ Make sure that messages do not get executed multiple times * 👕 Fix lint issue * 🐛 Fix issue that for manual executions in "own" mode messages got know acknowledged * ⚡ Increment count now that console.log got removed * ⚡ Improvements * ⚡ Fix default value * ⚡ Improve display name * fix(Gmail Node): Fix sending attachments when filesystem mode is used (#3396) * ⚡ Minor improvement Co-authored-by: Taha Sönmez <mtssonmez@gmail.com> Co-authored-by: Ben Hesseldieck <1849459+BHesseldieck@users.noreply.github.com> Co-authored-by: Iván Ovejero <ivov.src@gmail.com> Co-authored-by: Jan Oberhauser <jan.oberhauser@gmail.com> Co-authored-by: Jan Oberhauser <janober@users.noreply.github.com> Co-authored-by: Michael Kret <88898367+michael-radency@users.noreply.github.com> |
||
---|---|---|
.. | ||
credentials | ||
nodes | ||
src | ||
test/nodes | ||
gulpfile.js | ||
LICENSE.md | ||
package.json | ||
README.md | ||
tsconfig.json | ||
tslint.json |
n8n-nodes-base
The nodes which are included by default in n8n
npm install n8n-nodes-base -g
License
n8n is fair-code distributed under the Sustainable Use License.
Additional information on the license can be found in the FAQ