Live data from Hacker News

Show HN: We built a developer-first open-source Zapier alternative

trigger.dev

171–180 of 196 posts

Re: Show HN: We built a developer-first open-source Zapier alternative

#171
post #126

This looks great. I'll have to play around with it. Related, we built a developer oriented Zapier clone for event scale automations awhile back for our internal product. We've since pivoted and have been debating on potentially open sourcing the engine as well. We built ours using Rust with a DSL for all the triggers, actions, and action inputs/outputs. The actions themselves are defined as APIs, which makes it easy…

Yes, definitely. Put it on github, create a discord and see if a community forms around it.

Re: Show HN: We built a developer-first open-source Zapier alternative

#172
post #123

Earlier quoted context omitted.

Does windmill have any way of going into code, without it basically becoming "code in a input box". The developer first solution trigger.dev have here is really scratching a real problem. But as they say they are not for the easiest workflows. I'm really looking for something that is gui first but as a drop down to code when you want. But inline code editor, let me save it to a git repo or similar. And don't have glo…

> I'm really looking for something that is gui first but as a drop down to code when you want. But inline code editor, let me save it to a git repo or similar. That's like, exactly what we are, take a look at this screenshot for instance: https://github.com/windmill-labs/windmill/blob/main/imgs/win... As for syncing code to git, we do it as well through our CLI and Github Actions: https://github.com/windmill-labs/win…

WOW. I have been looking into this at work today, and windmill is def. what I was looking for, a low-code solution that do not hate code (as text). Thank you so much for creating this. The value prop. that you have in the intro[1] is perfect. The first paragraph on github is maybe correct. But I'm still not sold on what it actually does. Marketing is hard. Hope you will succeeded, the product looks great!

[1] https://docs.windmill.dev/docs/intro/

Re: Show HN: We built a developer-first open-source Zapier alternative

#173

Earlier quoted context omitted.

We do this at Activepieces (activepieces.com).

Is there an API or SDK for creating/managing flows? I want the flexibility to programmatically wire these integrations together rather than a nocode UI Additionally, this seems to rely on you inputting your credentials. How would that work for a usecase where my customers are the ones who provide the credentials?

Not yet, we're probably on the way there as we're exposing all our pieces (connectors) as typesafe npm packages. But for now, flows are built with the no-code UI. The workaround is to write all your code in one main Code step in any flow. Our web IDE is VS Code so it's not too much different, and we can be self-hosted.

On the UI, you can customize the credentials with a connection variable which is what enables in-app product integrations. We have users who are doing this. Shoot me an email if you'd like to explore our approach: ash@activepieces.com

Re: Show HN: We built a developer-first open-source Zapier alternative

#174
post #163

As someone who got burned by past "Open Source" projects, yours raises all redflags: - Advertised as "Open Source", yet this is actually a paid product with a pricing page. - You don't even have a guide on how to install this thing... euh, I mean what's the point of this if I can't use it? - You have a complicated license: https://github.com/triggerdotdev/trigger.dev/blob/main/LICEN... . You might have an "open" sour…

I don’t see an ee folder or ee/LICENSE so according to their license, everything in their repo seems open source although annoying they did this instead of just a real OSI recognized license.

Not having install docs isn’t the end of the world if I can figure it out and contribute back. But I don’t want to waste my time if it’s not actually open source and my work will be commercialized by a single org.

I don’t mind contributing for everyone to do whatever (including commercialization) but am not into doing free labor for a profit enterprise.

Re: Show HN: We built a developer-first open-source Zapier alternative

#175

This looks great, congrats on the launch! I am interested in a platform that bundles many pre-built integrations to various services that I could wire up through code and execute on my customers' behalf. Essentially, a way for me to present my customers with a plethora of integrations out of the box without having to build them all myself. This seems like it's moving in that direction and I saw another comment where…

We do exactly this at https://integration.app, including ability to manage flows via API.

We are focused on CRMs / Marketing tools for the next couple of months though.

Re: Show HN: We built a developer-first open-source Zapier alternative

#177

‘Developer-first Zapier alternative’ is an odd positioning, I think the point of Zapier is that it’s for non-developers mainly. Looking at the comments, though, it seems like there’s a need for something like this. Keen to see how you iterate and improve your positioning. Good luck!

My experience with Zapier is that you quickly hit a point where you’re building an ultra complex expression or manipulating json in a less than ideal editor. Also your zap is basically the ast of the code you would have written and grows quickly. Code is far more terse.

That said, long running durable workflow tools that are targeted at devs all have challenges. There’s room for a Goldilocks solution. I’d imagine temporal will win though.

Re: Show HN: We built a developer-first open-source Zapier alternative

#178
post #144

Earlier quoted context omitted.

Thanks! Have you contemplated making the backend open source or at least source-available ("Look but don't touch", you may only use the hosted service, etc)? Would love to take a look at the implementation

*looks around* I haven’t announced it yet -- but yes. Working towards open sourcing everything. :)

Oh god thank you for your work.

Re: Show HN: We built a developer-first open-source Zapier alternative

#179
post #157

I was recently looking for a simpler alternative to Temporal ( https://temporal.io/ ) so this could be ideal. If you could add instructions for self-hosting it (_sounds_ like you just need an Express server, but I would guess some backend persistent store/database/queue too) that would be great. The Webhook catalog only lists Github: I think integrating with Stripe would be neat. Like, when someone pays an invoice, S…

As someone curious to try out Temporal. What makes you think it is not simple, is it tricky enough that one should avoid it? What else makes this Trigger.dev stand out compared to Temporal? Temporal already has self hosting option, multiple language support and a battle proven history. Even if trigger looks good on paper, it would need some other really convincing reason for me to consider a completely fresh tool ove…

I share that curiosity! Temporal looks great and is proven. Running it looks simple enough. I mean getting their self-hosted version deployed (to production). I was reading through their docs and that does _not_ look simple (to me). Plus the guide is open about being a work in progress (https://docs.temporal.io/cluster-deployment-guide#elasticsea...). I am going to try it at some point though.

Re: Show HN: We built a developer-first open-source Zapier alternative

#180
post #163

As someone who got burned by past "Open Source" projects, yours raises all redflags: - Advertised as "Open Source", yet this is actually a paid product with a pricing page. - You don't even have a guide on how to install this thing... euh, I mean what's the point of this if I can't use it? - You have a complicated license: https://github.com/triggerdotdev/trigger.dev/blob/main/LICEN... . You might have an "open" sour…

I don’t see an ee folder or ee/LICENSE so according to their license, everything in their repo seems open source although annoying they did this instead of just a real OSI recognized license. Not having install docs isn’t the end of the world if I can figure it out and contribute back. But I don’t want to waste my time if it’s not actually open source and my work will be commercialized by a single org. I don’t mind c…

The wording suggests to me that there can be ee/ subdirectories scattered all through the directory tree, and within those the different licenses apply.
Post reply on HN