Retrieve a Monday.com row and all data in a single node

Published 9 months ago

Created by

Joey D’Anna

Template description

This workflow is a building block designed to be called from other workflows via an Execute workflow node. When called from another workflow, and given the JSON input of a "pulse" field with the ID to pull from monday, this workflow will return:

The items name and ID
All column data, indexable by the column name
All column data, indexable by the column's ID string
All board relation columns, with their data and column values
All subitems, with their data and column values

For example:

++Prerequisites++

A monday.com account and credential
A workflow that needs to get detailed data from a monday.com row
The pulse id of the monday.com row to retreive data from.

++Setup++

Import the workflow
Configure all monday nodes with your credentials and save the workflow
Copy the workflow ID from it's URL
In a different workflow, add an Edit Fields node, to output the field "pulse", with the monday item you want to retrieve.
Feed the Edit Fields node with your pulse into an Execute workflow node, and paste the workflow ID from above into it
- This "pulse" field will tell the workflow what pulse to retreive. This can be populated by an expression in your workflow
- There is an example of the Edit Fields and Execute Workflow nodes in the template

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.