Notion
35 sonuç — tümü kaynağa bağlı n8n referansı
Answer Notion knowledge base questions with You.com Research
Quick overview This workflow monitors a Notion questions database and, for items marked “To Research,” uses You.com Research to generate a cited answer, then writes the answer and sources back to the same Notion page and updates the status to “Answered”. How it works Triggers when a new page is added to a specified Notion database (polled every minute). Checks that the page has a non-empty Question field and that Status equals “To Research”. Sends the question text to You.com using the Research operation to generate an answer with sources. Updates the same Notion page with the generated Answer and Sources fields and sets Status to “Answered”. If the You.com request fails, writes an error message into the Answer field and leaves the item in “To Research” so it can be retried. Setup Use self-hosted n8n and install the community node package @youdotcom-oss/n8n-nodes-youdotcom. Add Notion API credentials and a You.com API credential, then select them in the corresponding nodes. Replace the Notion database ID in the trigger and ensure the database has properties named Question, Status (select), Answer (text/rich text), and Sources (text/rich text) with Status options “To Research” and “
Extract business card contacts from LINE with Google Gemini and Notion
Quick overview This workflow receives image messages from LINE, downloads the photo, uses Google Gemini to detect and extract business card details, and then saves the contact to a Notion CRM database before replying to the sender in LINE. How it works Receives a POST request from the LINE Messaging API webhook when a user sends a message. Extracts the message type, image message ID, reply token, and LINE user ID from the webhook payload. If the message is an image, downloads the image content from the LINE data API and converts it to Base64. Sends the image to Google Gemini (Generative Language API) to determine whether it is a business card and to extract name, company, position, phone, and email as JSON. Parses Gemini’s JSON response and branches based on whether the image is flagged as a business card. If it is a business card, creates a new page in a Notion CRM database with the extracted fields and pushes a confirmation message to the user in LINE. If it is not a business card, pushes a LINE message asking the user to resend a clearer business card photo. Setup Create a LINE Messaging API channel, enable webhooks, and add the n8n webhook URL from the LINE webhook trigger as y
Post a daily project health standup to Slack with Notion and Groq
Quick overview This workflow runs every morning, reads yesterday’s standup and today’s active projects from Notion, uses Groq (OpenAI-compatible chat completions) to generate a red/yellow/green project health standup, posts it to Slack, and saves the new standup back to Notion for tomorrow. How it works Runs every day at 7:30 AM on a schedule. Reads the previous standup digest from a Notion “memory” database row and fetches all “Active” projects from a Notion projects database. Builds a prompt that includes yesterday’s digest plus today’s project notes, last update dates, and next milestone dates. If there are no active projects, posts an “All quiet” message to a Slack channel. If there are active projects, sends the prompt to Groq’s chat completions endpoint to score projects as Red/Yellow/Green and list changes since yesterday. Posts the generated standup text to Slack and updates the Notion memory row with today’s digest and timestamp. Setup Add a Notion credential and set the database IDs for your Projects database and the single-row Memory database used to store the daily digest. Create a Groq API header-auth credential (Authorization: Bearer ) for the Groq chat completions re
Transcribe and summarize Notion meeting recordings with Gladia
Quick overview This workflow triggers on new meeting entries in a Notion database, sends the recording URL to Gladia for transcription with diarization and summarization, polls until the job completes, and then writes the summary and full transcript back to the same Notion page. How it works Triggers when a new page is added to the selected Notion meetings database. Reads the page’s “Recording URL” and starts an asynchronous transcription job in Gladia with speaker diarization and summarization enabled. Waits for a configured interval and repeatedly checks Gladia for the transcription result until it returns done or the maximum poll attempts is reached. When processing completes, updates the Notion page Status to “Transcribed” and writes the returned summary to the “Summary” property. Splits the full transcript into Notion-safe text chunks and appends them to the meeting page as blocks. If Gladia returns an error or the polling times out, updates the Notion page Status to “Failed” and writes a failure message to the “Summary” property. Setup Use a self-hosted n8n instance and install the n8n-nodes-gladia community node (Settings → Community Nodes). Add credentials for the Notion AP
Route workflow error incidents to Slack alerts with a Notion incident log
Quick overview This workflow captures n8n workflow execution errors, classifies and deduplicates them, logs incidents to a Notion database, and routes high-severity alerts to a Slack channel, with an optional daily Slack digest of open incidents. How it works Triggers when an n8n workflow execution fails via the built-in Error Trigger. Normalizes the error payload and extracts key metadata like workflow, execution, node, and stack details. Classifies the error into a category, severity, and suggested fix using rule-based text matching. Builds an incident fingerprint and formatted Slack message, then searches a Notion database for an existing incident with the same fingerprint. If a matching Notion incident exists, it updates the page’s last-seen timestamp, severity, suggested fix, and occurrence count and optionally posts a repeated Slack alert based on the minimum severity threshold. If no incident exists, it creates a new Notion incident page and posts a Slack alert only when the severity meets or exceeds the configured threshold. Runs daily on a schedule, fetches unresolved incidents from Notion, and posts a summary digest to the same Slack channel when any open incidents exist.
Roll overdue Notion tasks forward and flag stale ones on a schedule
Quick overview This workflow runs every morning, scans a Notion tasks database for overdue, unfinished items, rolls their due dates forward, increments a roll counter, and marks tasks as stale once they have been rolled too many times. How it works Runs every morning at 7:00 based on a schedule. Retrieves all pages from the selected Notion database. Filters for tasks with a due date before today and a status that is not in the configured “done” list. Sets each overdue task’s due date to today (or the next business day), increments its Rolled counter, and marks it Stale when the roll count exceeds the threshold. Updates the matching Notion pages with the new due date, Rolled number, and Stale checkbox values. Setup Add your Notion API credentials and share the target Notion database with the Notion integration. Select your tasks database in the Notion “Get Open Tasks” step. Ensure your database has matching properties (Due date, Status select/status, Rolled number, and Stale checkbox) and update the property names, DONE_VALUES, STALE_THRESHOLD, and ROLL_TO settings in the code to match your schema. Requirements A Notion internal integration credential, with the tasks database shared
Deduplicate and archive Notion database rows daily with an audit log
Quick overview This workflow runs daily and deduplicates a Notion database by grouping pages on a chosen property, keeping one “best” page per group (newest by default) and archiving the rest, then appending an audit recap line to a Notion log page. How it works Runs every day at 2am on a schedule. Fetches all pages from the selected Notion database, including full property data. Groups pages by a configurable Notion property (for example, “Name”) and identifies groups with more than one page. Chooses one page to keep per duplicate group based on the configured rule (newest, oldest, or mostFilled) and prepares the other pages for archiving. Archives each duplicate page in Notion by updating the page to archived: true. Appends a one-line recap (scanned count, duplicates found, and how many were archived) to a specified Notion page as an audit log. Setup Add your Notion API credentials and share both the target database and the audit log page with the Notion integration. Select the Notion database to deduplicate in the database ID field of the database query step. Update MATCH_PROPERTY and KEEP_RULE in the code step to match your database and your preferred keeper strategy. Paste the
Normalize and backfill Notion database properties with rules and logging
Quick overview This workflow runs daily to normalize and backfill properties in a Notion database, standardizing Status values, deriving a Key slug and Created week stamp, updating only changed pages, and appending a run recap to a Notion log page. How it works Runs every day at 3am on a schedule. Fetches all pages (rows) from a selected Notion database with full property data. Applies normalization rules to backfill missing Status values, canonicalize known Status variants, and optionally derive a Key slug from the title and a Created week value from the page creation time. Updates only the Notion pages where one or more of these derived values differs, and stamps a Last normalized date on each updated page. Appends a one-line recap of the run (scanned vs. updated counts and what changed) to a specified Notion page or block. Setup Add a Notion API credential and share both the target database and the log page with your Notion integration. Select the Notion database to process in the database ID field used to fetch all database pages. Update the rules in the code configuration (property names, DEFAULT_STATUS, and the CANONICAL_STATUS mapping) to match your database. Ensure the targ
Schedule approved Notion content calendar posts with Posta
Quick Overview This workflow runs every 15 minutes to fetch approved items from a Notion content calendar, creates and schedules matching posts in Posta for the specified time, and then updates the Notion database row with the Posta post URL and a Scheduled status. How it works Runs every 15 minutes on a schedule trigger. Retrieves all pages from a specified Notion database. Processes each returned Notion row one by one, using the Caption, Scheduled At, Social Account IDs, and optional Media IDs fields. Creates a post in Posta for the selected social accounts and attaches any referenced media IDs. Schedules the Posta post for the Notion row’s Scheduled At timestamp (converted to UTC). Updates the original Notion page by setting Status to Scheduled and writing back the Posta post URL. Setup Create a Notion integration, share your content calendar database with it, and connect the Notion credentials in n8n. Add your Posta API token as Posta credentials in n8n. Set the Notion database ID/URL in the Notion database read step to point to your content calendar. Ensure your Notion database includes the required properties (Caption, Status, Scheduled At, Social Account IDs, optional Media
🧹 Archive (delete) duplicate items from a Notion database
🧑💼 Who is this for? If you’re using Notion to manage a database (like saving links, tasks, notes, or anything really), and it’s starting to get messy with duplicate entries, this workflow is for you. It’s especially useful if you want to keep things tidy without doing any manual cleanup. 🧠 What problem is this workflow solving? Notion doesn’t have a built-in way to find or remove duplicates, so you either clean them up manually 😩 or just let them pile up. This workflow automatically finds entries that share the same property (like a URL or title) and archives the extra copies, keeping just one. ⚙️ What this workflow does Pulls all pages from a Notion database. Identifies duplicates based on a property you choose. Archives the duplicate pages (which is like soft-deleting them). Keeps one version of each duplicate group. It includes two optional triggers: Run it every day ⏰ Or trigger it automatically when a new page is added to the database ⚡ 🛠️ Setup Connect your Notion account in n8n. Select your database in the Notion nodes. In the “Format items properly” node, replace "SET YOUR PROPERTY HERE" with a reference to the property you want to use for detecting duplicates. I reco
CallForge - 08 - AI Product Insights from Sales Calls with Notion
CallForge - AI-Powered Product Insights Processor from Sales Calls Automate product feedback extraction from AI-analyzed sales calls and store structured insights in Notion for data-driven product decisions. 🎯 Who is This For? This workflow is designed for: ✅ Product managers tracking customer feedback and feature requests. ✅ Engineering teams identifying usability issues and AI/ML-related mentions. ✅ Customer success teams monitoring product pain points from real sales conversations. It streamlines product intelligence gathering, ensuring customer insights are structured, categorized, and easily accessible in Notion for better decision-making. 🔍 What Problem Does This Workflow Solve? Product teams often struggle to capture, categorize, and act on valuable feedback from sales calls. With CallForge, you can: ✔ Automatically extract and categorize product feedback from AI-analyzed sales calls. ✔ Track AI/ML-related mentions to gauge customer demand for AI-driven features. ✔ Identify feature requests and pain points for product development prioritization. ✔ Store structured feedback in Notion, reducing manual tracking and increasing visibility across teams. This workflow eliminates
CallForge - 07 - AI Marketing Data Processing with Gong & Notion
CallForge - AI-Powered Marketing Insights Extraction from Sales Calls Automate marketing intelligence gathering from AI-analyzed sales calls and store insights in Notion. 🎯 Who is This For? This workflow is designed for: ✅ Marketing teams looking to extract trends and insights from sales conversations. ✅ Product managers who need direct customer feedback from sales calls. ✅ Revenue operations (RevOps) teams optimizing AI-driven call analysis. It streamlines AI-powered marketing intelligence, identifying customer pain points, competitor mentions, and recurring trends—all automatically stored in Notion. 🔍 What Problem Does This Workflow Solve? Manually reviewing sales call transcripts for marketing insights is time-consuming and inconsistent. With CallForge, you can: ✔ Extract key marketing insights from AI-analyzed sales calls. ✔ Track recurring discussion topics across multiple conversations. ✔ Generate actionable marketing recommendations for strategy and content. ✔ Store structured insights in Notion for seamless access. This automation eliminates manual work and ensures marketing teams get data-driven insights from real customer conversations. 📌 Key Features & Workflow Steps
CallForge - 06 - Automate Sales Insights with Gong.io, Notion & AI
CallForge - AI-Powered Sales Call Data Processor Automate sales call analysis and store structured insights in Notion with AI-powered intelligence. Who is This For? This workflow is ideal for: ✅ Sales teams looking to automate call insight processing. ✅ Sales operations managers managing AI-driven call analysis. ✅ Revenue teams using Gong, Fireflies.ai, Otter.ai, or similar transcription tools. It streamlines sales call intelligence, ensuring that insights such as competitor mentions, objections, and customer pain points are efficiently categorized and stored in Notion for easy access. 🔍 What Problem Does This Workflow Solve? Manually reviewing and documenting sales call takeaways is time-consuming and error-prone. With CallForge, you can: ✔ Identify competitors mentioned in sales calls. ✔ Capture objections and customer pain points for follow-up. ✔ Track sales call outcomes and categorize insights automatically. ✔ Store structured sales intelligence in Notion for future reference. ✔ Improve sales strategy with AI-driven, automated call analysis. 📌 Key Features & Workflow Steps 🎙️ AI-Powered Call Data Processing This workflow processes AI-generated sales call insights and struct
CallForge - 04 - AI Workflow for Gong.io Sales Calls
CallForge - AI Gong Sales Call Processing Workflow Automate your Gong.io sales call analysis with AI-driven insights, real-time tracking, and structured CRM integration. Who is This For? This workflow is designed for: ✅ Sales teams looking to automate sales call processing. ✅ Revenue operations (RevOps) professionals managing high volumes of call data. ✅ AI-driven sales intelligence teams using Gong.io for data-driven insights. What Problem Does This Workflow Solve? Manually managing and analyzing large volumes of Gong call data is time-consuming and error-prone. With CallForge, you can: ✔ Automate call processing to scale AI-driven insights. ✔ Integrate with Notion to track and organize sales call data efficiently. ✔ Get real-time Slack updates to stay informed on call processing progress. ✔ Handle API failures gracefully, allowing easy reruns if a rate limit is hit. ✔ Ensure AI-ready analysis, feeding structured call data into an AI-powered system. What This Workflow Does 1. Triggers on New Gong Calls Captures new Gong calls and retrieves metadata, call summaries, and participant details. 2. Compares Calls Against Notion Database Checks whether the call has already been processed
Convert Notion to Markdown and Back to Notion
This workflow converts Notion pages to markdown, and then converts that markdown back to Notion blocks. It will triple the content of the last updated page it finds. This is useless by itself, but you can copy-paste from this workflow to create your own. Prerequisites A notion account with some pages or databases Setup instructions Create a notion credential and share some pages as described here: https://docs.n8n.io/integrations/builtin/credentials/notion/ How it works The HTTP Request gets notion child blocks from a page, because the default n8n block only gets plain text and no links. The first code block converts it to markdown. The second code block converts it back to Notion blocks The last HTTP block appends everything to the original Notion page, essentially duplicating it for the purpose of demoing the script. I hope in the future we get official n8n blocks that extract markdown, or use markdown to write to Notion. There is community block that also does this, but this template is easier: you can simply copy-paste the blocks from this workflow.
Automatically Import your Meta Threads Posts into Notion
Who is this for? This template is designed for social media managers, content creators, data analysts, and anyone who wants to automatically save and analyze their Meta Threads posts in Notion. It’s particularly useful for: Building a personal archive of your Threads content. Training AI models using your social media data. Tracking your online presence and engagement. What this workflow does This workflow uses the Meta Threads API to automatically retrieve your posts and import them into a Notion database. It retrieves the post content, date, and time, and stores them in designated properties within your Notion database. Setup Get Threads Access Token and ID: Obtain a long-lived access token and your Threads ID from the Meta Threads developer platform. This token auto-refreshes, ensuring uninterrupted workflow operation. Configure Credentials and Date Range: In the “Set Credentials” node (using edit fields), enter your token and ID. Set the since and until parameters in the “Set Date Range” node to specify the post import period. Connect to Notion and Create a Database: Connect to your Notion workspace and create a database with these properties (customize with the “Create Propert
Automated Notion Task Reminders via Slack
This workflow is designed to automate task reminders by retrieving tasks from a Notion database and sending reminders to Slack users. It checks for incomplete tasks from a Notion database and sends a Slack message to the relevant users with the task details and due dates. The automation is scheduled to run every weekday at 9:00 AM, ensuring that users are always reminded of pending tasks. Who is this for? This workflow is ideal for teams or individuals who manage their tasks using Notion but rely on Slack for communication. It provides an automated solution for ensuring that tasks in Notion are followed up on, reducing the risk of missing deadlines. What problem is this workflow solving? Often, team members need to be reminded of tasks from various platforms. This workflow bridges the gap between task management in Notion and communication in Slack by automatically sending task reminders. It ensures that team members are informed of their pending tasks each morning, helping them stay organized and on top of their work. What this workflow does Triggers every weekday at 9:00 AM: The workflow runs at 9:00 AM, Monday through Friday. Fetches tasks from Notion: It retrieves tasks from a
Time Tracking with Notion and iOS shortcut
Who might benfit from this workflow? Do you have to record your working hours yourself? Then this n8n workflow in combination with an iOS shortcut will definitely help you. Once set up, you can use a shortcut, which can be stored as an app icon on your home screen, to record the start, end and duration of your break. How it works Once setup you can tap the iOS shortcut on your iPhone. You will see a menu containing three options: "Track Start", "Track Break" and "Track End". After time is tracked iOS will display you a notification about the successful operation. How to set it up Copy the notion database to your notion workspace (Top right corner). Copy the n8n workflow to your n8n workspace In the notion nodes in the n8n workflow, add your notion credentials and select the copied notion database. Download the iOS Shortcut from our documentation page Edit the shortcut and paste the url of your n8n Webhook trigger node to the first "Text" node of the iOS shortcut flow. It is a best practice to use authentication. You can do so by adding "Header" auth to the webhook node and to the shrotcut. You need help implementing this or any other n8n workflow? Feel free to contact me via Linked
Sync blog posts from Notion to Webflow
Who is this for? This template is for everyone who manages their blog entries in Notion and want to have an easy way to transform them to Webflow. What this workflow does This workflow syncs your blog posts saved in a Notion Database once a day to Webflow. Sync Notion properties, rich text and cover image with your collection. Works with most elements: H1, H2, H3, normal text, bold text, italic text, links, quotes, bulleted lists, numbered lists, and images (under 4MB). Set up steps Connect your accounts. Add a "slug" field in Notion. Add a "Sync to Webflow?" checkbox in Notion. Run a test and map your collection data. Whenever the workflow runs, all the checked posts will be updated in the Webflow collection, whether it's a new post or an existing one.
Automatically document n8n workflows directly in Notion database
Use case n8n workflows can go out of hand when you're automating as much as we do at n8n. We needed a place to document them and keep track of who owns and maintains them. To facilitate this we use this n8n workflow to automatically sync workflows directly to a Notion database if it has the tag sync-to-notion. How to setup Add your n8n api creds Add your Notion creds Create notion database with fields env id as text, isActive (dev) as boolean, URL (dev) as url, Workflow created at as date, Workflow updated at as date, Error workflow setup as boolean (Make sure page is connected) Add tag sync-to-notion to some workflows
Add product ideas to Notion via a Slack command
Use Case In most companies, employees have a lot of great ideas. That was the same for us at n8n. We wanted to make it as easy as possible to allow everyone to add their ideas to some formatted database - it should be somewhere where everyone is all the time and could add a new idea without much extra effort. Since we're using Slack, this seemed to be the perfect place to easily add ideas and collect them in Notion. What this workflow does This workflow waits for a webhook call within Slack, that gets fired when users use the /idea command on a bot that you will create as part of this template. It then checks the command, adds the idea to Notion, and notifies the user about the newly added idea as you can see below: Creating your Slack bot Visit https://api.slack.com/apps, click on New App and choose a name and workspace. Click on OAuth & Permissions and scroll down to Scopes -> Bot token Scopes Add the chat:write scope Head over to Slash Commands and click on Create New Command Use /idea as the command Copy the test URL from the Webhook node into Request URL Add whatever feels best to the description and usage hint Go to Install app and click install Setup Add a Database in Not
Bookmarking urls in your browser and save them to Notion
Remember when you were doing some large research and wanted to quickly bookmark a page and save it, only to find premium options? Worry not; n8n got you covered. You can now create a simple bookmarking app straight to your browser using simple scrips on your browser called bookmarklets. A bookmarklet is a bookmark stored in a web browser that contains JavaScript commands that add new features to the browser. To create one, we need to add a short script to the bookmark tab of our browser like below A simple hack is to open a new tab and click on the star that appears on the right side Now that we have our bookmark, it's time for the fun part. Right-click on the bookmark we just created and select the edit option. This will allow you to set the name you want for your bookmark and the destination URL. The URL used here will be the script that shall "capture" the page we want to bookmark. The code below has been used and tested to work for this example javascript:(() => { var currentUrl = window.location.href; var webhookUrl = 'https://$yourN8nInstanceUrl/webhook/1rxsxc04b027-39d2-491a-a9c6-194289fe400c'; var xhr = new XMLHttpRequest(); xhr.open('POST', webhookUrl, true); xhr.setReq
Sync Outlook Calendar events to Notion
This workflow syncs Outlook Calendar events to a Notion database. The Outlook Calendar event must be within a specific time frame (default of within next year) for the workflow to pick up the event. The event subject will be the title of the Notion page, and the event link will be added to the Notion page as a property. Prerequisites Notion account and Notion credentials. Microsoft account and Microsoft credentials. How it works On scheduled intervals, find all Outlook Calendar events within a specific time frame. For each event, check if the event already exists in the Notion database. If it does not exist, create a new page in the Notion database, otherwise update the existing page. Setup This workflow requires that you set up a Notion database or use an existing one with at least the following fields: Title (title) Date (date) Event ID (text) Link (URL)
Report number of weekly created records in an app
This template shows how you can create reports on data in an app and share a summary in another app. Specifically, this example checks a Notion database for new submissions, filters for submissions with a specific tag, and then sends a Slack message with the number created this week. Setup instructions are located inside the workflow template.