This behavior is not acceptable. Even the Commons Clause itself tells you not to describe your software as open source, see the FAQ: https://commonsclause.com/

The Apache license is a well known and respected license, and the "Commons Clause" leverages the language of the also well known "Creative Commons", together creating a false impression that this software is distributed by a respectable group of developers. You cannot rely on putting its name there to correct your lies.

Your software is rightly called "source available". Do not gaslight us. In the words of Randall Monroe:

I just noticed CVS has started stocking homeopathic pills on the same shelves with--and labeled similarly to--their actual medicine. Telling someone who trusts you that you're giving them medicine, when you know you're not, because you want their money, isn't just lying--it's like an example you'd make up if you had to illustrate for a child why lying is wrong.

Note: If you lock this issue you are a liar and a coward. Hear the anger of those you've wronged.

Edit: this link is useful for onlookers wondering I'm angry out of the gate.

Hi n8n team,

This contribution contains the integrations of TheHive Project in the form of three nodes:

• TheHive node
  • Alert
    • List alerts
    • Fetch one alert
    • Create an alert
    • Update an alert
    • Search alerts
    • Count alerts (API v1 only)
    • Merge an alert into existing Case
    • Promote an alert into new Case
    • Execute a responder
  • Observable
    • List observables
    • Fetch one observable
    • Create an observable
    • Update an observable
    • Search observables
    • Count observables (API v1 only)
    • Execute an analyzer
    • Execute a responder
  • Case
    • List cases
    • Fetch one case
    • Create a case
    • Update a case
    • Search cases
    • Count cases (API v1 only)
    • Execute a responder
  • Task
    • List task (specified Case)
    • Fetch one task
    • Create a task
    • Update a task
    • Search tasks
    • Count tasks (API v1 only)
    • Execute a responder
  • Log
    • List logs
    • Fetch one log
    • Create a log
    • Execute a responder
• Cortex node
  • Analyzer
    • Execute
  • Responder
    • Execute
  • Job
    • Get Job
    • Get Report
• TheHive-Trigger node

The nodes development was initiated in this forum post and we tried to deliver a good quality nodes, So if there are any changes to make, feel free to contact us with your suggestions

Best regards!

Describe the bug When a IMAP workflow trigger is in an active workflow new messages will be processed until a certain time when they will cease working. The workflow will remain active and no errors are reported. Without inspecting the inbox the workflow looks as if no new emails were received, but when in actuality there are new emails. If you deactivate the trigger and reactivate all messages that were not read they will now be processed.

To Reproduce Steps to reproduce the behavior:

1. Create new workflow
2. Add IMAP trigger and configure to IMAP server
3. Add a node that handel down stream data from the IMAP trigger (eg slack or ftp)
4. Activate
5. on a long job say ever 12 hours send an email the address the IMAP triggers on
6. wait, typically the workflow will process on email but after the first one something timeout internally and nothing further processes.

Expected behavior I would expect that each email no matter the time between occurrences that the IMAP email trigger fires.

Environment (please complete the following information):

• n8n docker image 0.90 with Postgres

** Notes ** There are no errors in n8n i see in the logs, I have tried increasing the log level but haven't had much luck. The IMAP email trigger does process a attachment, I have tested with and without attachments and have similar results.

I can get more information if someone tells me what would be useful. I have seen forum posts about this issue but no one has filed a bug.

I keep getting this Entries exist but they do not contain any JSON data. after every workflow execution.

e.g. starring my github repo like in the example youtube video.

But a Command Execution node works e.g. node -e "console.log('success');" gives out a JSON

[
{
"exitCode": 0,
"stderr": "",
"stdout": "success"
}
]

Am I doing something wrong with the access token generation on the github? I gave all the permissions before generating the token and I still am not able to receive any JSON data.

KoboToolbox is a popular open-source field survey / data collection tool largely used by humanitarian organizations.

This PR has support for most API calls (no trigger...): fetching form definitions, submissions, and webhooks.

All tested, code linted, all should be pretty polished...

Describe the bug The Dropbox node gives an error: "Dropbox Credentials invalid!" after updating n8n to 0.111.0

To Reproduce Steps to reproduce the behavior:

1. Update n8n to the latest version (0.111.0)
2. Any existing workflows using the dropbox node will result in an Error
3. Rolling back n8n to 0.110.3 resolves this issue

Expected behavior There shouldn't have been any issue with Dropbox.

