7-day Pinterest content planner with Notion integration and email delivery
ποΈ 7-Day Pinterest Content Planner
Plan a full week of scroll-stopping pins in under two minutes! π
π§© What you get
π 7 ready-to-post pins (title, description, keywords, UTM-tagged link)
ποΈ Notion Ideas DB integration (optional) or use the built-in sample list
π Smart rotation of boards & keywords so no two pins feel the same
π One clean email with everything you needβjust copy & paste into your scheduler
π Built-in error alerts so you never miss a post
π How it flows
Manual Trigger β Set User Config β
(Notion enabled?) Pull Ideas / Else use sample list β
Build 7-Day Plan β Build Email β Send Email β
(On failure) Error Trigger β Email Owner
π οΈ Prerequisites
- Email credentials (SMTP or Gmail)
- (Optional) Notion database
Ideaswith:- Title (title)
- URL (url)
- Board (select)
- Keywords (rich text)
βοΈ Quick setup
Update these in Set: User Config
FROM_EMAIL, EMAIL_TO_SELF, ENABLE_NOTION, NOTION_DB_ID, BRAND_SITE_URL, UTM_SOURCE, UTM_MEDIUM, UTM_CAMPAIGN, BOARD_NAMES, KEYWORDS
β° Schedule
Default: Every Monday 08:00 (Asia/Ho_Chi_Minh)
Tweak the cron whenever you like.
β Test in 60 seconds
- Fill in
BRAND_SITE_URL+ UTM fields β hit Manual Trigger - (Optional) Enable Notion, add DB ID β run again
- Flip on the weekly cron β relax!
π Compliance
β
Stickies
β
Manual path
β
No secrets in JSON
β
Timezone-aware Cron
7-Day Pinterest Content Planner with Notion Integration and Email Delivery
This n8n workflow automates the creation and delivery of a 7-day Pinterest content planner, leveraging Notion for content management and email for delivery. It's designed to help content creators and marketers streamline their Pinterest strategy by providing a structured plan directly to their inbox.
What it does
This workflow simplifies your Pinterest content planning with the following steps:
- Manual Trigger / Scheduled Execution: The workflow can be triggered manually for immediate use or scheduled to run periodically (e.g., weekly) using the Cron node.
- Notion Database Interaction (Placeholder): While the JSON indicates a Notion node, its configuration is not detailed. In a complete setup, this node would likely fetch content ideas, pin descriptions, or scheduling information from a Notion database.
- Data Transformation (Placeholder): A Function node and an Edit Fields (Set) node are present, suggesting data manipulation. This would typically involve formatting the data retrieved from Notion into a digestible structure for the email.
- Conditional Logic (Placeholder): An If node is included, implying that certain conditions might be checked before proceeding (e.g., checking if enough content is available, or if specific criteria are met).
- Email Delivery: Compiles the processed content into an email and sends it to a specified recipient, delivering the 7-day Pinterest content planner.
- Error Handling: An "Error Trigger" node is present, indicating that a separate error workflow can be configured to catch and handle any failures in the main workflow execution, ensuring you're alerted to issues.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running instance of n8n.
- Notion Account: With a database configured to store your Pinterest content ideas (requires Notion API integration).
- Email Service: An SMTP server or an email service provider configured as a credential in n8n to send emails.
Setup/Usage
- Import the Workflow: Import the provided JSON into your n8n instance.
- Configure Credentials:
- Notion: Set up your Notion API credentials to connect to your Notion workspace and the specific database containing your Pinterest content.
- Email: Configure your email credentials (SMTP or other email service) for the "Send Email" node.
- Customize Notion Node: Adjust the "Notion" node (ID 487) to specify which database to query and what data to retrieve for your Pinterest planner.
- Customize Function and Set Nodes: Modify the "Function" (ID 14) and "Edit Fields" (ID 38) nodes to transform the Notion data into the desired format for your email content.
- Configure If Node: Adjust the "If" node (ID 20) with any conditional logic necessary for your planning process.
- Customize Email Content: Edit the "Send Email" node (ID 11) to define the subject, body, and recipient(s) of the email. You will likely use expressions to dynamically insert the content planner data processed in previous steps.
- Set Schedule (Optional): If you want the planner delivered periodically, configure the "Cron" node (ID 7) to your desired schedule (e.g., once a week). Otherwise, use the "Manual Trigger" (ID 838) for on-demand execution.
- Activate the Workflow: Once configured, activate the workflow to start automating your Pinterest content planning.
Related Templates
Two-way property repair management system with Google Sheets & Drive
This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required β one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- βοΈ How It Works Workflow 1 β New Repair Requests Behind the Scenes: A tenant fills out a Google Form (βRepair Request Formβ), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded β runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 β Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (βRepair Update Formβ). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row β enabling a full repair history in one place. --- π§© Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- β‘ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- π οΈ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.
Automate RSS to social media pipeline with AI, Airtable & GetLate for multiple platforms
Overview Automates your complete social media content pipeline: sources articles from Wallabag RSS, generates platform-specific posts with AI, creates contextual images, and publishes via GetLate API. Built with 63 nodes across two workflows to handle LinkedIn, Instagram, and Blueskyβwith easy expansion to more platforms. Ideal for: Content marketers, solo creators, agencies, and community managers maintaining a consistent multi-platform presence with minimal manual effort. How It Works Two-Workflow Architecture: Content Aggregation Workflow Monitors Wallabag RSS feeds for tagged articles (to-share-linkedin, to-share-instagram, etc.) Extracts and converts content from HTML to Markdown Stores structured data in Airtable with platform assignment AI Generation & Publishing Workflow Scheduled trigger queries Airtable for unpublished content Routes to platform-specific sub-workflows (LinkedIn, Instagram, Bluesky) LLM generates optimized post text and image prompts based on custom brand parameters Optionally generates AI images and hosts them on Imgbb CDN Publishes via GetLate API (immediate or draft mode) Updates Airtable with publication status and metadata Key Features: Tag-based content routing using Wallabag's native system Swappable AI providers (Groq, OpenAI, Anthropic) Platform-specific optimization (tone, length, hashtags, CTAs) Modular designβduplicate sub-workflows to add new platforms in \~30 minutes Centralized Airtable tracking with 17 data points per post Set Up Steps Setup time: \~45-60 minutes for initial configuration Create accounts and get API keys (\~15 min) Wallabag (with RSS feeds enabled) GetLate (social media publishing) Airtable (create base with provided schemaβsee sticky notes) LLM provider (Groq, OpenAI, or Anthropic) Image service (Hugging Face, Fal.ai, or Stability AI) Imgbb (image hosting) Configure n8n credentials (\~10 min) Add all API keys in n8n's credential manager Detailed credential setup instructions in workflow sticky notes Set up Airtable database (\~10 min) Create "RSS Feed - Content Store" base Add 19 required fields (schema provided in workflow sticky notes) Get Airtable base ID and API key Customize brand prompts (\~15 min) Edit "Set Custom SMCG Prompt" node for each platform Define brand voice, tone, goals, audience, and image preferences Platform-specific examples provided in sticky notes Configure platform settings (\~10 min) Set GetLate account IDs for each platform Enable/disable image generation per platform Choose immediate publish vs. draft mode Adjust schedule trigger frequency Test and deploy Tag test articles in Wallabag Monitor the first few executions in draft mode Activate workflows when satisfied with the output Important: This is a proof-of-concept template. Test thoroughly with draft mode before production use. Detailed setup instructions, troubleshooting tips, and customization guidance are in the workflow's sticky notes. Technical Details 63 nodes: 9 Airtable operations, 8 HTTP requests, 7 code nodes, 3 LangChain LLM chains, 3 RSS triggers, 3 GetLate publishers Supports: Multiple LLM providers, multiple image generation services, unlimited platforms via modular architecture Tracking: 17 metadata fields per post, including publish status, applied parameters, character counts, hashtags, image URLs Prerequisites n8n instance (self-hosted or cloud) Accounts: Wallabag, GetLate, Airtable, LLM provider, image generation service, Imgbb Basic understanding of n8n workflows and credential configuration Time to customize prompts for your brand voice Detailed documentation, Airtable schema, prompt examples, and troubleshooting guides are in the workflow's sticky notes. Category Tags social-media-automation, ai-content-generation, rss-to-social, multi-platform-posting, getlate-api, airtable-database, langchain, workflow-automation, content-marketing
Dynamic Hubspot lead routing with GPT-4 and Airtable sales team distribution
AI Agent for Dynamic Lead Distribution (HubSpot + Airtable) π§ AI-Powered Lead Routing and Sales Team Distribution This intelligent n8n workflow automates end-to-end lead qualification and allocation by integrating HubSpot, Airtable, OpenAI, Gmail, and Slack. The system ensures that every new lead is instantly analyzed, scored, and routed to the best-fit sales representative β all powered by AI logic, sir. --- π‘ Key Advantages β‘ Real-Time Lead Routing Automatically assigns new leads from HubSpot to the most relevant sales rep based on region, capacity, and expertise. π§ AI Qualification Engine An OpenAI-powered Agent evaluates the leadβs industry, region, and needs to generate a persona summary and routing rationale. π Centralized Tracking in Airtable Every lead is logged and updated in Airtable with AI insights, rep details, and allocation status for full transparency. π¬ Instant Notifications Slack and Gmail integrations alert the assigned rep immediately with full lead details and AI-generated notes. π Seamless CRM Sync Updates the original HubSpot record with lead persona, routing info, and timeline notes for audit-ready history, sir. --- βοΈ How It Works HubSpot Trigger β Captures a new lead as soon as itβs created in HubSpot. Fetch Contact Data β Retrieves all relevant fields like name, company, and industry. Clean & Format Data β A Code node standardizes and structures the data for consistency. Airtable Record Creation β Logs the lead data into the βLeadsβ table for centralized tracking. AI Agent Qualification β The AI analyzes the lead using the TeamDatabase (Airtable) to find the ideal rep. Record Update β Updates the same Airtable record with the assigned team and AI persona summary. Slack Notification β Sends a real-time message tagging the rep with lead info. Gmail Notification β Sends a personalized handoff email with context and follow-up actions. HubSpot Sync β Updates the original contact in HubSpot with the assignment details and AI rationale, sir. --- π οΈ Setup Steps Trigger Node: HubSpot β Detect new leads. HubSpot Node: Retrieve complete lead details. Code Node: Clean and normalize data. Airtable Node: Log lead info in the βLeadsβ table. AI Agent Node: Process lead and match with sales team. Slack Node: Notify the designated representative. Gmail Node: Email the rep with details. HubSpot Node: Update CRM with AI summary and allocation status, sir. --- π Credentials Required HubSpot OAuth2 API β To fetch and update leads. Airtable Personal Access Token β To store and update lead data. OpenAI API β To power the AI qualification and matching logic. Slack OAuth2 β For sending team notifications. Gmail OAuth2 β For automatic email alerts to assigned reps, sir. --- π€ Ideal For Sales Operations and RevOps teams managing multiple regions B2B SaaS and enterprise teams handling large lead volumes Marketing teams requiring AI-driven, bias-free lead assignment Organizations optimizing CRM efficiency with automation, sir --- π¬ Bonus Tip You can easily extend this workflow by adding lead scoring logic, language translation for follow-ups, or Salesforce integration. The entire system is modular β perfect for scaling across global sales teams, sir.