Actioning your meeting next steps using transcripts and AI
This n8n workflow demonstrates how you can summarise and automate post-meeting actions from video transcripts fed into an AI Agent. Save time between meetings by allowing AI handle the chores of organising follow-up meetings and invites. How it works This workflow scans for the calendar for client or team meetings which were held online. Attempts will be made to fetch any recorded transcripts which are then sent to the AI agent. The AI agent summarises and identifies if any follow-on meetings are required. If found, the Agent will use its Calendar Tool to to create the event for the time, date and place for the next meeting as well as add known attendees. Requirements Google Calendar and the ability to fetch Meeting Transcripts (There is a special OAuth permission for this action!) OpenAI account for access to the LLM. Customising the workflow This example only books follow-on meetings but could be extended to generate reports or send emails.
By JimleukCreate custom PDF documents from templates with Gemini & Google Drive
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. 1 — What Does It Do / Which Problem Does It Solve? This workflow turns Google Docs-based contract & form templates into ready-to-sign PDFs in minutes—all from a single chat flow. Automates repetitive document creation. Instead of copying a rental, sales, or NDA template and filling it by hand every time, the bot asks for the required values and fills them in. Eliminates human error. It lists every mandatory field so nothing is missed, and removes unnecessary clauses via conditional blocks. Speeds up approvals. The final draft arrives as a direct PDF link—one click to send for signing. One template → unlimited variations. Every new template you drop in Drive is auto-listed with zero workflow edits—it scales effortlessly. 100 % no-code. Runs on n8n + Google Apps Script—no extra backend, self-hosted or cloud. --- 2 — How It Works (Detailed Flow) 📝 Template Discovery 📂 The TemplateList node scans the Drive folder you specify via the ?mode=meta endpoint and returns an id / title / desc list. The bot shows this list in chat. 🎯 Selection & Metadata Fetch The user types a template name. 🔍 GetMetaData opens the chosen Doc, extracts META_JSON, placeholders, and conditional blocks, then lists mandatory & optional fields. 🗣 Data-Collection Loop The bot asks for every placeholder value. For each conditional block it asks 🟢 Yes / 🔴 No. Answers are accumulated in a data JSON object. ✅ Final Confirmation The bot summarizes the inputs → when the user clicks Confirm, the DocProcess sub-workflow starts. ⚙️ DocProcess Sub-Workflow | 🔧 Step | Node | Task | | --- | --- | --- | | 1 | User Choice Match Check | Verifies name–ID match; throws if wrong | | 2 | GetMetaData (renew) | Gets the latest placeholder list | | 3 | Validate JSON Format | Checks for missing / unknown fields | | 4 | CopyTemplate | Copies the Doc via Drive API | | 5 | FillDocument | Apps Script fills placeholders & removes blocks | | 6 | Generate PDF Link | Builds an export?format=pdf URL | 📎 Delivery The master agent sends 🔗 Download PDF & ✏️ Open Google Doc links. 🚫 Error Paths status:"ERROR", missing:[…] → bot lists missing fields and re-asks. unknown:[…] → template list is outdated; rerun TemplateList. Any Apps Script error → the returned message is shown verbatim in chat. --- 3 — 🚀 Setup Steps (Full Checklist) > Goal: Get a flawless PDF on the first run. > > > Mentally tick the ☑️ in front of every line as you go. > ☁️ A. Google Drive Preparation | Step | Do This | Watch Out For | | --- | --- | --- | | 1 | Create a Templates/ folder → put every template Doc inside | Exactly one folder; no sub-folders | | 2 | Placeholders in every Doc are {{UPPER_CASE}} | No Turkish chars or spaces | | 3 | Wrap optional clauses with [[BLOCKNAME:START]]…[[BLOCKNAME:END]] | The START tag must have a blank line above | | 4 | Add a META_JSON block at the very end | Script deletes it automatically after fill | | 5 | Right-click Doc > Details ▸ Description = 1-line human description | Shown by the bot in the list | | 6 | Create a second Generated/ folder (for copies) | Keeps Drive tidy | > 🔑 Folder ID (long alphanumerical) = <TEMPLATEPARENTID> > > > We’ll paste this into the TemplateList node next. > Simple sample template → Template Link --- 🛠 B. Import the Workflow into n8n bash Settings ▸ Import Workflow ▸ DocAgent.json If nodes look Broken afterwards → no community-node problem; you only need to select credentials. --- 📑 C. Customize the TemplateList Node Open Template List node ⚙️ → replace '%3CYOURPARENTID%3E' in parents with the real folder ID in the URL. Right-click node > Execute Node. Copy the entire JSON response. In the editor paste it into: DocAgent → System Prompt (top) User Choice Match Check → System Prompt (top) Save. > ⚠️ Why manual? Caching the list saves LLM tokens. Whenever you add a template, rerun the node and update the prompts. > --- 🔗 D. Deploy the Apps Script | Step | Screen | Note | | --- | --- | --- | | 1 | Open Gist files GetMetaData.gs + FillDocument.gs → File ▸ Make a copy | Both files may live in one project | | 2 | Project Settings > enable Google Docs API ✔️ & Google Drive API ✔️ | Otherwise you’ll see 403 errors | | 3 | Deploy ▸ New deployment ▸ Web app | | | • Execute as | Me | | | • Who has access | Anyone | | | 4 | On the consent screen allow scopes:• …/auth/documents• …/auth/drive | Click Advanced › Go if Google warns | | 5 | Copy the Web App URL (e.g. https://script.google.com/macros/s/ABC123/exec) | If this URL changes, update n8n | Apps Script source code → Notion Link --- 🔧 E. Wire the Script URL in n8n | Node | Field | Action | | --- | --- | --- | | GetMetaData | URL | <WEBAPPURL>?mode=meta&id={{ $json["id"] }} | | FillDocument | URL | <WEBAPPURL> | > 💡 Prefer using an .env file? Add GASWEBAPPURL=… and reference it as {{ $env.GASWEBAPPURL }}. > --- 🔐 F. Add Credentials Google Drive OAuth2 → Drive API (v3) Full Access Google Docs OAuth2 → same account LLM key (OpenAI / Gemini) (Optional) Postgres Chat Memory credential for the corresponding node --- 🧪 G. First Run (Smoke Test) Switch the workflow Active. In the chat panel type /start. Bot lists templates → pick one. Fill mandatory fields, optionally toggle blocks → Confirm. 🔗 Download PDF link appears → ☑️ setup complete. --- ❌ H. Common Errors & Fixes | 🆘 Error | Likely Cause | Remedy | | --- | --- | --- | | 403: Apps Script permission denied | Web app access set to User | Redeploy as Anyone, re-authorize scopes | | placeholder validation failed | Missing required field | Provide the listed values → rerun DocProcess | | unknown placeholders: … | Template vs. agent mismatch | Check placeholder spelling (UPPER_CASE ASCII) | | Template ID not found | Prompt list is old | Rerun TemplateList → update both prompts | | Cannot find METAJSON | No meta block / wrong tag | Add [[METAJSONSTART]] … [[METAJSON_END]], retry | --- ✅ Final Checklist [ ] Drive folder structure & template rules ready [ ] Workflow imported, folder ID set in node [ ] TemplateList output pasted into both prompts [ ] Apps Script deployed, URL set in nodes [ ] OAuth credentials & LLM key configured [ ] /start test passes, PDF link received --- 🙋♂️ Need Help with Customizations? Reach out for consulting & support on LinkedIn: Özgür Karateke Full Documentation → Notion Simple sample template → Template Link Apps Script source code → Notion Link
By Ozgur Karateke🤖 Instagram MCP AI agent – read, reply & manage comments with GPT-4o
🤖 Instagram AI Agent with MCP Server – Built for Smart Engagement and Automation Hi! I’m Amanda 🥰 I build intelligent automations with n8n and Make. This powerful workflow was designed to help teams automatically handle Instagram interactions with AI. Using Meta Graph API, LangChain, MCP Server, and GPT-4o, it allows your AI agent to search for posts, read captions, fetch comments, and even reply or message followers, all through structured tools. --- 🔧 What the workflow does Searches for recent media using Instagram ID and access token Reads and extracts captions or media URLs Fetches comments and specific replies from each post Replies to comments automatically with GPT-generated responses Sends direct messages to followers who commented Maps user input and session to keep memory context via LangChain Communicates via Server-Sent Events (SSE) using your MCP Server URL --- 🧰 Nodes & Tech Used LangChain Agent + Chat Model with GPT-4o Memory Buffer for session memory toolHttpRequest to search media, comments, and send replies MCP Trigger and MCP Tool (custom SSE connection) Set node for input and variable assignment Webhook and JSON for Instagram API structure --- ⚙️ Setup Instructions Create your Instagram App in Meta Developer Portal Add your Instagram ID and Access Token in the Set node Update the MCP Server Tool URL in the MCP Instagram node Use your n8n server URL (e.g. https://yourdomain.com/mcp/server/instagram/sse) Trigger the workflow using the included LangChain Chat Trigger Interact via text to ask the agent to: “Get latest posts” “Reply to comment X with this message” “Send DM to this user about...” --- 👥 Who this is for Social media teams managing multiple comments Brands automating engagement with followers Agencies creating smart, autonomous digital assistants Developers building conversational Instagram bots --- ✅ Requirements Meta Graph API access Instagram Business account n8n instance (Cloud or Self-hosted) MCP Server configured (SSE Endpoint enabled) OpenAI API Key (for GPT-4o + LangChain) --- 🌐 Want to use this workflow? ❤️ Buy workflows: https://iloveflows.com ☁️ Try n8n Cloud: https://n8n.partnerlinks.io/amanda
By Amanda BenksCapture leads in HubSpot from Typeform
This workflow is triggered when a typeform is submitted, then it saves the sender's information into HubSpot as a new contact. Typeform Trigger: triggers the workflow when a typeform is submitted. Set: sets the fields for the values from Typeform. HubSpot 1: creates a new contact with information from Typeform. IF: filters contacts who expressed their interest in business services. HubSpot 2: updates the contact's stage to opportunity. Gmail: sends an email to the opportunity contacts with informational material. NoOp: takes no action for contacts who are not interested.
By LorenaAI-powered lead email classification & auto-reply with GPT-4o and Gmail
How it works This workflow automatically responds to incoming emails identified as potential leads using AI-generated text. It connects to your email inbox via IMAP, classifies incoming messages with an AI model, filters out non-leads, and sends a personalized reply to relevant messages. Steps Email Trigger (IMAP): Watches your inbox for new emails in real time. Is Lead? (Message Model): Uses AI to determine whether the sender is a lead. Filter: Passes only lead emails to the next step. Write Customized Reply (Message Model): Generates a personalized response using AI. Get Message: Retrieves original email details to ensure correct threading. Reply to Message: Sends the AI-generated reply to the sender. Setup Instructions Connect your IMAP Email credentials to the first node and set the folder to watch (e.g., INBOX). In the "Filter leads" node, adjust the AI prompt to match your lead qualification criteria. In the "Reply with customized message" node, edit the AI prompt to reflect your product, service, or business tone. Connect your Gmail (or other email provider) credentials in the Get Message and Reply to Message nodes. Test with a few sample emails before activating. Requirements IMAP-enabled email account (for receiving messages) Gmail API access (or modify to your email provider) OpenAI or other AI model credentials for message analysis and reply generation This template is ready to use, with all steps documented inside sticky notes for easy customization.
By RodrigoAutomate Instagram comment responses with Google Sheets & CRM tracking
This workflow contains community nodes that are only compatible with the self-hosted version of n8n. 🎯 Overview This n8n workflow template automates the process of monitoring Instagram comments and sending predefined responses based on specific comment keywords. It integrates Instagram's Graph API with Google Sheets to manage comment responses and maintains an interaction log for customer relationship management (CRM) purposes. 🔧 Workflow Components The workflow consists of 9 main nodes organized into two primary sections: 📡 Section 1: Webhook Verification ✅ Get Verification (Webhook node) 🔄 Respond to Verification Message (Respond to Webhook node) 🤖 Section 2: Auto Comment Response 📬 Insta Update (Webhook node) ❓ Check if update is of comment? (Switch node) 👤 Comment if of other user (If node) 📊 Comment List (Google Sheets node) 💬 Send Message for Comment (HTTP Request node) 📝 Add Interaction in Sheet (CRM) (Google Sheets node) 🛠️ Prerequisites and Setup Requirements 🔵 Meta/Facebook Developer Setup 📱 Create Facebook App > 📋 Action Items: > - [ ] Navigate to Facebook Developers > - [ ] Click "Create App" and select "Business" type > - [ ] Configure the following products: > - ✅ Instagram Graph API > - ✅ Facebook Login for Business > - ✅ Webhooks 🔐 Required Permissions Configure the following permissions in your Meta app: | instagram_basic | 📖 Read Instagram account profile info and media | instagrammanagecomments | 💬 Create, delete, and manage comments | instagrammanagemessages | 📤 Send and receive Instagram messages | pagesshowlist | 📄 Access connected Facebook pages 🎫 Access Token Generation > ⚠️ Important Setup:+ > - [ ] Use Facebook's Graph API Explorer > - [ ] Generate a User Access Token with required permissions > - [ ] ⚡ Important: Tokens expire periodically and need refreshing 🌐 Webhook Configuration 🔗 Setup Webhook URL > 📌 Configuration Checklist: > - [ ] In Meta App Dashboard, navigate to Products → Webhooks > - [ ] Subscribe to Instagram object > - [ ] Configure webhook URL: your-n8n-domain/webhook/instagram > - [ ] Set verification token (use "test" or create secure token) > - [ ] Select webhook fields: > - ✅ comments - For comment notifications > - ✅ messages - For DM notifications (if needed) ✅ Webhook Verification Process The workflow handles Meta's webhook verification automatically: 📡 Meta sends GET request with hub.challenge parameter 🔄 Workflow responds with the challenge value to confirm subscription 📊 Google Sheets Setup Example - https://docs.google.com/spreadsheets/d/1ONPKJZOpQTSxbasVcCB7oBjbZcCyAm9gZ-UNPoXM21A/edit?usp=sharing 📋 Create Response Management Sheet Set up a Google Sheets document with the following structure: 📝 Sheet 1 - Comment Responses: | Column | Description | Example | |--------|-------------|---------| | 💬 Comment | Trigger keywords | "auto", "info", "help" | | 📝 Message | Corresponding response message | "Thanks for your comment! We'll get back to you soon." | 📈 Sheet 2 - Interaction Log: | Column | Description | Purpose | |--------|-------------|---------| | ⏰ Time | Timestamp of interaction | Track when interactions occur | | 🆔 User Id | Instagram user ID | Identify unique users | | 👤 Username | Instagram username | Human-readable identification | | 📝 Note | Additional notes or error messages | Debugging and analytics | --- 🔧 Built By - akash@codescale.tech
By Akash KankariyaAutomated Gmail classification & response system with GPT and WhatsApp alerts
This n8n template uses AI to automatically classify incoming Gmail messages into five categories and route them to the right people or departments. It can also reply automatically and send WhatsApp alerts for urgent or relevant messages. This helps ensure high-priority emails never get missed, while other messages are handled efficiently. How It Works Trigger A new email in Gmail triggers the workflow. Classification (OpenAI GPT) The email is analyzed by an OpenAI GPT model and classified into one of: High Priority Customer Support Promotion Finance/Billing Random/Other Conditional Logic & Actions High Priority → Create draft reply + send WhatsApp alert. Customer Support → Auto-reply + send WhatsApp confirmation alert. Promotion → Summarize email + send WhatsApp promotional alert. Finance/Billing → Forward to finance team + send WhatsApp finance alert. Random/Other → Label and log only. Multi-Channel Output Responses are sent via Gmail. Alerts are sent via WhatsApp (or another compatible API). Setup Instructions Step 1: Gmail Authorization Add a Gmail node in n8n. Connect using OAuth2 and grant read/send permissions. Step 2: OpenAI API Key Get your API key from OpenAI. Add it to n8n credentials for the OpenAI node. Step 3: WhatsApp Integration Use your WhatsApp Business API or a provider like Twilio or 360Dialog. Replace placeholders with your details: [YOURWHATSAPPNUMBER] [YOURFINANCETEAM_NUMBER] [YOURSUPPORTTEAM_NUMBER] Step 4: Import & Run Import the workflow JSON into n8n. Adjust prompts, labels, and routing logic as needed. Execute and monitor results. Good to Know Fully customizable — add or remove categories, adjust responses, and change alert channels. Can be integrated with Slack, Discord, Trello, Notion, Jira, or CRM systems. Scales easily across teams and departments. Requirements Gmail account with OAuth2 credentials set up in n8n OpenAI API key for classification and content generation WhatsApp (or other messaging service) integration Optional: Slack, Notion, CRM, or accounting tool integrations Customization Ideas Create support tickets in Trello, Notion, or Jira from Customer Support emails. Sync Finance emails with QuickBooks, Stripe, or Google Sheets. Replace WhatsApp alerts with Slack or Discord messages. Use Zapier/Make for cross-platform automations.
By Nabin BhandariReceive updates for AWS SNS events
Companion workflow for AWS SNS Trigger node docs
By amudhanComprehensive SEO keyword research & analysis with DataForSEO and Google Sheets
Overview This n8n workflow, named "Keyword Search for Blogs," automates the process of gathering and organizing keyword research data for SEO purposes. It integrates with Google Sheets and Google Drive to manage input and output data, and leverages the DataForSEO API to fetch comprehensive keyword-related information, including related keywords, keyword suggestions, keyword ideas, autocomplete suggestions, subtopics, and SERP (Search Engine Results Page) analysis. The workflow is designed to streamline SEO research by collecting, processing, and storing data in an organized manner for blog content creation. Workflow Functionality The workflow performs the following key functions: Trigger: Initiated manually via the "When clicking ‘Test workflow’" node, allowing users to start the process on-demand. Input Data Retrieval: Reads primary keywords, location, and language data from a specified Google Sheet ("SEO PRO"). Spreadsheet Creation: Creates a new Google Sheet with a dynamic title based on the current date (e.g., "YYYY-MM-DD-seo pro") and predefined sheet names for organizing different types of keyword data (e.g., keyword, SERP, Content, related keyword, keyword ideas, suggested keyword, subtopics, autocomplete). Google Drive Integration: Moves the newly created spreadsheet to a designated folder ("seo pro") in Google Drive for organized storage. API Data Collection: Related Keywords: Fetches related keywords using the DataForSEO API (/v3/dataforseolabs/google/relatedkeywords/live), including SERP information and keyword metrics like search volume, CPC, and competition. Keyword Suggestions: Retrieves keyword suggestions via the DataForSEO API (/v3/dataforseolabs/google/keywordsuggestions/live). Keyword Ideas: Collects keyword ideas using the DataForSEO API (/v3/dataforseolabs/google/keywordideas/live). Autocomplete Suggestions: Gathers Google autocomplete suggestions through the DataForSEO API (/v3/serp/google/autocomplete/live/advanced). Subtopics: Generates subtopics for the primary keyword using the DataForSEO API (/v3/contentgeneration/generatesub_topics/live). People Also Ask & Organic Results: Pulls "People Also Ask" questions and organic SERP results via the DataForSEO API (/v3/serp/google/organic/live/advanced). Data Processing: Uses Split Out nodes to break down API responses into individual items for processing. Employs Edit Fields nodes to map and format data, extracting relevant fields like keyword, search intent, search volume, CPC, competition, keyword difficulty, and SERP item types. Filters SERP results to separate "People Also Ask" and organic results for targeted processing. Data Storage: Appends processed data to multiple sheets in the destination Google Sheet ("2025-06-08-seo pro") across different tabs: Master Sheet: Stores comprehensive data including keywords, search intent, related keywords, SERP analysis, and more. Related Keywords: Stores related keyword data with metrics. Suggested Keywords: Stores suggested keyword data. Keyword Ideas: Stores keyword ideas with relevant metrics. Autocomplete: Stores autocomplete suggestions. Subtopics: Stores generated subtopics. Organic Results: Stores organic SERP data with details like domain, URL, title, and description. Key Features Automation: Eliminates manual keyword research by automating data collection and organization. Scalability: Processes multiple keywords and their related data in a single workflow run, with a limit of 100 related items per API call. Dynamic Organization: Creates and organizes data in a new Google Sheet with a timestamped title, ensuring easy tracking of research over time. Comprehensive SEO Insights: Collects diverse SEO metrics (e.g., keyword difficulty, search intent, SERP item types) to inform content strategy. Error Handling: Uses filters to ensure only relevant data (e.g., "peoplealsoask" or "organic" results) is processed and stored. Use Case This workflow is ideal for SEO professionals, content creators, and digital marketers who need to perform in-depth keyword research for blog content. It provides a structured dataset that can be used to identify high-potential keywords, understand search intent, analyze SERP competition, and generate content ideas, all of which are critical for optimizing blog posts to rank higher on search engines. Inputs Google Sheet ("SEO PRO"): Contains primary keywords, location names, and language names. Google Drive Folder: Destination folder ("seo pro") for storing the output spreadsheet. DataForSEO API Credentials: Requires HTTP Basic Authentication credentials for accessing DataForSEO API endpoints. Outputs A new Google Sheet titled with the current date (e.g., "2025-06-08-seo pro") containing multiple tabs: Master Sheet: Aggregated data for all keyword types. Related Keywords: Detailed metrics for related keywords. Suggested Keywords: Suggested keywords with metrics. Keyword Ideas: Keyword ideas with metrics. Autocomplete: Google autocomplete suggestions. Subtopics: Generated subtopics for content planning. Organic Results: Organic SERP data including domains, URLs, titles, and descriptions. Benefits Time-Saving: Automates repetitive tasks, reducing manual effort in keyword research. Organized Data: Stores all data in a structured Google Sheet for easy access and analysis. Actionable Insights: Provides detailed SEO metrics to guide content creation and optimization strategies. Scalable and Reusable: Can be reused for different keywords by updating the input Google Sheet. Technical Details Nodes: Utilizes n8n nodes including manualTrigger, googleSheets, googleDrive, httpRequest, splitOut, set, and filter. API Integration: Leverages DataForSEO API for real-time keyword and SERP data. Credentials: Requires Google Sheets OAuth2 and Google Drive OAuth2 credentials, along with DataForSEO HTTP Basic Authentication. Data Mapping: Uses set nodes to map API response fields to desired output formats, ensuring compatibility with Google Sheets. Potential Enhancements Add error handling for API failures or invalid inputs. Include additional DataForSEO API endpoints for more granular data (e.g., competitor analysis). Implement deduplication logic to avoid redundant keyword entries. Add a scheduling node to run the workflow automatically at regular intervals. This workflow is a powerful tool for SEO-driven content planning, providing a robust foundation for creating optimized blog content.
By rana tamureEnterprise knowledge search with GPT-4 Turbo, Google Drive & Academic APIs
Enterprise Knowledge Search with GPT-4 Turbo, Google Drive & Academic APIs This workflow provides an enterprise-grade RAG (Retrieval-Augmented Generation) system that intelligently searches multiple sources and generates AI-powered responses using GPT-4 Turbo. How it works This workflow provides an enterprise-grade RAG (Retrieval-Augmented Generation) system that intelligently searches multiple sources and generates AI-powered responses using GPT-4 Turbo. Key Steps Form Input - Collects user queries with customizable search scope, response style, and language preferences Intelligent Search - Routes queries to appropriate sources (web, academic papers, news, internal documents) Data Aggregation - Unifies and processes information from multiple sources with quality scoring AI Processing - Uses GPT-4 Turbo to generate context-aware, source-grounded responses Response Enhancement - Formats outputs in various styles (comprehensive, concise, technical, etc.) Multi-Channel Delivery - Delivers results via webhook, email, Slack, and optional PDF generation Data Sources & AI Models Search Sources Web Search: Google, Bing, DuckDuckGo integration Academic Papers: arXiv, PubMed, Google Scholar via Crossref API News Articles: News API, RSS feeds, real-time news Technical Documentation: GitHub, Stack Overflow, documentation sites Internal Knowledge: Google Drive, Confluence, Notion integration AI Models GPT-4 Turbo: Primary language model for response generation Embedding Models: For semantic search and similarity matching Custom Prompts: Specialized prompts for different response styles Set up steps Setup time: 15-20 minutes Configure API credentials - Set up OpenAI API, News API, Google Drive, and other service credentials Set up search sources - Configure academic databases, news APIs, and internal knowledge sources Connect analytics - Link Google Sheets for usage tracking and performance monitoring Configure notifications - Set up Slack channels and email templates for automated alerts Test the workflow - Run sample queries to verify all components are working correctly Keep detailed configuration notes in sticky notes inside your workflow
By vinci-king-01Weekly Facebook ads performance reports with AI-powered analysis & Gmail delivery
Who’s it for Perfect for marketing agencies that manage multiple Facebook ad accounts and want to automate their weekly reporting. It eliminates manual data collection, analysis, and client updates by delivering a ready-to-share PDF report. How it works Every Monday, the workflow: Fetches the previous week’s campaign metrics from the Facebook Graph API. Formats and summarizes each campaign’s performance using OpenAI. Merges all summaries into one comprehensive report with insights and next-week suggestions. Converts the report into a polished PDF using any PDF generation API. Sends the final PDF report automatically to the client via Gmail. How to set up Connect your Facebook, OpenAI, and Gmail accounts in n8n. Add credentials for your preferred PDF generator (e.g., PDFCrowd, Placid, etc.). Open the “Set Node” to customize recipient email, date range, or report text. Requirements Facebook Graph API access token OpenAI API key Gmail credentials API key for your PDF generation service How to customize You can modify the trigger day, personalize the report design, or include additional analytics such as ROAS, CPC, or conversion data for deeper insights.
By Muhammad AliCreate a coupon on Paddle
No description available.
By Harshil Agrawal