Environment (please complete the following information):

• OS: [e.g. Ubuntu Linux 18.04] Ubuntu 20.04
• n8n Version [e.g. 0.26.0] 0.111.0
• Node.js Version [e.g. 10.16.0] 14.x

Additional context Add any other context about the problem here.

We recently ran into a blocker where we were fetching temporary AWS credentials for uploading a file to S3 but the AWS S3 node in n8n didn't have proper support for it.

This pull request adds the third credential parameter sessionToken which is then passed on to aws4.

Hey I implemented the basic features to send either a template or a html email. Gonna keep adding support for all the fields on the api request to send emails.

Describe the bug

Error after upgrade

/bin/busybox:1 ELF

^

SyntaxError: Invalid or unexpected token at Object.compileFunction (node:vm:360:18) at wrapSafe (node:internal/modules/cjs/loader:1055:15) at Module._compile (node:internal/modules/cjs/loader:1090:27) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1180:10) at Module.load (node:internal/modules/cjs/loader:1004:32) at Function.Module._load (node:internal/modules/cjs/loader:839:12) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12) at node:internal/main/run_main_module:17:47

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior A clear and concise description of what you expected to happen.

Environment (please complete the following information):

• OS: [e.g. Ubuntu Linux 18.04]
• n8n Version [e.g. 0.119.0]
• Node.js Version [e.g. 14.16.0]
• Database system [e.g. SQLite; n8n uses SQLite as default otherwise changed]
• Operation mode [e.g. own; operation modes are own, main and queue. Default is own]

Additional context Add any other context about the problem here.

Closes #794

This PR introduces new credential type for AWS S3 node that supports custom S3 compatible object storage services, such as min.io, swift etc.

New credential type allows to set the URL of an endpoint as well as the method to access buckets: virtual-host style (bucket.s3.endpoint.com) or path style (s3.endpoint.com/bucket). The latter is required for aforementioned min.io, for example.

Please let me know if any changes are required

Hey Jan, how do I build the source and run it from node index.js? I want to deploy on plesk.

I tried a lot of things for hours but nothing seems to work. When I try to "build" via VS Code I get following error: error TS2688: Cannot find type definition file for 'jest'. error TS2688: Cannot find type definition file for 'node'.

Some operation I did got me the folder "dist" but even when I run that, there are errors.

Please help or give me a hint. Thanks Sven

This PR adds the ability to get additional fields for the Folder:List operation to the NextCloud Node.

Before this change the user is able to get from NextCloud Folder:List only default file or folder properties.

After this change the user is able to get any file or folder property for Folder:List operation by specifying fields to include in the "Additional Options" field for Folder:List operation. Those fields are:

1. Comments Unread
2. Contained File Count
3. Contained Folder Count
4. Content Type
5. eTag
6. Favorite
7. File ID
8. File Path
9. Has Preview
10. Last Modified
11. Owner Display Name
12. Permissions
13. Resource Type
14. Share Types
15. Size

Here is how they look:

I'm submitting this pull request in reference to issue #4162 #959 #36 where we were having difficulty setting up n8n on DigitalOcean app platform and encountered some strange behavior when using nginx reverse proxy. This is an issue that some of the earliest users had when using N8N, and is hard to pinpoint when configured wrong.

The problem is the Server Side Event that will push the workflow status to the UI. After a lot of researching, I believed that using a WebSocket over an EventSource would fix the problem and have the following benefits:

• No need to worry about having n8n behind a reverse proxy (e.g. Cloudflare)
• No need to disable proxy_buffering & chunked_transfer_encoding for the entire app with nginx (which was causing SSE connections to get stuck)
• Ability to run n8n on cloud platforms
• Possibility to add a One-click deployment on DigitalOcean button (https://docs.digitalocean.com/products/app-platform/how-to/add-deploy-do-button)
• Opens the opportunity to add live editing capability in the future to make it possible to work on larger workflows with multiple people. (maybe ill work out a proof of concept in the future)

As a non-security expert, I cannot confidently say whether replacing the SSE with a WebSocket will raise any security concerns. However, I have tested this change with another client origin, and it appears to adhere to CORS rules. More investigation is needed, I think. The change is tested local, on Digital Ocean App platform, and works with SSL.

I hope this provides some additional benefits for our community and will lower the barrier to entry for new users.

Please let me know if there is anything else I can do to help make this PR happen :)