Skip to main content

New best story on Hacker News: Show HN: We built a developer-first open-source Zapier alternative

Show HN: We built a developer-first open-source Zapier alternative
490 by eallam | 138 comments on Hacker News.
For the past few months we’ve been building Trigger.dev and can now share our beta with you: https://ift.tt/1cJvEVk . Trigger.dev is an open source platform that makes it easy for developers to create event-driven background tasks directly in their code. You write workflows using our SDK, and can view all the runs in our web app. Why we built this: - We found current workflow / automation tools like Zapier and n8n are good for simple tasks, but not for more advanced use cases. - Dropping down into code in these tools is just not a great experience. We prefer using our own IDEs, version control, and having access to GitHub Copilot etc. - Sometimes, a workflow requires us to query a database or handle some sensitive information. It would be great if this data wasn’t sent to a third party. Our beta version lets you: - Trigger workflows from webhooks, custom events or schedules (CRON) - Use API integrations with Slack, GitHub, Shopify and Resend. We’re adding more of these each week. - Add delays of up to 1 year. Workflows will resume where they left off, even if your server has gone down. - Support for Fetch and subscribing to generic webhooks. - Observe every workflow run in the app (great for debugging). - Open source MIT license so anyone can self-host the platform. We’re still early so would love your feedback and opinions. Feel free to try us out for free – and if you want a specific API integrated, just let us know. Main website: https://trigger.dev Github: https://ift.tt/1cJvEVk

Comments

Popular posts from this blog

New best story on Hacker News: Ask HN: I’m an FCC Commissioner proposing regulation of IoT security updates

Ask HN: I’m an FCC Commissioner proposing regulation of IoT security updates 449 by SimingtonFCC | 144 comments on Hacker News. Hi everyone, I’m FCC Commissioner Nathan Simington, and I’m here to discuss security updates for IoT devices and how you can make a difference by filing comments with the FCC. As you know, serious vulnerabilities are common in IoT, and it often takes too long for these to be patched on end-user devices—if the manufacturer even bothers to release an update, and if the device was even designed to receive them. Companies may cease supporting a device well before consumers have stopped using it. The support period is often not communicated at the time of sale. And sometimes the end of support is not even announced, leaving even informed users unsure whether their devices are still safe. I’ve advocated for the FCC to require device manufacturers to support their devices with security updates for a reasonable amount of time [1]. I can't bring such a proposal