What is Your Feedback on Creating Custom Pipedream Components?

This topic was automatically generated from Slack. You can find the original thread here.

!channel Happy new year! We wanted to start off the new year by collecting your feedback on the process of creating your own custom Pipedream sources and actions (we call these components). We’d love to know if you’ve created any, how and why you did, and what you think could be improved the tooling and process overall!

Please let us know by filling out this short survey.

Thank you!

done! Although may be redundant info as I said no because no python? Is that still the case?

Thank you! And yes that is still the case today, good reminder on that.

Done, I write and publish custom actions regularly and would still love it if we could do it in Python as well.

Answered the survey, bring it to the Web UI and create it from there :slightly_smiling_face:

have you seen that you can publish actions directly from the builder?

Ah this is great thanks .

Does the Edit Action works on all the shared components?

Once updated I assume the others have to manually update one by one. Is there an option to automatically update all instances of the same action across your workflows?

Does the Edit Action works on all the shared components?
Edit Action should work for most of your workspace’s private components (the technical nuance is that it only supports components that are single-file, as opposed to those in our public registry that typically import other files from the repo).

Once updated I assume the others have to manually update one by one. Is there an option to automatically update all instances of the same action across your workflows?
That’s right, you’ll need to update each instance to the latest version. Unfortunately we don’t support “update all” yet, but we know that’s been an ask from folks.