cloud-run-hello-app-demo VS pipedream

$ git clone https://github.com/subfuzion/cloud-run-hello-app-demo.git $ cd cloud-run-hello-app-demo $ gcloud run deploy $SERVICE --source=. --allow-unauthenticated This command is equivalent to running `gcloud builds submit --pack image=[IMAGE] .` and `gcloud run deploy hello --image [IMAGE]` Building using Buildpacks and deploying container to Cloud Run service [hello] in project [cloud-run-hello-app-demo] region [us-central1] ✓ Building and deploying new service... Done. ✓ Uploading sources... ✓ Building Container... Logs are available at https://console.cloud.google.com/cloud-build/builds/d71d846a-782d-4161-bbfa-a3f289ae669a?project=243539805744]. ✓ Creating Revision... ✓ Routing traffic... ✓ Setting IAM Policy... Done. Service [hello] revision [hello-00001-wek] has been deployed and is serving 100 percent of traffic. Service URL: https://hello-5maonkvcja-uc.a.run.app

https://github.com/PipedreamHQ/pipedream/issues/954

No I don’t think so. You probably want n8n if you’re keen on self-hosting.

Not sure if IFTTT has a plugin but I suspect not, I've currently got a Pipedream feature request that they are now adding it to their platform (it's not ready yet) but you'll still need to request the API access yourself. Pipedream: Google My Business Feature Request (I am NebularNerd)

We noticed that too and thought scripts could be the universal layer for integrations, so we built a hub for it https://hub.windmill.dev

Pipedream (which is probably Automatisch main competitor) also has a repo full of integrations: https://github.com/PipedreamHQ/pipedream. Their format is a bit more specific than Windmill.

Hopefully, we all agree on a format and differentiate ourselves on the quality of the orchestration, flow capabilities, performance etc ...

Hey, try opening one of: - https://github.com/PipedreamHQ/pipedream - https://github.com/gitpod-io/template-flutter

Yup it's something that's been on the backlog for a bit and we're trying to solve for.

Here's the issue if you'd like to follow: https://github.com/PipedreamHQ/pipedream/issues/193

It is possible to make a custom source for ForwardEmail, and then emit 1 action per row, but that requires writing code outside of the GUI.

Definitely hear you on this pain and we're working on it.

But you can run custom Node.js code anywhere you need it, extending any of the built-in actions or adding your own. This is where Pipedream shines. You can quickly transition from a no-code workflow to a Node.js serverless function as you need more complex logic.