Workflow Templates

This workflow creates an automatic self-hosted URL shortener. It consists of three sub-workflows: Short URL creation for extracting the provided long URL, generating an ID, and saving the record in the database. It returns a short link as a result. Redirection for extracting the ID value, validating the existence of its correspondent record in the database, and returning a redirection page after updating the visits (click) count. Dashboard for calculating simple statistics about the saved record and displaying them on a dashboard. Read more about this use case and how to set up the workflow in the blog post How to build a low-code, self-hosted URL shortener in 3 steps. Prerequisites A local proxy set up that redirects the n8n.ly domain to your n8n instance An Airtable account and credentials Basic knowledge of JavaScript, HTML, and CSS Nodes Webhook nodes trigger the sub-workflows on calls to a specified link. IF nodes route the workflows based on specified query parameters. Set nodes set the required values returned by the previous nodes (id, longUrl, and shortUrl). Airtable nodes retrieve records (values) from or append records to the database. Function node calculates statistics on link clicks to be displayed on the dashboard, as well as its design. Crypto node generates a SHA256 hash.

Template Detail This template automates the process of converting a list of addresses into their latitude and longitude (LatLong) coordinates using Google Sheets and the Google Maps API. It's designed for businesses, developers, and analysts who need accurate geolocation data for use cases like delivery routing, event planning, or market analysis. What the Template Does Fetch Address Data: Retrieves addresses from a Google Sheet. Google Maps API Integration: Sends each address to the Google Maps API and retrieves the corresponding LatLong coordinates. Update Google Sheets: Automatically updates the same Google Sheet with the LatLong data for each address. Enhancements Google Sheets Template: Provide a pre-configured Google Sheets template that users can copy. Example link: Google Sheets Template. Columns required: Address: Column to input addresses. LatLong: Column for the latitude and longitude results. Updated Workflow Structure Trigger: A manual trigger node starts the workflow. Retrieve Data from Google Sheets: Fetch addresses from a Google Sheet. Send to Google Maps API: For each address, retrieve the LatLong coordinates directly via the Google Maps API. Update Google Sheets: Write the LatLong results back into the Google Sheet. Steps to Use Prepare Google Sheet: Copy the provided Google Sheets template and add your addresses to the Address column. Configure Google Cloud API: Enable the Maps API for your Google Cloud project. Generate an API key with the required permissions. Run the Workflow: Start the workflow in n8n; it will process the addresses automatically. Updated LatLong data will appear in the corresponding Google Sheet. Review the Results: Use the enriched LatLong data for mapping or analysis.

This workflow posts a poem translated into English every day in a Telegram chat. Cron node: triggers the workflow every day at 10:00. You can change the time and interval based on your use case. HTTP Request node: makes an HTTP request to the Poemist API that returns a random poem. LingvaNex node: translates the returned poems into English. Telegram node: takes in the translated poem and posts it in the chat.

This workflow automatically promotes your new Shopify products on Twitter and Telegram. This workflow is also featured in the blog post 6 e-commerce workflows to power up your Shopify store. Prerequisites A Shopify account and credentials A Twitter account and credentials A Telegram account and credentials for the channel you want to send messages to. Nodes Shopify Trigger node triggers the workflow when you create a new product in Shopify. Twitter node posts a tweet with the text "Hey there, my design is now on a new product! Visit my {shop name} to get this cool {product title} (and check out more {product type})". Telegram node posts a message with the same text as above in a Telegram channel.

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. Monetize Your n8n Workflow with x402 This workflow lets you monetize any n8n workflow with the x402 payment protocol. It uses 1Shot API as the onchain transaction fascilitator role. Check out the tutorial video for a complete walkthrough.

This workflow enriches the information of a new contact that gets added to HubSpot. HubSpot Trigger: This node triggers the workflow when a new contact gets added to HubSpot. Get Contact: This node fetches the information of the new contact. Clearbit: This node returns the data of the person and the company associated with the email address. Update Contact: This node will update the contact with the information returned by the Clearbit node. Based on your use case, you can select which fields you want to update.

This workflow extracts text from images sent in a Telegram chat and uploads the images to AWS S3. Telegram Trigger node** triggers the workflow when an image is sent in a Telegram channel. AWS S3 node** uploads the sent image to an S3 bucket. AWS Textract node** extracts text from the image. Airtable node** adds the extracted text and image information to a table.

This workflow synchronizes data one-way from Pipedrive to HubSpot. Cron node** schedules the workflow to run every minute. Pipedrive* and *Hubspot1 nodes pull in both lists of persons from Pipedrive and contacts from HubSpot. Merge node* with the option *Remove Key Matches identifies the items that uniquely exist in Pipedrive. Hubspot2 node** takes those unique items and adds them to HubSpot.

