+3

User Enablement Demo

Published 2 years ago

Created by

tephlon
jason

Template description

This workflow was originally presented at the February 2022 n8n Meetup.

Enabling End-Users to Configure Workflows

Requirements

In order to use this workflow, you will need the following in place:

  • A configured Baserow account
    • A group in Baserow called User Empowerment Demo
    • A database in the User Empowerment Demo called Office Shopping List
    • Inside the Office Shopping List database, you will need two tables:
      • Shopping List:
        • Column 1 - Single line text column named Item
      • Shopper:
        • Column 1 - Single line text column named Name
        • Column 2 - Email column named Email
  • An email account for sending out alerts

Customization

To make this workflow work for you, please customize the following items:

  • All Baserow nodes will need to be updated with your own credentials, database, tables and fields
  • The Send Shopping List node will need to be configured with your email credentials and email addresses
  • The Create Shopper Form Set node will need to have the code in the HTML value modified to reflect your Production URL from the Submit Shopper node (See instructions below)
  • The Cron node will need to be modified to reflect the timing that you wish to use

Modifying the Webform

The webform is the piece that people normally want to customize but is often the most complex because it is raw HTML. Here are some quick tips for making changes to the form.

Webform Nodes

There are two nodes that control what you see in the form:

  • Create Shopper Form - displays the form and submits it to the correct webhook
  • Create Response Page - displays the results when the form is submitted

Editing the Webform

The easiest way that I have found to edit the webform is to:

  1. Open up the Set node (Create Shopper Form or Create Response Page) that contains the HTML you wish to edit.
  2. Copy the contents of the HTML value to your favourite HTML editor
  3. Make your changes
  4. Paste the updated HTML back into the Set node

Changing the Webhook URL the Webform Posts To

In order for the webform to work properly, do the following:

  1. Determine the Production URL for the Submit Shopper webhook node
  2. In the Create Shopper Form node, look for the following line in the HTML value:
    form action="https://tephlon.app.n8n.cloud/webhook/submit-shopper" method="POST"
  3. Replace https://tephlon.app.n8n.cloud/webhook/submit-shopper with your Production URL

Changing the Webform Image

The image that is in the webform is actually embedded in the HTML in each of the Create Shopper Form or Create Response Page Set nodes and can be modified from there using these steps:

  1. Open up the appropriate Set node
  2. In the HTML value, find the line that starts with background-image:. It will be followed by a long string that looks like random characters
  3. Using a tool like Image to Base64 Converter, upload your image and generate a new CSS background source
  4. Replace the original background-image: line (including all the "random" characters) with the new generated CSS background source

Share Template

More Building Blocks workflow templates

Webhook node
Respond to Webhook node

Creating an API endpoint

Task: Create a simple API endpoint using the Webhook and Respond to Webhook nodes Why: You can prototype or replace a backend process with a single workflow Main use cases: Replace backend logic with a workflow
jon-n8n
Jonathan
Customer Datastore (n8n training) node

Very quick quickstart

Want to learn the basics of n8n? Our comprehensive quick quickstart tutorial is here to guide you through the basics of n8n, step by step. Designed with beginners in mind, this tutorial provides a hands-on approach to learning n8n's basic functionalities.
deborah
Deborah
HTTP Request node
Item Lists node

Pulling data from services that n8n doesn’t have a pre-built integration for

You still can use the app in a workflow even if we don’t have a node for that or the existing operation for that. With the HTTP Request node, it is possible to call any API point and use the incoming data in your workflow Main use cases: Connect with apps and services that n8n doesn’t have integration with Web scraping How it works This workflow can be divided into three branches, each serving a distinct purpose: 1.Splitting into Items (HTTP Request - Get Mock Albums): The workflow initiates with a manual trigger (On clicking 'execute'). It performs an HTTP request to retrieve mock albums data from "https://jsonplaceholder.typicode.com/albums." The obtained data is split into items using the Item Lists node, facilitating easier management. 2.Data Scraping (HTTP Request - Get Wikipedia Page and HTML Extract): Another branch of the workflow involves fetching a random Wikipedia page using an HTTP request to "https://en.wikipedia.org/wiki/Special:Random." The HTML Extract node extracts the article title from the fetched Wikipedia page. 3.Handling Pagination (The final branch deals with handling pagination for a GitHub API request): It sends an HTTP request to "https://api.github.com/users/that-one-tom/starred," with parameters like the page number and items per page dynamically set by the Set node. The workflow uses conditions (If - Are we finished?) to check if there are more pages to retrieve and increments the page number accordingly (Set - Increment Page). This process repeats until all pages are fetched, allowing for comprehensive data retrieval.
jon-n8n
Jonathan
Merge node

Joining different datasets

Task: Merge two datasets into one based on matching rules Why: A powerful capability of n8n is to easily branch out the workflow in order to process different datasets. Even more powerful is the ability to join them back together with SQL-like joining logic. Main use cases: Appending data sets Keep only new items Keep only existing items
jon-n8n
Jonathan
GitHub node
HTTP Request node
Merge node
+11

Back Up Your n8n Workflows To Github

This workflow will backup your workflows to Github. It uses the public api to export all of the workflow data using the n8n node. It then loops over the data checks in Github to see if a file exists that uses the workflow name. Once checked it will then update the file on Github if it exists, Create a new file if it doesn't exist and if it's the same it will ignore the file. Config Options repo_owner - Github owner repo_name - Github repository name repo_path - Path within the Github repository >This workflow has been updated to use the n8n node and the code node so requires at least version 0.198.0 of n8n
jon-n8n
Jonathan
Webhook node
Item Lists node
Respond to Webhook node

Convert JSON to an Excel file

Send a simple JSON array via HTTP POST and get an Excel file. The default filename is Export.xlsx. By adding the (optional) request ?filename=xyz you can specify the filename. NOTE: do not forget to change the webhook path!
dickhoning
Dick

Implement complex processes faster with n8n

red icon yellow icon red icon yellow icon