Live data from Hacker News

Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra

pipedream.com

71–80 of 113 posts

Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra

#71

Earlier quoted context omitted.

Forgive me if this is clean and I haven’t seen it I’m just browsing from a mobile device. With all workflow type services I’ve encountered I find that the actual underlying workflow can’t be managed under source control as one would do with (hopefully) most if not all application & infrastructure code. Can I “deploy” workflows from source control?

Hi, Dylan, a co-founder here. Deploying workflows from source via CLI or your CI/CD pipeline is in the works! We want you to host workflows on Github / Gitlab and be able to deploy them using your standard process. Feel free to reach out to me directly if you'd like more information and I can let you know when we're testing this. dylan [at] pipedream [dot] com

Speaking of which, it's always overwhelming learning new tools. I know I can benefit from this, but at the same time I'm not sure I can risk trying it out given the time it will take to experiment and learn. I'd be using triggers based off Github commits and merges, but I don't see any specific examples for that and it's not exactly clear how the tutorial on the home page would translate to what I want to do so I currently feel deterred from giving it a whirl. Are there plans to create more tutorials? What kind of (rough) timeline can we expect to see more tutorials?

BTW, love the name Pipedream!

Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra

#72

Why would I use this instead of an option built into a major cloud provider such as AWS, GCP, or Azure? How do you differentiate yourself. Do you (or will you) support frameworks like Serverless?

Hi, Dylan, a co-founder here. It's a great question. We've found that for integrations or common automations, building on a cloud platform is too low-level. You've got to manage a number of services that aren't core to your use case (e.g. API Gateway, IAM, Cloudwatch Logs, etc.). We operate at a higher level and just give you an execution environment to run Node.js code or stitch together pre-built actions, similar t…

How would you differentiate yourself from Microsoft Flow?

Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra

#73

Congrats on launching! I'm a founder of a startup in the same space, so just wanted to say good luck. I love the name. It's exciting to see so many folks working on making connective developer tooling a better experience. I had a link originally included in here but -- you guys should enjoy your launch. I understand and have a great deal of empathy for the effort it takes to build and launch something new. Enjoy all…

Keith, this is Dylan, a co-founder. We've been very impressed with what y'all are building at Standard Library and I agree it's a great time to be working on developer integration tools! Thanks for the note.

Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra

#74

Earlier quoted context omitted.

Hi, Dylan, a co-founder here. It's a great question. We've found that for integrations or common automations, building on a cloud platform is too low-level. You've got to manage a number of services that aren't core to your use case (e.g. API Gateway, IAM, Cloudwatch Logs, etc.). We operate at a higher level and just give you an execution environment to run Node.js code or stitch together pre-built actions, similar t…

How would you differentiate yourself from Microsoft Flow?

I haven't used Microsoft Flow in depth so I unfortunately can't comment.

If you've used it and like it, I'd honestly love for you to give Pipedream a try and tell us where we can improve compared to your experience with other tools. We'd love the feedback!

dylan [at] pipedream [dot] com

Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra

#77
post #2

Co-founder here. We have been heads down working Pipedream for the past 9 months and are excited to share our beta with you. Pipedream is an integration platform built for developers. Develop any workflow, based on any trigger with authentication management built-in and no server or cloud resources to manage. Workflows are code, which you can run for free. The beta version includes the ability to: - Run any Node code…

I'm not trolling, but what's the difference between Pipedream and Microsoft Flow?

Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra

#78

Earlier quoted context omitted.

So basically, people are going to build on top of your service and if yall don't figure out a revenue model, you'll need to close down shop, leaving people scrambling to migrate somewhere else... No thanks, I've been there before. You'd be better off just charging from the get-go. Otherwise, this should be 100% open source.

From your past experience, do you have anything constructive to tell this new team on how they can attempt to build a business without knowing the future that would make you more comfortable using it? I ask because I see a lot of these dismissive comments on HN which end with "open source it" - and that doesn't seem like a super constructive piece of advice to a new startup team. FWIW, at my current company, an analy…

Start charging immediately, and put up a real pricing page with SLAs. Find out as soon as possible if people will actually value this enough to pay for it.

This provides a signaling of value, creates a real business relationship, and directly contributes to the lifespan of the vendor.

Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra

#79

I'd have an easier time evaluating pipedream if I got something other than a blank page when clicking through to the website from my mac running chrome.

Hi David, this is Dylan, a co-founder. I'd love if you had the time to send me a screenshot of what you're seeing, with your Developer Tools Console open in Chrome, if you don't mind. It'd be a huge help!

dylan [at] pipedream [dot] com

Re: Show HN: Pipedream. Develop any workflow, on any trigger, with auth and no infra

#80
post #76

I like it but I don't fully get it. Why use this service and not Lambda or Azure Functions?

Hi, this is Dylan, a co-founder. It's a great question. Having built many applications on Lambda this is something I think about a lot :) .

We've found that for integrations or common automations, building on a cloud platform is too low-level. Frequently you're working with more than just a Lambda. You've got to manage a number of services that aren't core to your use case (e.g. API Gateway, IAM, Cloudwatch Logs, etc.). There's a lot of boilerplate config, and many of these services are tangential to the core logic of your app.

We operate at a higher level and just give you an execution environment to run Node.js code or stitch together pre-built actions, similar to integration platforms like Zapier. We manage the HTTP endpoint, function config, and give you built-in observability. We also provide higher-level services, like built-in app integrations and OAuth / API key-based authorization. Building this yourself on AWS can take time.

This kind of abstraction isn't great for every application, but we think it shines when you're building integrations between services.

Let me know if that answers your questions, or if you have any more!

Post reply on HN