c2e97a89f9
* HighLevel Node & Credentials with basic Get/GetAll contacts * moved contact description into subfolder * improving all HighLevel contact crud operations * Get All Contacts request filters and options * Get All Contacts request operation pagination * Get All Contacts pagination with rootProperty * fixing contact operations lint error node-param-options-type-unsorted-items * Get All Contact pagination using response total to terminate loop * Get All Contacts pagination using qs startAfterId and startAfter instead of nextPageUrl * cleanup ContactDescription.ts operations * added OpportunityDescription.ts Get All Operation * added PipelineDescription.ts Get All pipelines (pagination no supported) * GenericFunctions.ts created highLevelApiPagination method * removed returnAll from getAll pipelines because pagination not supported * minor improvement using IPostReceiveRootProperty Interface * added TaskDescription.ts GetAll operation * TaskDescription get operation * task delete operation * ContactDescription fixing duplicate additionalFields * OpportunityDescription.ts adding filters for get all operation * opportunity get and delete operation * opportunity create additional fields * task create with additionalFields * create opportunity added missing status * pagination resource mapping; create opportunity for contact email/phone/id * create task format field dueDate to suppressMilliseconds * opportunity's pipeline options with loadOptions * fixed task dueDate; task update operation * added contact dnd fields * added contact tags * add contact source parameter * using returnAll Tasks with undocumented limit property * add contact customField with loadOptions * task dueDate preSendAction throw required error * opportunity stageId using getPipelineStages method * improve update contacts operation; renaming identifier to contactId * contact tasks renamed contactIdentifier to contactId and identifier to taskId * delete unused postReceiveAction * getTaskPostReceiceAction to inject contactId into items * remove source field from update contact because not supported * renaming opportunities pipelineIdentifier to pipelineId * opportunity parameter reordering * opportunity update operation * opportunity renamed "Identifier" to "Opporituny ID" * create opportunity additional field tags * opportunity create/update additional fields * opportunity update contactIdentifier * deleted pipeline getAll resource; cleanup generic functions; * opportunity getAll option stageId use getPipelineStages * opportunity assignedTo options use loadOptionsMethod getUsers * added loadOptions description ''Choose from the list, or specify an ID [...]' * getAll Tasks removing output maxResults * highLevelApiRequest add IPollFunctions * add HighLevelTriggerNode * add highLevelOAuth2Api credentials * revert from v2 oauth2 back to apiKey v1 (incompatible client-oauth2) * delete run.sh (was commited by accidant) * removed HighLevelTrigger.node.ts (polling) until we support API V2 webhooks * task additionalFields in alphabetical order; task assignedTo using loadOptions getUsers * contact additionalFields/updateFields/filters in alphabetical order * opportunity additionalFields/fields in alphabetical order * ⚡ linter fixes, formating * ⚡ fixed deprecated auth * ⚡ lock file and auth fix * ⚡ linter fixes * ⚡ requestWithAuthentication in highLevelApiRequest * ⚡ timeZones autoload and naming fixes * contact property dnd - improved display name and description * contact property dnd - improved display name and description * contact create/update pre send action to validate email/phone * updated description for contact lookup email and phone parameters * opportunity monetary value - removed getAll filter (doesn't work) - added param description * opportunity getAll startDate and endDate to type dateTime and dateTimeToEpochPreSendAction * loadOption getTimezones() using /timezones and not moment.tz.names() * improved description for opportunity parameter assignedTo * added hint to opportunity param contactIdentifier "there can only be one..." * added contact phone description and placeholder * contact renamed operation "create" to "create or update" and added notice * update opportunity - prefetch fields title/status required by api * create/update task splitting up additionalFields to prep update changes * update task- prefetch fields title/dueDate required by api * linter fixes * ⚡ improvements * ⚡ updated autoloaded parameters names to follow convention * update opportunity added hint "You cannot update an opportunity's pipeline ID." Co-authored-by: Michael Kret <michael.k@radency.com> |
||
|---|---|---|
| .github | ||
| .vscode | ||
| assets | ||
| docker | ||
| packages | ||
| scripts | ||
| .dockerignore | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.js | ||
| .gitignore | ||
| .npmrc | ||
| .prettierignore | ||
| .prettierrc.js | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| CONTRIBUTOR_LICENSE_AGREEMENT.md | ||
| LICENSE.md | ||
| LICENSE_EE.md | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| SECURITY.md | ||
| turbo.json | ||
| vetur.config.js | ||
n8n - Workflow automation tool
n8n is an extendable workflow automation tool. With a fair-code distribution model, n8n will always have visible source code, be available to self-host, and allow you to add your own custom functions, logic and apps. n8n's node-based approach makes it highly versatile, enabling you to connect anything to everything.
Demo
📺 A short video (< 4 min) that goes over key concepts of creating workflows in n8n.
Available integrations
n8n has 200+ different nodes to automate workflows. The list can be found on: https://n8n.io/integrations
Documentation
The official n8n documentation can be found under: https://docs.n8n.io
Additional information and example workflows on the n8n.io website: https://n8n.io
The changelog can be found here and the list of breaking changes here.
Usage
Start
Execute: npx n8n
n8n cloud
Sign-up for an n8n cloud account.
While n8n cloud and n8n are the same in terms of features, n8 cloud provides certain conveniences such as:
- Not having to set up and maintain your n8n instance
- Managed OAuth for authentication
- Easily upgrading to the newer n8n versions
Support
If you have problems or questions go to our forum, we will then try to help you asap:
Jobs
If you are interested in working for n8n and so shape the future of the project check out our job posts
What does n8n mean and how do you pronounce it?
Short answer: It means "nodemation" and it is pronounced as n-eight-n.
Long answer: "I get that question quite often (more often than I expected) so I decided it is probably best to answer it here. While looking for a good name for the project with a free domain I realized very quickly that all the good ones I could think of were already taken. So, in the end, I chose nodemation. 'node-' in the sense that it uses a Node-View and that it uses Node.js and '-mation' for 'automation' which is what the project is supposed to help with. However, I did not like how long the name was and I could not imagine writing something that long every time in the CLI. That is when I then ended up on 'n8n'." - Jan Oberhauser, Founder and CEO, n8n.io
Development setup
Have you found a bug 🐛 ? Or maybe you have a nice feature ✨ to contribute ? The CONTRIBUTING guide will help you get your development environment ready in minutes.
License
n8n is fair-code distributed under the Sustainable Use License and the n8n Enterprise License.
Additional information about the license model can be found in the docs.