Convert Notion page to WordPress (Gutenberg) HTML
This workflow fetches the complete content of a specific Notion page and converts all its blocks into a single HTML string compatible with the WordPress Gutenberg block editor.
It's designed to be used as a sub-workflow. You can call it from a parent workflow (e.g., "when a Notion page is updated") by passing it a notion_url. It returns a single item containing the complete, ready-to-use HTML for a WordPress post body.
Key Features
- Full Page Conversion: Fetches all blocks from a page, including nested blocks (like content inside columns or toggles).
- Rich Text Support: Correctly parses and converts rich text annotations, including bold, italic, <u>underline</u>, <s>strikethrough</s>, and links.
- Gutenberg-Compatible: Wraps content in the appropriate Gutenberg HTML comments (e.g.,
,, ``) so WordPress recognizes them as blocks. - Handles Complex Layouts: Includes specific logic to correctly rebuild Notion's column and column_list blocks into a responsive Gutenberg-friendly format.
- Supports Various Blocks: Converts paragraphs, all heading types (H1, H2, H3), bulleted and numbered lists, images, videos (YouTube/Vimeo), embeds, code blocks, and dividers.
How It Works
- Input: The workflow is triggered by an Execute Workflow node, which expects a
notion_urlin the input data. (A manual trigger with a sample URL is included for testing). - Fetch Data: It first gets the Notion page specified by the URL and then uses a second Notion node to fetch all child blocks recursively (
fetchNestedBlocks: true). - Process Rich Text: A Code node (
decode paragraphs) iterates over text-based blocks (paragraphs, lists) and uses a helper function to convert the Notionannotationsarray into standard HTML tags (e.g.,<strong>,<em>,<a>). - Convert Blocks: A second Code node (
decode blocks) uses a largeswitchstatement to map each Notion blocktypeto its corresponding Gutenberg HTML structure. - Rebuild Columns: A crucial Code node (
column&column_list) runs once on all blocks. It finds allcolumnblocks, then finds their children, and finally wraps them inside their parentcolumn_listblock. This is essential for correctly handling nested layouts. - Filter & Aggregate: The workflow filters out all nested blocks, keeping only the top-level ones (since the nested content is now inside its parent, like the column block). It then aggregates all the generated HTML snippets into a single array.
- Final Output: A final Set node joins the array of HTML blocks with newline characters, producing a single text string in a field named
wp. This string can be directly used in the "Content" field of a WordPress node in your parent workflow.
Setup
- Notion Credentials: You must configure your Notion credentials in the two Notion nodes:
Get a database pageGet many child blocks
- Trigger: To use this, call it from another workflow using an Execute Workflow node. Pass the URL of the Notion page you want to convert in the
notion_urlfield.
Convert Notion Page to WordPress Gutenberg HTML
This n8n workflow simplifies the process of converting content from a Notion page into WordPress Gutenberg-ready HTML. It's designed to be triggered manually or by another workflow, allowing for flexible integration into your content publishing pipeline.
What it does
This workflow performs the following steps:
- Triggers Manually or by Another Workflow: The workflow can be initiated either by clicking the "Execute workflow" button in n8n or by an
Execute Workflow Triggernode from another n8n workflow. - Retrieves Notion Page Content: It connects to Notion to fetch the content of a specified page.
- Transforms Content with Code: A
Codenode is used to process and transform the raw Notion content into a format suitable for conversion to HTML. - Edits Fields: An
Edit Fields (Set)node further refines the data, likely preparing it for the final HTML conversion. - Aggregates Data: An
Aggregatenode combines the processed data, which might be necessary before generating the final HTML. - Filters Output (Conditional): A
Filternode allows for conditional processing of the data. This could be used to ensure the content meets certain criteria before proceeding or to branch the workflow based on content characteristics. - Converts to HTML (Implicit): While not explicitly named "Convert to HTML", the combination of the
Code,Edit Fields, andAggregatenodes suggests that the content is being prepared for HTML output, likely in a subsequent, unincluded node, or the final output of this workflow is the HTML itself. - Outputs Processed Data: The workflow outputs the transformed data, ready for use in a WordPress Gutenberg editor.
Prerequisites/Requirements
- n8n Instance: A running instance of n8n.
- Notion Account: Access to a Notion workspace and an integration with API access configured.
- Notion API Key: For connecting n8n to your Notion account.
Setup/Usage
- Import the workflow: Import the provided JSON into your n8n instance.
- Configure Notion Credentials:
- Locate the "Notion" node.
- Add or select your Notion API credentials. If you don't have them, follow the n8n documentation to create a Notion integration and obtain an API key.
- Specify Notion Page:
- In the "Notion" node, configure the operation to retrieve the desired Notion page content. You will likely need to provide the Notion page ID.
- Review and Customize Code (Optional):
- Examine the "Code" node. This node contains the core logic for transforming Notion's block-based content into a more HTML-friendly structure. You may need to customize this JavaScript code based on the specific Notion block types you use and your desired HTML output.
- Configure Edit Fields (Optional):
- Adjust the "Edit Fields (Set)" node if you need to rename, add, or remove fields from the data being processed.
- Adjust Filter (Optional):
- If you wish to add conditional logic, configure the "Filter" node with your desired conditions.
- Execute the workflow:
- Click "Execute Workflow" in the n8n editor to run the workflow manually.
- Alternatively, integrate this workflow as a sub-workflow into another n8n workflow using the
Execute Workflow Triggernode.
The output of the workflow will be the processed data, which should contain the HTML content ready to be pasted into a WordPress Gutenberg editor or further processed by another node (e.g., a WordPress node to create a post).
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte