Live data from Hacker News

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

trigger.dev

91–100 of 196 posts

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

#91

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 also do this at windmill: https://github.com/windmill-labs/windmill

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

#92

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…

We do this at windmill https://github.com/windmill-labs/windmill, including self-hosting instructions and pre-made integrations with stripe

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

#93
post #5

i think an open source zapier alternative would be a desktop app that had a nice UI, and synthesized terraform/FaaS code/API gateway-equivalent stuff behind the scenes and then ran it against my preferred cloud provider account. not this, as convenient for some as it may be.

We do not provide a desktop app, but we provide the FaaS and instructions to self-host wherever: https://github.com/windmill-labs/windmill

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

#94
post #23

This is fascinating. It checks a lot of my boxes. I was recently looking at ActionsFlow [0] which is similar but runs on GitHub Actions. My thoughts - 1. I don't see proper secret storage being handled. You typically don't want your API keys in your code. What would you recommend instead? 2. "OAuth" based secrets. Many integrations require giving access to an App via OAuth, which involves a flow. I think that's being…

We support both typescript and python at windmill [1]. But our model is doing low-code for the workflows, and actual scripts/code for the steps themselves so it's quite different than trigger.dev. We handle OAuth, refresh tokens and secrets being managed by the platform. It's quite different from trigger.dev considering they are doing workflows entirely in code which has some pro and cons.

[1]: https://github.com/windmill-labs/windmill

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

#95
post #20

I forgot to mention in the original post we've built a bunch of example workflows here: https://github.com/triggerdotdev/trigger.dev-examples

Is there a brief description of what each example is? After following that link, I was just looking for one or two sentences, without having to look through each script.

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

#96

Earlier quoted context omitted.

Zapier's UI is a hot mess. If you breathe on a zap it turns off. Default names for zaps are "Untitled Zap". Pricing is very high for any sort of serious traffic. The webapp runs very slow. But most important, no one knows how to say "Zapier". Is it ZAHpier or ZAYpier?

Rhymes with happier.

Then it should have been spelled Zappier.

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

#97

How does this compare to Pipedream and Windmill, both of which are also open-source?

Founder of Windmill here, and d-k-p answer is spot-on. If you want to manage your entire workflows as a typescript code, then trigger.dev would be preferable. Windmill supports typescript, python, go and bash, and handle all the advanced features such as retries, approval steps, pre-made integrations to hundreds of API at the workflow level in a UI-based editor. Then for the steps, themselves. you would use either your IDE and sync to Windmill, or use our web IDE.

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

#98

Please make curl example on how to send custom event , instead of using nodejs sdk ?

Yes, the best API documentation includes curl examples regardless of any other examples.

With SDK examples you have to set up a code project, install the SDK, add some boilerplate code, make the API call, and figure out out to display/use the output. Ugh.

With curl examples you can run the example with no set up, just a little customization. You just run a single command. Easy-peasy.

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

#99

For people who are building durable workflows. You should definitely checkout temporal [1]. It is production ready, you can implement pretty much same using the original SDK of the underline services. [1] https://temporal.io/

Their pricing model is much preferred: https://temporal.io/cloud i.e. pay for what resources you use instead of how many users you have. This is how we pay for AWS/GCP/Azure. I think a lot of dev SaaS could / should go this way.

Unfortunately there's currently a steep mandatory support charge of $200 a month, which makes it unviable for smaller operations. I think they're planning to offer the service without the support aspect, which would be fantastic and I'd be first in line for..

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

#100

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…

"A simpler alternative to Temporal" is a good description for us. We'll get a self-hosting guide up soon for you. We're adding integrations that people ask for as fast as we can build them and Stripe is high on that list :)
Post reply on HN