Archive Empty Pages in Notion Database Daily
Overview
This workflow automatically cleans up your Notion workspace by archiving pages that are completely empty — pages with no text content in any block and no filled property values. It runs daily at 2 AM, so you can keep your databases tidy without manual effort. The workflow is especially useful for removing unwanted placeholder pages, blank templates, or accidentally created empty entries.
Workflow Steps
Here is every node in the workflow, its type, authentication method, and configured parameters:
-
Every day @ 2am (Cron Trigger) — No auth
- Runs the workflow once per day at 2:00 AM.
- No configuration needed beyond the trigger time.
-
Get All Databases (Notion) — Notion API (API Key or OAuth2)
- Resource: database
- Operation: getAll
- Return All: true
- Fetches a list of all databases the Notion integration can access.
-
Get All Database Pages (Notion) — Notion API (API Key or OAuth2)
- Resource: databasePage
- Operation: getAll
- Return All: true
- Database ID: taken from
{{$json["id"]}}(the database ID from the previous node) - Retrieves every page in each database, including its properties.
-
Check for empty properties (Function Node) — No auth
- Function Code: Iterates over each page’s properties. If any property has data (non‑empty array), it sets
toDelete = false. If all properties are empty, it setstoDelete = true. - This is a custom JavaScript function that marks pages with no filled properties for potential deletion.
- Function Code: Iterates over each page’s properties. If any property has data (non‑empty array), it sets
-
If Empty Properties (IF Node) — No auth
- Condition:
{{$json["toDelete"]}}equalstrue - Routes only pages that have no filled properties to the next step for block‑level checking.
- Condition:
-
SplitInBatches (Split In Batches Node) — No auth
- Batch Size: 1
- Processes one page at a time, ensuring each page’s blocks are inspected independently.
-
Get Page Blocks (Notion) — Notion API (API Key or OAuth2)
- Resource: block
- Operation: getAll
- Return All: true
- Block ID: taken from
{{$json["id"]}}(the page ID) - Retrieves all content blocks (text, headings, lists, etc.) inside the page.
-
Process Blocks (Function Node) — No auth
- Function Code: For each block, it checks if the block’s text array is empty. If all blocks have empty text, it marks the page for deletion. If any block has non‑empty text, it stops and marks the page as not to delete.
- Returns an object with
toDelete(boolean) andpageID(the page’s ID).
-
If toDelete (IF Node) — No auth
- Condition:
{{$json["toDelete"]}}equalstrue - Only pages that are confirmed empty (both properties and blocks) continue to archiving.
- Condition:
-
Archive Page (Notion) — Notion API (API Key or OAuth2)
- Resource: page
- Operation: archive
- Page ID: taken from
{{$json["pageID"]}} - Moves the empty page to the trash/archive, removing it from active views.
Setup Instructions
To use this workflow, you need:
- A Notion account with access to the databases you want to clean.
- A Notion Integration (API token). Go to https://www.notion.so/my-integrations, create a new integration, and copy the “Internal Integration Secret” (API key).
- In Notion, share each database with your integration (click “Share” in the database top‑right, add the integration by name).
- In n8n, add a Notion credential (type: Notion API) and paste your integration token.
- Enable the workflow and it will run daily at 2 AM. You can adjust the cron trigger to any schedule you prefer.
Use Cases & Variations
- Weekly cleanup — Change the cron trigger to run weekly instead of daily (e.g., every Monday at 9 AM).
- Specific databases only — Modify the “Get All Databases” node to filter by a specific database ID if you only want to clean one database.
- Archive versus delete — The workflow archives (soft delete). To permanently delete, change the Notion operation to “delete” (but be careful — this cannot be undone).
- Exclude certain properties — Edit the “Check for empty properties” function to ignore specific property types (e.g., “created_time” or “last_edited_time”).
- Send a notification — Add a Slack or email node after archiving to report how many pages were cleaned each run.
- Only check top‑level blocks — The current code checks all blocks recursively. If you want only the first block, adjust the loop.
Workflow JSON
{
"id": 115,
"name": "Archive empty pages in Notion Database",
"nodes": [
{
"name": "Get All Databases",
"type": "n8n-nodes-base.notion",
"position": [
240,
300
],
"parameters": {
"resource": "database",
"operation": "getAll",
"returnAll": true
},
"credentials": {
"notionApi": {
"id": "36",
"name": "Notion account"
}
},
"typeVersion": 2
},
{
"name": "Get All Database Pages",
"type": "n8n-nodes-base.notion",
"position": [
420,
300
],
"parameters": {
"simple": false,
"options": {},
"resource": "databasePage",
"operation": "getAll",
"returnAll": true,
"databaseId": "={{$json[\"id\"]}}"
},
"credentials": {
"notionApi": {
"id": "36",
"name": "Notion account"
}
},
"typeVersion": 2
},
{
"name": "Get Page Blocks",
"type": "n8n-nodes-base.notion",
// ... truncated (copy to see full JSON)How to Import This Workflow
- 1Copy the workflow JSON above using the Copy Workflow JSON button.
- 2Open your n8n instance and go to Workflows.
- 3Click Import from JSON and paste the copied workflow.
Don't have an n8n instance? Start your free trial at n8nautomation.cloud
Related Templates
YouTube Video Summarizer with Telegram Notification
High-Level Summary This workflow automatically processes YouTube videos by fetching their transcripts, generating a structured AI-powered summary using OpenAI's GPT-4o-mini, and sending the summary along with video metadata to a Telegram chat. It is triggered via a webhook, making it easy to integrate with other tools or services (e.g., a browser extension, a form, or another automation). The workflow is ideal for content curators, researchers, or teams who want to quickly digest video content without watching the full video. Workflow Steps Webhook — Receives an incoming HTTP POST request containing a YouTube URL in the request body. This is the entry point of the workflow. (No auth) Get YouTube URL (Set node) — Extracts the field from the incoming webhook payload and stores it as a string variable for downstream use. (No auth) YouTube Video ID (Code node) — Runs a JavaScript function that parses the YouTube URL using a regex pattern to extract the 11-character video ID (supports both and formats). (No auth) Get YouTube Video (YouTube node) — Uses the extracted video ID to fetch video metadata (title, description, etc.) from the YouTube Data API v3. (OAuth2 — requires a Google Cloud project with YouTube Data API enabled) YouTube Transcript (Community node: ) — Fetches the transcript/captions for the video. This node requires the video ID (passed from the previous step). (No auth — uses public YouTube captions) Split Out (SplitOut node) — Splits the transcript array into individual items so each text segment can be processed separately. (No auth) Concatenate (Summarize node) — Concatenates all transcript text segments into a single string, separated by spaces, to prepare the full transcript for analysis. (No auth) gpt-4o-mini (OpenAI Chat Model node) — Configures the OpenAI language model (GPT-4o-mini) that will be used for summarization. (API Key auth — requires an OpenAI API key) Summarize & Analyze Transcript (LLM Chain node) — Sends the concatenated transcript to the GPT-4o-mini model with a detailed prompt asking for a structured summary with headers, bullet points, bold terms, and tables. The output is a markdown-formatted analysis. (No auth — uses the model configured in the previous node) Response Object (Set node) — Assembles the final output object containing: - : The AI-generated summary text - : An empty array (placeholder for future use) - : The video title from YouTube metadata - : The video description from YouTube metadata - : The YouTube video ID - : The original YouTube URL from the webhook (No auth) Respond to Webhook — Sends the assembled response object back to the original webhook caller (e.g., a browser extension or app). (No auth) Telegram — Sends a message to a specified Telegram chat containing the video title and the YouTube URL. (API Key auth — requires a Telegram Bot Token and chat ID) Setup Instructions To use this workflow, you will need the following accounts and credentials: OpenAI Account: Create an account at platform.openai.com and generate an API key. Add this as a credential in n8n under "OpenAI". Google Cloud Project: Enable the YouTube Data API v3 in your Google Cloud Console, create OAuth 2.0 credentials (Desktop app type), and add them in n8n under "YouTube OAuth2 API". Telegram Bot: Create a bot via @BotFather on Telegram to get a Bot Token. Find your chat ID (e.g., by messaging your bot and visiting ). Add the token as a credential in n8n under "Telegram API". Webhook URL: After activating the workflow, copy the production webhook URL (e.g., ). You will send POST requests to this URL with a JSON body like . Use Cases and Variations Content Curation: Automatically summarize long conference talks, tutorials, or webinars and share them with your team on Telegram. Research Assistant: Collect video transcripts and AI summaries for later reference or database storage. Browser Extension Integration: Pair this workflow with a browser extension that sends the current YouTube URL to the webhook when clicked. Variations: - Replace Telegram with Slack, Discord, or email notifications. - Store summaries in a Google Sheet or Airtable for a searchable archive. - Add a filter to skip videos shorter than a certain duration. - Use a different LLM (e.g., Claude, Gemini) by swapping the OpenAI node. - Add error handling to notify you if a video has no captions.
Telegram Bot TikTok Video Downloader (No Watermark)
Overview This workflow transforms your Telegram bot into a powerful TikTok video downloader without watermarks. When a user sends a TikTok link to the bot, it automatically validates the URL, fetches the video page, extracts the clean video URL, downloads the file, and sends it back to the user with statistics (views, likes, author). The entire process is handled seamlessly with real-time status updates and robust error handling. This is perfect for content curators, social media managers, or anyone who wants to save TikTok videos without watermarks directly from Telegram. The bot provides a smooth user experience with progress messages and clear error feedback. Workflow Steps Telegram Trigger (No auth) — Listens for incoming messages from Telegram users. Configured to receive only updates. This node requires a Telegram Bot Token set up in n8n credentials. Validate TikTok URL (No auth) — An IF node that checks if the received message contains in the text. Uses string contains operator with loose type validation. Routes valid URLs to the processing path and invalid ones to an error message. Send Invalid URL Message (Telegram API Key auth) — Sends a friendly error message to the user explaining they need to provide a valid TikTok link with examples. Uses the chat ID from the original trigger message. Send Chat Action (Telegram API Key auth) — Sends a "uploading video" chat action to show the user that the bot is processing their request. This provides visual feedback in the Telegram chat. Send Processing Message (Telegram API Key auth) — Sends a status message "⏳ Downloading video... Please wait!" to keep the user informed about the progress. Configure Variables (No auth) — A Set node that stores the video URL (trimmed) and chat ID as named variables for use in subsequent nodes. This ensures data persistence through the workflow. Get TikTok Page HTML (No auth) — An HTTP Request node that fetches the TikTok video page HTML. Uses browser-like headers (User-Agent, Accept, Accept-Language) to mimic a real browser request. Configured with a 30-second timeout and full response capture. On error, it continues to the error handling path. Extract Video URL (No auth) — A Code node running JavaScript that parses the HTML to find the script tag containing video metadata. Extracts the video URL (playAddr or downloadAddr), cookies, description, author, and statistics (plays, likes, comments). On error, it routes to the error handler. Download Video File (No auth) — An HTTP Request node that downloads the actual video file using the extracted URL. Includes cookies from the previous step, proper referrer header, and a 60-second timeout. Configured to return binary file data. On error, it routes to the error handler. Delete Process Notif (Telegram API Key auth) — Deletes the "Processing..." status message to clean up the chat after the video is ready. Uses the message ID from the earlier status message. Send Video to User (Telegram API Key auth) — Sends the downloaded video file to the user with a formatted caption showing the author, view count, and like count. Uses binary data mode for file upload. Format Error (No auth) — A Code node that captures error messages from failed nodes and formats them into a user-friendly error object with the chat ID for response. Send Error Message (Telegram API Key auth) — Sends a detailed error message to the user explaining possible reasons for failure (deleted video, invalid link, maintenance, restrictions) with HTML formatting. Setup Instructions Prerequisites Telegram Bot Token: Create a bot via @BotFather on Telegram and get your API token n8n Instance: Self-hosted or cloud n8n (n8n.io) Configuration Steps Telegram Credentials: In n8n, go to Credentials → New → Telegram API. Enter your bot token from BotFather Webhook Setup: The Telegram Trigger node automatically sets up a webhook URL. Make sure your n8n instance is publicly accessible or use a tunnel (ngrok) Test the Bot: Send any TikTok video link to your bot (e.g., ) Use Cases & Variations Primary Use Case Personal Video Archiving: Save your favorite TikTok videos without watermarks for offline viewing Content Curation: Collect videos for repurposing on other platforms Social Media Management: Download client videos for scheduling tools Possible Adaptations Add Multiple Platforms: Extend the workflow to support Instagram Reels, YouTube Shorts, or Twitter videos by adding additional validation and extraction logic Database Storage: Add a Google Sheets or Airtable node to log downloaded videos with metadata Admin Notifications: Add a second Telegram channel to notify you when someone downloads a video Rate Limiting: Implement user rate limiting using n8n's Wait node or a database Video Processing: Add FFmpeg or other processing nodes to convert formats or add watermarks Multi-language Support: Modify error messages and captions based on user language preferences
Daily Berlin Weather SMS Alert via Plivo
Daily Berlin Weather SMS Alert This workflow automatically sends an SMS message every morning at 9 AM with the current temperature in Berlin. It combines a scheduled trigger, a weather data API, and an SMS service to deliver a simple, useful notification straight to your phone. How It Works Cron (No auth) — Runs the workflow every day at 9:00 AM. The parameter is set to hour 9, with no specific minute (defaults to 0), so it fires once daily. OpenWeatherMap (API Key auth) — Fetches current weather data for the city of Berlin. The parameter is set to "berlin". An API key is required (stored as a credential). The node returns JSON data including the main temperature in Celsius. Plivo (Auth ID + Auth Token) — Sends an SMS using the Plivo SMS API. The parameter is an expression: It dynamically inserts the temperature value from the previous node. The recipient phone number is configured in the Plivo credential (or can be set in the node parameters if adjusted). Setup Instructions OpenWeatherMap: Create a free account at openweathermap.org and generate an API key. In n8n, add a new credential of type "OpenWeatherMap API" and paste your API key. Plivo: Sign up at plivo.com and obtain your Auth ID and Auth Token (found in the Plivo console). Also ensure you have a Plivo phone number that can send SMS. In n8n, add a credential of type "Plivo API" with these details. Cron: No setup required – just ensure the workflow is active. After configuring the credentials, the workflow will run automatically at 9 AM each day. You can change the city by editing the parameter in the OpenWeatherMap node, or modify the message text in the Plivo node. Use Cases & Variations Different city: Replace "berlin" with any other city name (e.g., "London", "Paris"). Multiple recipients: Duplicate the Plivo node or use a separate node per phone number. Weather conditions: Extend the message to include humidity, weather description (e.g., "Clear sky") by adding more expressions. Other triggers: Replace the Cron trigger with a webhook or manual trigger for on-demand checks. Alternative services: Swap OpenWeatherMap for another weather API, or use Twilio instead of Plivo for SMS. This template is an excellent starting point for learning how to combine scheduled triggers, API calls, and messaging services in n8n.