dylburger

Take a look at https://pipedream.com/apps/openai/actions/summarize

Sorry for the delay. You can make an integration for others! See https://pipedream.com/docs/components/guidelines/#process .

We do a little work to create the shell of the app integrations, e.g. we add the logo, for OAuth apps we configure the details of the OAuth authorization / refresh process, etc. Then you can develop any sources or actions for the app and publish them for all Pipedream users.

The best place to chat is on our public Slack or GitHub, if you're interested. See https://pipedream.com/support .

We corrected this, and I think it's a lot more clear now. Thanks for mentioning!

Fixed in https://github.com/PipedreamHQ/pipedream/commit/27fd34aa1cb0... . Thanks!

Hey Alex!

We build our own containers and still run them on Lambda. The container base image contains the necessary language runtimes so that we can execute both Node.js and e.g. Python in the same workflow.

Do you think it would make sense to add an OpenFAAS integration to Pipedream? Then it would show up when users searched for it in workflows, and have a dedicated page at https://pipedream.com/apps . Even if we just end up wrapping HTTP requests to kick off a function, we've found it's helpful because users are often searching for FaaS platforms by name when they want to integrate with them in a workflow.

Yes we're thinking a lot about this. The vision would be let you execute workflows on whatever function runtime you use. So you'd have one definition of a workflow on Pipedream, but that could be serialized to e.g. a Google Cloud Function, an OpenFAAS function, etc. And you'd get to run it in your own VPC, with access to your own internal resources, without relying on Pipedream's infra.

Still in the idea phase, but let me know if that resonates.

We hear this a lot from devs and we do plan to tackle it. I was building productivity tools (mostly for Gmail / Google Calendar) at my last startup and would have loved to have Pipedream manage OAuth / token refresh, kick off workflows on behalf of my users, etc.

If you're interested, join our community and you'll get early updates on stuff we're working on (GitHub integration, TypeScript / other new language runtimes, etc.): https://pipedream.com/support

The fix for the broken hamburger menu on mobile should be out, thanks again for raising.

You can see our pricing at https://pipedream.com/pricing and a deeper overview / FAQ here: https://pipedream.com/docs/pricing/

We are shipping a fix for this right now! Really glad you noted this. Will let you know when it's out.

I hear you! We're tracking this in a couple of issues:

1. We plan to publish an execution environment (as a container) that simulates the core Pipedream runtime. You could run this locally or as a container on whatever container service you'd like. 2. We get a lot of requests for a fully-self-hosted / open-source version, and we're considering how to approach that as well.

Please follow the issues below, and let us know if you have any more feedback!

[1] https://github.com/PipedreamHQ/pipedream/issues/1635 [2] https://github.com/PipedreamHQ/pipedream/issues/954

Hi, Pipedream co-founder and engineer here. Thank you for noting the concerns. Some questions / thoughts below:

* Would technical docs on our privacy and security practices help? e.g. how we use AWS, specific security controls, automatic data deletion policies?

* Yes, the product is still in beta but maturing quickly. Happy to answer any specific questions where you think lack of longevity will be an issue for you.

* Paid plans for individual developers, teams, and enterprises are coming soon. We started with a free tier to encourage experimentation and solicit feedback while the product is in beta. This has worked well, but lack of pricing is one of the top pieces of feedback - I hear you clearly on the concern.

* We've raised the quota for early users who need that added time, and we're happy to do it if you expect you'll need that for your workflows. In general, we expect the 30 min daily quota to stay that way for users of the free tier. You'd then be able to pay for additional time.

Let me know if that helps and reach out to dylan [at] pipedream [dot] com anytime.

Thanks! Long-term, we're building Pipedream to be a fully-programmable platform for managing integrations between apps. Think of it as IFTTT for developers. Paid plans and team features are coming soon.

Event sources are one piece of that. RSS is one type of source, but we're creating sources for Twitter, Slack, Github, and all of the apps supported on Pipedream today [1]. Sources expose a single API for retrieving events from many platforms. So if you just want to run code on new Twitter mentions, Slack messages, or new Github PRs, Pipedream tries to abstract the API-specific details, so you just

    pd deploy

and Pipedream emits new events as the source produces them.

[1] https://docs.pipedream.com/apps/all-apps/

Hi y'all, Pipedream engineer and co-founder here. We just rolled out a new core feature of the platform - event sources - and thought it'd be fun to show off how it works for RSS feeds.

Event sources let you treat an RSS feed like an event stream: Pipedream polls the feed for you, and exposes a REST API and private SSE stream for accessing new items from the feed.

You can also trigger a Pipedream workflow on new items. We built 12 example workflows (linked on the page) for doing all sorts of things with RSS feeds, for example:

- RSS to Email

- RSS to AWS EventBridge

- Run a Puppeteer script to take a screenshot of every new item in an RSS feed

- etc.

Give it a try and let us know if you have any feedback or suggested improvements!

Hi there, Pipedream co-founder and engineer here. Paid plans are coming soon. We launched with a free tier during our beta to let developers experiment and solicit feedback improve the product for the longer-term.

Would love if you had a chance to give it a spin. We're always eager to hear what can be improved.

Hi y'all, Pipedream co-founder and engineer here. We shipped the first version of Pipedream last October, and have heard a lot of requests for an API and CLI to programmatically manage workflows. We shipped the first public version of both, and this README highlights how you can use them to run any Node.js code on a schedule.

For example, you can use the CLI to run this script every 15 seconds:

  echo 'console.log("Hello, world")' > cronjob.js
  pd deploy --run cronjob.js --timer --frequency 15s  # cron expressions also supported with --cron

At this stage, we're looking for any and all feedback on these interfaces. What can we improve? What works and what doesn't? What else do you want to do but can't? Let us know in comments here or on our Slack community [1].

Behind the scenes, we package your Node.js code into a Pipedream component [2] - just a terse way to express Node.js code and its metadata in a reusable way. This interface will improve and evolve over time, but we'd love any feedback y'all have on the component API, too.

If you haven't explored the Pipedream platform at large, give it a go at https://pipedream.com . We let you run serverless workflows, hosted on Pipedream infra, optimized for integrations between services. You can think of us like a Zapier for developers. Check out the docs at

https://docs.pipedream.com

Happy to answer any questions below - thanks for the read!

[1] http://pipedream.com/community

[2] https://github.com/PipedreamHQ/pipedream/blob/master/COMPONE...

Hi, I'm a co-founder and engineer at Pipedream.

Paid tiers are coming soon, and if you hit our daily compute limit before that, we're happy to raise your limit to make sure your workflows run without issue.

Let me know if you have any other questions! Feel free to reach out to me directly at dylan [at] pipedream [dot] com.

Hi y'all, I'm a co-founder at Pipedream. During a recent refactor of our CSP, we used this workflow to store and aggregate CSP violations using SQL to report on our violation data. This helped us find a few entries we missed because our CSP was too strict.

Now that we've got a new CSP running in production, it's nice to get violations sent to Slack so we can identify other potential issues.

Tools like https://report-uri.com/ are great for reporting on CSP violations, but we found this was an easy way to roll our own and get some advanced functionality (SQL, running Node code on each violation to filter and format the violation JSON) with little work.

You can copy and extend this workflow in any way you'd like!

Hi y'all, I'm a founder and engineer at Pipedream, and I wanted to share this workflow I wrote to automate a personal problem I had and show off our tool.

Spotify no longer notifies you when a playlist you follow adds new music, so I wrote a little Node.js code to list all the playlists in my library owned by others, and checks them for new tracks once an hour.

The code for diffing tracks is a little complex, but Pipedream makes it easy to connect my Spotify account and run Node code that uses the OAuth Bearer token tied to my OAuth grant. It hosts the code and runs the job on a schedule, giving me inline observability, emails me on errors, built-in state via the this.$checkpoint variable, etc.

Would love feedback on the workflow and the product. Pipedream is still a young product, so we'd love to know what we can improve. Thanks!

Hi, this is Dylan, a co-founder and engineer at Pipedream.

It's a great question. AWS is incredibly powerful (we use it at Pipedream), but we think Pipedream is better optimized for building workflows and integrations between developer apps and SaaS services. The idea is that we'll save you a lot of time creating and managing these integrations.

We're trying to strike that balance of giving devs the control they need without having to worry about the stuff that shouldn't matter when they're building integrations.

A few ways we differentiate specifically from AWS and other cloud platforms for the integration use case:

- One click "triggers" that enable you to run a workflow on an HTTP request, cron job, or email [1], vs. having to e.g. Terraform a CloudWatch Events schedule or setup an API Gateway / SES email endpoint.

- You can connect third-party accounts within Pipedream and we manage the OAuth flow, giving you programmatic access to your OAuth access tokens. You can manage API keys in the same way [2]. If you've ever had to manage the OAuth authorization flow yourself, storing refresh tokens and generating access tokens, you know how nice it is not to have to manage.

- When you just need to checkpoint the items you've previously processed (common when you're pulling data from an API every few minutes), you don't have to store the data in external state. You can use our built-in checkpoint API to store and retrieve basic state [3].

Also, while you _can_ write Node.js code, you don't have to. Many of our users don't know Node, and exclusively use the actions we've added that abstract common operations [4]. As we add more actions, the tool should be more accessible to "no code" workflows and less technical users.

We'd love if you had a few minutes to sign up and use the tool! If there are things you still like about AWS and want that control in Pipedream, that's exactly the kind of feedback that would help. Send me a note anytime:

dylan [at] pipedream [dot] com

[1] https://docs.pipedream.com/workflows/steps/triggers/

[2] https://docs.pipedream.com/connected-accounts/

[3] https://docs.pipedream.com/workflows/steps/code/#managing-st...

[4] https://docs.pipedream.com/workflows/steps/actions/

Just wanted to follow up to let you know we're starting work on Python soon. Feel free to subscribe to the issue here to get notified of our progress: https://github.com/PipedreamHQ/roadmap/issues/1 .

Hi, this is Dylan, another co-founder and engineer. I'm sorry we dropped the ball here. As you can imagine, it's tough to respond to every request and we've been a bit busy since launch, but I apologize we didn't get to yours.

All of us were early employees of BrightRoll [1], an advertising marketplace that handled 10 million requests / second at peak. We've scaled large systems in the past and we've built this system with scale in mind.

Believe it or not, most workflows are extremely low volume. That, in part with the design of the system, allows us to offer the generous free tier.

We're planning to introduce paid tiers soon. You can see my comment on the parent thread that addresses some of the general questions around pricing asked by others in the thread.

This was a very early release of the platform and we hoped offering the product for free would encourage experimentation. To a great degree, we've seen that, so we think it was the right choice.

[1] https://en.wikipedia.org/wiki/BrightRoll