Show HN: We built a developer-first open-source Zapier alternative
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.<p>My thoughts -<p>1. I don&#x27;t see proper secret storage being handled. You typically don&#x27;t want your API keys in your code. What would you recommend instead?<p>2. &quot;OAuth&quot; based secrets. Many integrations require giving access to an App via OAuth, which involves a flow. I think that&#x27;s being handled internally from the video [1] and from this project [2], but it&#x27;s not clear. How is that handled?<p>A common use case I&#x27;d automated once is that when a GitHub project gets starred, the developers public information is scrapped and they are then followed on Twitter, if their twitter handle is found. With Trigger.dev, the twitter part isn&#x27;t clear.<p>3. Error Handling - What about when some job fails to run? I understand there is a delay mechanism. But what about injecting custom error handling? Sending a message on slack, for example.<p>4. Dashboards - They look awesome. And I get the impression that each &quot;action&quot; in the code is mapped to individual blocks in the dashboard. I&#x27;d love to be able to see a proper graph of the flow.<p>I love that I can see the json request &#x2F; response for each. It&#x27;ll make debugging easier when some API changes or fails.<p>5. No Code solutions - In the long run, I can easily picture writing the integration I want in plain text, and having Github CoPilot or ChatGPT generate the code for me, and then I can quickly modify it.<p>6. Incentive for integrations - As with most automation tools, entering the market is challenging as you&#x27;re lacking integrations. The awesome thing about ActionsFlow [0] was that it was re-using an existing community of GitHub Actions, and therefore you don&#x27;t start from scratch. Have you thought about reusing workflows from n8n or other projects?<p>7. Integrating with existing Automations -  I think a bit more focus should be made on integrating with IFTTT &#x2F; Zapier &#x2F; n8n. I see you provide webhooks, but I think some easy wrappers + documentation would be better. This way, I can try out newer workflows in Trigger, and easily just extend my existing system. And then if Trigger.dev works for me, I can think about migrating away from my existing automation solution.<p>8. Open Source Longevity - Trigger.dev is MIT licensed. Could you please explain the rationale? How do you plan to combat someone launching a competitor using your code? N8n is deliberately &quot;Soure Code Available&quot; and not &quot;Open source&quot;, which I thought was a decent compromise. Will you be following a more Open Core model similar to GitLab (which is also MIT licensed)?<p>9. De-coupling runners and the dashboard - I&#x27;d love to not have the pain of maintaining the dashboard &#x2F; event listeners, but being able to control the running of the jobs. Similar to a CI or Airflow.<p>10. Support for other languages - This is something that Dagger CI [3] now allows. Letting you use whatever programming language. With Github Actions, I can just package it as a container. Do you plan to support anything else?<p>After moving from using HCL to Typescript for my Terraform code, the advantage is so great, that I can&#x27;t seem myself going back to using a custom language such as Dagger&#x27;s CUE [4]. Trigger.dev targeting Typescript is already a big win. However, I do have a number of automations in Python.<p>Overall, I&#x27;m super optimistic. Congratulations on the launch.<p>[0] - <a href="https:&#x2F;&#x2F;actionsflow.github.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;actionsflow.github.io&#x2F;</a><p>[1] - <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=aFlwD0frvnQ">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=aFlwD0frvnQ</a><p>[2] - <a href="https:&#x2F;&#x2F;github.com&#x2F;triggerdotdev&#x2F;Pizzly">https:&#x2F;&#x2F;github.com&#x2F;triggerdotdev&#x2F;Pizzly</a><p>[3] - <a href="https:&#x2F;&#x2F;dagger.io&#x2F;">https:&#x2F;&#x2F;dagger.io&#x2F;</a><p>[4] - <a href="https:&#x2F;&#x2F;docs.dagger.io&#x2F;1215&#x2F;what-is-cue&#x2F;">https:&#x2F;&#x2F;docs.dagger.io&#x2F;1215&#x2F;what-is-cue&#x2F;</a>