Re:Show HN: Automatisch – Open source workflow automation, a...
by farukaydin on Wednesday January 25, 2023 @11:55AM
(#34520737)
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.
Re:Show HN: Automatisch – Open source workflow automation, a...
by rubenfiszel on Wednesday January 25, 2023 @12:06PM
(#34520914)
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
Pipedream (which is probably Automatisch main competitor) also has a repo full of integrations: 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 ...
Re:Show HN: Automatisch – Open source workflow automation, a...
by swyx on Wednesday January 25, 2023 @02:14PM
(#34522812)
ah the ole xkcd 927 strikes again :)
Re:Show HN: Automatisch – Open source workflow automation, a...
by sneak on Wednesday January 25, 2023 @04:13PM
(#34524260)
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.
Re:Show HN: Automatisch – Open source workflow automation, a...
by leetrout on Wednesday January 25, 2023 @07:46PM
(#34526352)
CloudEvents is trying to standardize on the messaging
Re:Show HN: Automatisch – Open source workflow automation, a...
by ilyt on Thursday January 26, 2023 @01:57AM
(#34528514)
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.
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.