Does Pipedream Allow Exporting and Importing of Projects and Workflows Across Different Accounts?

Help
1

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

Hi all. I am evaluating Pipedream for a new use case in my company and I can’t find a definitive answer in the documentation, nor the UI. The ability to Export and Import Projects and Workflows across accounts. We want to build example projects/workflows for our customers and let them import these examples into their account own Pipedream account. This would allow our customers who need to implement full stack business logic (webhooks/api/custom code) quickly and don’t have the resources or talent to do it in a timely fashion using their existing teams. Think of this as an niche case of Developer Relations for enterprise and as such, these examples are never public and usually custom tailored per customer. I remember at some point you could export JSON of your workflows, but that feature is now removed. Thanks

2

Are the share links what you are looking for?

3

Shared links does not look private and if the link got outside the org, anyone could have access to it. Think Enterprise

4

Yeah that’s true, maybe what you remembered here is GitHub Sync?

I remember at some point you could export JSON of your workflows, but that feature is now removed.

5

What if we add a way to expire links on demand?

6

So if we and the customer had a plan that used Github Sync, we could share the repo and then they could use the repo to update their account?

7

expiring links is just good hygiene, who knows where my private link goes over time. however its best in the enterprise use case to see the file. share the file. version the file.

8

so Github sounds better

9

I was asking about GitHub Sync because I don’t remember there was a JSON export feature in the past, let me first check if it is possible to create a repo from one account and then “move” access to another account because I don’t think so currently

10

thanks

11

just to be clear, I am not married to a JSON output of the workflow. any format is fine, it just needs to be portable so i can share it in a secure way with our customers. keep it updated in a version controlled way such as github so we know who created it, when it was given to the customer and someone can support it months or years down the road. Odds are once an enterprise customer deploys a project/workflow and its in “PRODUCTION”, it wont get touched for at least a year, maybe more,

12

Yep I gotcha, you want visibility and traceability on workflow versions

13

The flow for using GitHub sync to transfer a workflow from one workspace to another is limited currently, because we cannot instantiate a new project from an existing one

14

Unfortunately that will require some extensive product work

15

interesting, well workflows alone would work, just more manhours

16

To support linking a new project to an existing one

17

ok so i just want to be clear before looking for another alternative to Pipedream, you see no clear path for this use case at present

18

Correct

19

that sad, your product does what we want… functionally

20

What our partners usually do, is create a new workspace for a client, then develop the workflows there