The last post on creating Multiuser workflows got some good traction and I got lots of DMs in regards to the same. The common one was how to share access to workflows without giving access to n8n workflows

Background

All workflows must start with a trigger. We had previously discussed the different trigger types used in n8n

Among these, the webhook is the most versatile trigger type for all automation types. The chat trigger comes in handy too when it comes to the agentic workflows

Workflow accessibility

The main component required of your workflow by the end users is the functionality, and accessibility. This will be handy when building workflows for teams that are less technical and they need to interact with it regularly. Having them log onto n8n to perform the different tasks can not scale, and will provide lots of security challenges

What you’ll need

• A data storage – Supabase is better for its ease of use and integration.
• An oath workflow to collect the Oath tokens, codes and APIs
• N8n
• Good prompting skills/coding / Drag and drop UIs

Setup

My approach has been creating a simple UI that users can use, and send this data via webhooks to the n8n workflow. Once this is processed, I format the response data in a nice format that is then displayed to the user. This makes the automations feel more of systems than just workflows, can be used by multiple users and they don’t have to mess up with my setup in n8n

The end goal for this setup is a UI that will receive the data, send this to n8n and return the end results to the users.

Creating the dashboard

Create a simple UI that can be accessible with HTML, css and JS. If you are using an AI specify that this code is running in n8n and if possible not to import any external modules

Example prompt

... This code will be run in n8n. My n8n is on (self or cloud) so do (not) import/require any external modules. This will be displayed as a beautiful modern HTML on {{webhook etc}}

This will include the fields to input your desired data eg the main input, leads, name, email etc

N8n setup

Set up a trigger node that will receive this data. T he webhook node provides the best trigger for this. You can use a GET or a POST request to extend the functionality within a single workflow

The webhook will get the data, process it and return the response via a respond to webhook node

Response setup

This is the hardest part of this whole process. Presenting the data to the user in an appealing method

If you are using an AI to generate the dashboards, Paste the response from the webhook and and ask AI to update your dashboard code to match the output. This makes it easy to format the dashboard to fit your own setup

Deployment

This app can run natively on n8n code node. It will be made of two steps the dashboard and the Actual workflows

The users will be calling the main dashboard via a publicly available webhook URL perform their actions and trigger the second workflow which then returns the results to the dashboard

Final thoughts

This setup guide can be used for tons of other workflows and setups that require a front end or interactivity from the users.

For chat based workflows, embedding the chat URL to a website can replace the webhook trigger on this

Attach a data storage with a log of what run, what and the other data sets for better handling