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.
Tags
NotionSlack
WebflowRelated workflows
See all Notion→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.
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.
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