How do i set up a template for internal use/ without having to share it?

I would like to create workflow templates without having to submit them to the community. I would like to be able to send these internally in my organization, provide the initial set up screen for people to set up their credentials without people diving into the workflow.

I basically just want this screen when sharing a workflow with someone:

Even more ideally, i would like people in my org to be able to select from an internal template repository

Information on your n8n setup

  • n8n version: cloud pro

Hey @Andres_Quesada hope all is good. Welcome to the community.

You can always share the JSON of the workflow, which anyone in your org could copy and paste on a canvas. If you wish to include the explanations you could either share them along the workflow JSON OR you could create sticky notes on the canvas with text.

It appears there is also a way to point to an internal templates host:

Another page on using internal templates:

Another page, which touches on how a workflow can be shared:

Thank you @jabbson!

Thank you for pointing out that you can host your own template library if you have self hosted n8n. That’s very helpful and makes me consider hosting my own instance instead of continuing with cloud as this feature does not appear to be available in cloud.

However, the main feature I’m looking for, even if I was to publish it internally, is for that screen I’m showing in the screen shot in my original post which shows just some easy to fill out fields to set up credentials required by the automation.

Is there a way to set up this easy setup screen within the workflow editor that is available to me currently? Or if I self host it, will I have access to some feature that will enable me to show that screen? Is that screen automatically generated?

You are welcome.

I never tried or worked with custom template libraries, so I can only hope/believe that if you implement the endpoints mentioned in the docs, this will give you the same or similar experience as having access to the default public library.

What would be invaluable, if you choose to go this route, is if you could document and share your experience doing this, explaining for what worked, what didn’t, which challenges you faced and how you overcame them.

1 Like

Yup I’m just hoping anyone with access to create templates, even if it’s just for the community, can share insight on what the interface is like when packaging a workflow to submit as a template and can share if they have to do additional setup to get that screen or if it’s automatically generated or if it’s something n8n does when publishing a template or whatever

this is how template is submitted for: Discover 5297 Automation Workflows from the n8n's Community

just json.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.