Earlier quoted context omitted.
Thank you so much! We have actually put so much effort into developer experience, especially for building new integrations. You can check examples using oauth authentication: https://automatisch.io/docs/build-integrations/examples If you want to check out all documentation for building integrations, you can use this page: https://automatisch.io/docs/build-integrations/folder-struct... My suggestion would be that you…
Great stuff! FWIW I've been looking for a "some code" platform, that removes the overhead and plumbing requirements for automation, but still allows arbitrary code to run in the automations. Basically, I can code, but there are loads of things about web development I have no interest in or want to think about. What would be amazing to me would be a way in which APIs can be abstracted away and a low code API for vario…
Show HN: Automatisch – Open source workflow automation, an alternative to Zapier
31–40 of 59 posts
Re: Show HN: Automatisch – Open source workflow automation, an alternative to Zapier
#32Re: Show HN: Automatisch – Open source workflow automation, an alternative to Zapier
#33The installation instructions mention Render but doesn't say what it's needed for, or if it's needed. Is only the Docker needed? Can you provide more details on the installation page?
The other installation methods are docker (https://automatisch.io/docs/guide/installation#docker) and docker compose. (https://automatisch.io/docs/guide/installation#docker-compos...) You can choose one of them. I think most of our users are using Docker setup atm.
Please let me know if you have any other questions.
Re: Show HN: Automatisch – Open source workflow automation, an alternative to Zapier
#34I 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.
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, an alternative to Zapier
#35Language: Typescript
Re: Show HN: Automatisch – Open source workflow automation, an alternative to Zapier
#36A mastodon/activitypub output action (or input trigger) would be cool.
Re: Show HN: Automatisch – Open source workflow automation, an alternative to Zapier
#37Your integrations logo wall has the postgres elephant, but I don't see Postgres in the list. A mastodon/activitypub output action (or input trigger) would be cool.
We have initially thought of developing that integration already. However, circumstances had us postpone it for a while. We already have an integration request for postgres on https://github.com/automatisch/automatisch/discussions/858.
I'd appreciate it if you could give an upvote to that discussion so we can prioritize the integrations accordingly.
Re: Show HN: Automatisch – Open source workflow automation, an alternative to Zapier
#38I didn't find them.
You guys are https://automat.berlin/contact/ , right? A GmbH.
For credibility, legal, and fine reasons, get a product-specific imprint and data policy up and available as soon as possible.
Re: Show HN: Automatisch – Open source workflow automation, an alternative to Zapier
#39I 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.
Re: Show HN: Automatisch – Open source workflow automation, an alternative to Zapier
#40Earlier quoted context omitted.
From gleaning at the repo's license, they use AGPL. So that seems tailored towards building a business around it. I find that quite exciting, because I have been thinking about which license to use for a project of mine as well, so that a) it is open-source, and b) I can build a business on top of it. AGPL seems to fit the bill perfectly, as long as you are careful about the license of contributions.
We spent some time to research about licenses. AGPL allows us to keep it open source and also build a business around it as you said.