Monday.com Useful Utilities
Published 10 months ago
Created by
Joey D’Anna
Categories
Template description
This template is a set of building blocks to access Monday.com in ways not supported by the official Monday node.
Prerequisites
- Monday account and Monday credentials.
Included are setups to:
- Find a column value by the column's name (instead of a numerical index which can change when board structure is changed)
- Find a column value by the column's ID (again, instead of using a numerical index)
- Pull a board relation column, and get all the related pulses
- Pull an items subitems and split them out
- Upload a file to an item's files field
Setup
- Create a Monday.com credential
- Update the nodes in the template to use your credential
- Copy/Paste the nodes you need from this template into any other workflow
- To retreive a column by name:
- Route a Monday.com node that gets an item to the COLUMN BY NAME node
- Edit the COLUMN BY NAME node, and enter the name in the first line of code.
- To retreive a column by its ID:
- Follow Monday.com's instructions to locate the column's ID
- Route a Monday.com node that gets an item to the COLUMN BY ID node
-Edit the COLUMN BY ID node, and enter the ID in the first line of code.
- To retreive all linked pulses from a Board Relation column:
- Route a Monday.com node that gets an item to the GET BOARD RELATION node
- Edit the GET BOARD RELATION node to specify the column name.
- All linked pulses will be retrieved by the subsequent PULL LINKEDPULSE node
- To pull all subitems from an item:
- Route a Monday.com node that gets an item to the PULL SUBITEMS node
- All subitems will be retrieved by the subsequent GET EACH SUBITEM node
- To upload a File:
- Repalce the Convert to File node with whatever node you are using to output your binary file data
- Enable the MONDAY UPLOAD node
- If the destination column is named anything other then the default of "file" - edit the MONDAY UPLOAD node and change column_id:"file" in the first Value field to match the name of your file column
Share Template
More Building Blocks workflow templates
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
Jonathan
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
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.
Jonathan
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
Jonathan
+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
Jonathan
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!
Dick