This workflow handles the incoming call from Twitter and sends the required response for verification. On registering the webhook with the Twitter Account Activity API, Twitter expects a signature in response. Twitter also randomly ping the webhook to ensure it is active and secure. Webhook node: Use the displayed URL to register with the Account Activity API. Crypto node: In the Secret field, enter your API Key Secret from Twitter. Set node: This node generates the response expected by the Twitter API. Learn more about connecting n8n with Twitter in the Getting Started with Twitter Webhook article.

Airtable Hierarchical Record Fetcher Description This n8n workflow retrieves an Airtable record along with its related child records in a hierarchical structure. It can fetch up to 3 levels of linked records and assembles them into a comprehensive JSON object, making it ideal for complex data relationships and nested record structures. Features Multi-level Record Fetching**: Retrieves parent record, linked child records (level 2), and optionally grandchild records (level 3) API Call Optimization**: Uses Airtable's filterByFormula to minimize API calls by fetching multiple related records in single requests Selective Level 3 Fetching**: Only fetches level 3 records for specified linked fields to optimize performance Rich Text Processing**: Converts Airtable's pseudo-markdown rich text fields to HTML format Hierarchical JSON Output**: Organizes all data in a structured, nested JSON format Flexible Configuration**: Customizable depth and field selection per execution Input Parameters The workflow accepts a JSON array with the following structure: [ { "base_id": "appN8nPMGoLNuzUbY", "table_id": "tblLVOwpYIe0fGQ52", "record_id": "reczMh1Pp5l94HdYf", "level_3": [ "fldRaFra1rLta66cD", "fld3FxCaYk8AVaEHt" ], "to_html": true } ] Parameter Details | Parameter | Type | Required | Description | |-----------|------|----------|-------------| | base_id | string | Yes | Airtable base identifier | | table_id | string | Yes | Airtable table identifier for the main record | | record_id | string | Yes | Airtable record identifier to fetch | | level_3 | array | No | Array of field IDs from level 2 records for which to fetch level 3 children | | to_html | boolean | No | Convert rich text fields from pseudo-markdown to HTML (default: false). This requires marked npm package. | Output Structure The workflow returns a hierarchical JSON object with the following structure: { "id": "recXXXXXXX", "field_1": ..., "field_2": ..., "level2_child": [ { "id": "recXXXXXXX", "field_a": ..., "field_b": ..., "level3_child": [ { "id": "recXXXXXXX", "field_y": ..., "field_z": ..., }, ... ] }, ... ] } `

This workflow contains community nodes that are only compatible with the self-hosted version of n8n. This template helps you discover trending Instagram Reels from competitors or any public profiles you choose. 📺 How It Works The workflow automatically monitors selected Instagram accounts using Apify, pulls recent Reels, and analyzes their performance. It calculates engagement levels, detects early “hot” content, translates text if needed, and organizes all results into a structured Notion database — ready for review and production. I've recorded a video walkthrough to show you how the system works in detail. 👉 https://www.youtube.com/watch?v=rdfRNHpHX8o @youtube 📄 Download Notion Database Structure You can download the Notion table structure (with all required columns and formats) here: 👉 https://drive.google.com/file/d/1FVaS_-ztp6PDAJbETUb1dkg8IqE4qHqp/view?usp=sharing 👤 Who’s it for This workflow is for marketers, content creators, social media managers, and automation enthusiasts who want to stay ahead of Instagram Reels trends. Whether you're building a content pipeline or studying competitors, this tool saves hours of manual tracking. 🔧 How to set up Create the required databases in Notion (structure file provided). Import the .json workflow into your n8n instance. Set up credentials for Notion, Apify, and Gemini API. Link those credentials in the workflow. Adjust the Variables node with your test account list and settings. Run a test with 3–5 profiles and validate the output. Once working, update Variables with your full config. 📋 Requirements An n8n instance (self-hosted or cloud) A Notion account (separate workspace recommended) Apify account (usage-based pricing for Instagram scraping) Gemini API key for AI processing (usage-based pricing) 🧩 How to customize the workflow The system is fully modular. You can: In the Set Prompt node, you can define your own rules for detecting content categories and video types. Change video filters (e.g., what counts as “hot” or “early hot”) Modify Notion fields or adapt to your own database structure Add more parsing logic to Variables Switch translation language Integrate with your content production flow Each part of the workflow is clearly labeled and editable — feel free to adapt it to your goals.

Using the Systeme API can be challenging due to its pagination settings and low rate limit. This requires a bit more knowledge about API requests than a beginner might have. This template provides preconfigured HTTP Request nodes to help you work more efficiently. Pagination settings, item limits, and rate limits are all configured for you, making it easier to get started. How to configure Systeme.io credentials The Systeme API uses the Header Auth method. So create a Header Auth credential in your n8n with the name "X-API-Key". . Check out my other templates 👉 https://n8n.io/creators/solomon/