3 ms·

I currently use n8n, but always great to see more alternatives in this space. One thing that has surprised me is that no one has tried to standardize on the Za

I currently use n8n, but always great to see more alternatives in this space. One thing that has surprised me is that no one has tried to standardize on the Zapier or IFTTT APIs / SDK implementation to allow for faster deployment of integrations. Seems like there could be a movement here that is akin to how many services use S3 compatible APIs.

farukaydin 4y ago
We checked their abstraction, but it was not a good match with what we have in our minds. Apart from that, it also differs for architectural reasons because they don't have to make it self-hostable, which also affects how they build/run the integrations.
rubenfiszel 4y ago
We noticed that too and thought scripts with simple main functions and their parameters could be the universal layer for integrations, so we (Windmill) built an open-source hub for it https://hub.windmill.dev https://hub.windmill.dev Pipedream (which is probably Automatisch main competitor) also has a repo full of integrations: https://github.com/PipedreamHQ/pipedream https://github.com/PipedreamHQ/pipedream. Their format is a bit more specific than Windmill. Hopefully, we all agree on a format and differentiate ourselves on the quality of the orchestration, flow capabilities, performance etc ...
swyx 4y ago
ah the ole xkcd 927 strikes again :)
sneak 4y ago
n8n is not open source. There is an argument (that I agree with) that the AGPL (used by this project) is not a free software license either, for similar reasons, but this does not seem to have consensus yet.
leetrout 4y ago
CloudEvents is trying to standardize on the messaging https://cloudevents.io/ https://cloudevents.io/
ilyt 4y ago
It's because they are dozen of those automation clicky things each slightly different and with slightly different featureset that fits this or that workflow better.
avinassh 4y ago
n8n is not open source, while Automatisch is GPL. https://github.com/n8n-io/n8n/blob/d1b4d42/LICENSE.md https://github.com/n8n-io/n8n/blob/d1b4d42/LICENSE.md

farukaydin 4y ago

We checked their abstraction, but it was not a good match with what we have in our minds. Apart from that, it also differs for architectural reasons because they don't have to make it self-hostable, which also affects how they build/run the integrations.

rubenfiszel 4y ago

We noticed that too and thought scripts with simple main functions and their parameters could be the universal layer for integrations, so we (Windmill) built an open-source hub for it https://hub.windmill.dev https://hub.windmill.dev Pipedream (which is probably Automatisch main competitor) also has a repo full of integrations: https://github.com/PipedreamHQ/pipedream https://github.com/PipedreamHQ/pipedream. Their format is a bit more specific than Windmill. Hopefully, we all agree on a format and differentiate ourselves on the quality of the orchestration, flow capabilities, performance etc ...

swyx 4y ago

ah the ole xkcd 927 strikes again :)

sneak 4y ago

n8n is not open source. There is an argument (that I agree with) that the AGPL (used by this project) is not a free software license either, for similar reasons, but this does not seem to have consensus yet.

leetrout 4y ago

CloudEvents is trying to standardize on the messaging https://cloudevents.io/ https://cloudevents.io/

ilyt 4y ago

It's because they are dozen of those automation clicky things each slightly different and with slightly different featureset that fits this or that workflow better.

avinassh 4y ago

n8n is not open source, while Automatisch is GPL. https://github.com/n8n-io/n8n/blob/d1b4d42/LICENSE.md https://github.com/n8n-io/n8n/blob/d1b4d42/LICENSE.md