HumationHuman + Automation
Back to Catalog

Generate multiple LinkedIn posts from Notion with ChatGPT & Claude AI

Niclas AuninNiclas Aunin
83 views
2/3/2026
Lead ManagementWebhookHubSpotSalesforceCRM
Official Page

LinkedIn Content Generation Workflow

Summary

Automated workflow that transforms Notion content notes into publication-ready LinkedIn posts using Claude AI. Monitors Notion database and generates multiple variations based on structured outlines, so that the author can pick the one they like most.

Use Cases

  • Automate LinkedIn content creation from content planning database.
  • Generate multiple post variations from a single outline.
  • Maintain consistent voice and formatting across all posts.
  • Scale content production while preserving quality.

How It Works

  1. Trigger - Monitors Notion "Content Plan" database hourly for updates.
  2. Conditional Check - Verifies "LinkedIn Post (Main)" tag and "Ready for Writing" status
  3. Main Post - Claude generates single post from project name and notes
  4. Outline Analysis - Parallel process creates 3 distinct post concepts with different angles
  5. Multi-Post Generation - Each outline becomes a complete LinkedIn post
  6. Save to Notion - All posts automatically saved to database

AI Setup:

  • Claude Sonnet 4.5 (claude-sonnet-4-5-20250929)
  • Main post: temperature 0.8 (creative)
  • Multi-post: default temperature (consistent)

How to Use

  1. Setup a content database in notion, or link your existing one:

    • Use field mapping as outlined below or update field mapping in n8n template.

  2. Add content to Notion:

    • Project name (topic)
    • Notes (article content/key points)
    • Tag: "LinkedIn Post (Main)"
    • Status: "Ready for Writing"

  3. Workflow triggers automatically (hourly check)

  4. Retrieve posts from Notion database

  5. Review and publish to LinkedIn

Requirements

Credentials:

  • Notion API (access to Content Plan database)
  • Anthropic API key
  • OpenAI API Key

Notion Database:

  • Connect Database
  • Required properties:
    • Project name (text)
    • Notes (rich text)
    • Tags (multi-select with "LinkedIn Post (Main)")
    • Status (select with "Ready for Writing")

Notes:

  • Posts optimized for 1800 character limit
  • Generates both single posts and multi-angle variations

n8n Workflow: Generate Multiple LinkedIn Posts from Notion with AI

This n8n workflow automates the process of generating multiple LinkedIn posts from content stored in Notion, leveraging the power of AI models like ChatGPT (OpenAI) or Claude AI (Anthropic). It allows you to manage your content ideas in Notion and automatically generate ready-to-publish LinkedIn posts based on specific criteria.

What it does

This workflow streamlines your content creation and social media publishing by:

  1. Monitoring Notion Database: It continuously watches a specified Notion database for new or updated items.
  2. Filtering Content: It checks if the Notion item has a "Generate Post" property set to true. This acts as a trigger to indicate which items should be processed for post generation.
  3. Generating LinkedIn Posts with AI:
    • If the "Generate Post" property is true, it sends the Notion content to either an OpenAI (ChatGPT) or Anthropic (Claude AI) chat model.
    • The AI agent is configured to create engaging LinkedIn posts based on the provided Notion content.
  4. Splitting Multiple Posts: If the AI generates multiple post suggestions within a single output, the workflow splits them into individual items for further processing.
  5. Updating Notion: After generating the posts, it updates the original Notion item, marking the "Generate Post" property as false to prevent reprocessing and potentially adding the generated posts back into Notion (though this specific action is not explicitly shown in the provided JSON, it's a common next step for such a workflow).

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance (self-hosted or cloud).
  • Notion Account: A Notion workspace with a database configured for your content ideas.
    • You'll need a Notion integration token and the database ID.
    • Ensure your Notion database has a property (e.g., a checkbox or select property) named "Generate Post" that the workflow can monitor.
  • OpenAI API Key (Optional): If you choose to use ChatGPT for content generation.
  • Anthropic API Key (Optional): If you choose to use Claude AI for content generation.
  • LinkedIn Account (Optional): While the workflow generates the posts, it doesn't explicitly post them to LinkedIn in this version. You would typically add a LinkedIn node after the AI generation to publish the content.

Setup/Usage

  1. Import the Workflow:
    • Download the workflow JSON.
    • In your n8n instance, click "Workflows" in the left sidebar, then "New", and select "Import from JSON". Paste the workflow JSON.
  2. Configure Credentials:
    • Notion Trigger Node (ID: 488): Configure your Notion API credentials. You'll need to provide your Notion integration token and select the database you want to monitor.
    • AI Agent Node (ID: 1119):
      • This node uses either the "Anthropic Chat Model" or "OpenAI" node as its language model.
      • Anthropic Chat Model (ID: 1145): If using Claude AI, configure your Anthropic API Key.
      • OpenAI Node (ID: 1250): If using ChatGPT, configure your OpenAI API Key.
      • Ensure the AI agent is configured with a prompt that guides it to generate LinkedIn posts from your Notion content.
  3. Activate the Workflow: Once all credentials and node settings are configured, activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.

The workflow will now run automatically based on the Notion Trigger's schedule (e.g., every 5 minutes) or when manually executed, generating LinkedIn posts for any Notion items marked for generation.

Related Templates

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

Daniel NkenchoBy Daniel Nkencho
601

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

Wessel BulteBy Wessel Bulte
247

🎓 How to transform unstructured email data into structured format with AI agent

This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From – sender’s email address To – recipient’s email address Subject – email subject line Summary – short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits ✅ Full Automation: Eliminates manual reading and data entry from incoming emails. ✅ Multi-Source Integration: Handles data from different email providers seamlessly. ✅ AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. ✅ Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. ✅ Time Efficiency: Processes emails in real time, improving productivity and response speed. *✅ Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.

DavideBy Davide
1616