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.
Thanks! The horizontal scrolling issue looks fixed. Unfortunately, though, the hamburger menu still isn’t working, and strangely it looks as if whole site is rendered twice?
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!
My other pipedream in addition to this would be multi tenancy (including integrations).
A perfect world scenario is a drop in multi tenant zapier alternative that enables SaaS providers to either create workflows for their users so all they need to do is authenticate integrations for the most part or allow for them to build their own workflows from scratch.
I realize this is probably out of scope of the services aim but it doesn't hurt to throw it out there since all of the alternatives that exist are sorely lacking in various ways.
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
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.
Hey, I'm the maintainer of OpenFaaS. Thanks for mentioning the project.
Pipedream v1 ran on Lambda, but this post is touted as "AWS Lambda alternative", have you moved off the AWS Lambda platform?
I was curious how you added support for other languages, was it in the same way that you built-in support for Node.js? Where all the code gets effectively built into a single Lambda function and proxied?
For people who want to call OpenFaaS workloads from Pipedream, that's possible over HTTP and Pipedream makes that relatively simple. One thing I think they've really nailed is the OAuth integration, it just makes that whole painful flow a lot more convenient. I also like the editor and the way it infers what kind of input will go into the next step in a workflow.
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.
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.
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!
