Webhook and X (Formerly Twitter) integration

Who's it for This template is for home cooks, small restaurant owners, or anyone who wants to streamline their meal planning, ingredient cost tracking, leftover management, nutritional analysis, and social media promotion. It's ideal for those looking to optimize their kitchen operations, reduce food waste, maintain a healthy diet, and efficiently share their culinary creations. How it works / What it does This advanced workflow acts as a comprehensive culinary assistant. Triggered by a new menu item, it performs several key functions: Cost and Ingredient Tracking:** A "Menu Agent" uses AI to analyze your input (e.g., a recipe or dish) and extract a detailed list of ingredients, their associated costs, unit prices, and total cost, then logs this into a Google Sheet as a "Recipe List." Leftover Management:** A "Leftovers Agent" identifies any unused ingredients from your planned dish and suggests three new recipes to utilize them, helping to minimize food waste. This information is also recorded in a Google Sheet. Nutritional Diary:** A "Nutritionist Agent" generates a diary-style entry with dietary advice based on the meal, highlighting key nutrients and offering personalized suggestions. This entry is appended to a "Diary" Google Sheet. Social Media Promotion:** A "Post Agent" takes the nutritional diary entry and transforms it into an engaging social media post (specifically for X/Twitter in this template), which is then sent as a direct message, ready for you to share with your followers. How to set up Webhook Trigger: The workflow starts with a Webhook. Copy the webhook URL from the "Webhook" node. You will send your menu item input to this URL. Google Sheets Integration: You need to set up a Google Sheets credential for your n8n instance. Create a Google Sheet document (e.g., "Recipe List"). Within this document, create three sheets: "Recipe: This sheet will store your menu items, ingredients, costs, etc. Ensure it has columns for Date, Item, Ingredients, Ingredient Cost, Unit Price, Quantity, Total, Cost, and Leftover Ingredients. "leftovers" (Leftovers): This sheet will store suggested recipes for leftover ingredients. Ensure it has columns for Date and Ingredients. "diary" (Diary): This sheet will store your nutritional diary entries. Ensure it has a column for Diary. In the "Append row in sheet", "Append row in sheet1", and "Append row in sheet2" nodes, replace the Document ID with the ID of your Google Sheet. For "Sheet Name," ensure you select the correct sheet (e.g., "レシピ", "diary", "leftovers") from the dropdown. OpenRouter Chat Model: Set up your OpenRouter credentials in the "OpenRouter Chat Model" nodes. You will need your OpenRouter API key. Twitter Integration: Set up your Twitter credentials for the "Create Direct Message" node. In the "Create Direct Message" node, specify the User (username) to whom the direct message should be sent. This is typically your own Twitter handle or a test account. Requirements An n8n instance. A Google account with Google Sheets enabled. An OpenRouter API key. A Twitter (X) account with developer access to send Direct Messages. How to customize the workflow Input Data:** The initial input to the "Webhook" node is expected to be the name of a dish or recipe. You can modify the "Menu Agent" to accept more detailed inputs if needed. Google Sheets Structure:** Adjust the column mappings in the Google Sheets nodes if your spreadsheet column headers differ. AI Agent Prompts:** Customize the System Message in each AI Agent node (Menu Agent, Leftovers Agent, Nutritionist Agent, Post Agent) to refine their behavior and the kind of output they generate. For example, you could ask the Nutritionist Agent to focus on specific dietary needs. Social Media Platform:** The "Create Direct Message" node is configured for Twitter. You can swap this with another social media node (e.g., Mastodon, Discord) if you prefer to post elsewhere, remembering to adjust the "Post Agent" system message accordingly. Output Parser:** The "Structured Output Parser" is configured for a specific JSON structure. If you change the "Menu Agent" to output a different structure, you'll need to update this parser.

Generate social posts from GitHub pushes to Twitter and LinkedIn On each GitHub push, this workflow checks if the commit set includes README.md and CHANGELOG.md, fetches both files, lets an LLM generate a Twitter and LinkedIn post, then publishes to Twitter and LinkedIn (Person). Apps & Nodes Trigger:** Webhook Logic:** IF, Merge, Aggregate GitHub:** Get Repository File (×2) Files:** Extract from File (text) (×2) AI:** OpenAI Chat Model → LLM Chain (+ Structured Output Parser) Publish:** Twitter, LinkedIn (Person) Prerequisites GitHub:** OAuth2 or PAT with repo read. OpenAI:** API key. Twitter:* OAuth2 app with *Read and Write; scopes tweet.read tweet.write users.read offline.access. LinkedIn (Person):* OAuth2 credentials; required scope:* w_member_social, openid. Setup GitHub Webhook: Repo → Settings → Webhooks Payload URL: https://<your-n8n-domain>/webhook/github/push Content type: application/json • Event: Push • Secret (optional) • Branches as needed. Credentials: Connect GitHub, OpenAI, Twitter, and LinkedIn (Person). How it Works Webhook receives GitHub push payload. IF checks that README and CHANGELOG appear in added/modified. GitHub (Get Repository File) pulls README.md and CHANGELOG.md. Extract from File (text) converts both binaries to text. Merge & Aggregate combines into one item with both contents. LLM (OpenAI + Parser) returns a JSON with twitter and linkedin. Twitter posts the tweet. LinkedIn (Person) posts the LinkedIn text.

How It Works ⚙️ This workflow is a comprehensive, AI-powered system that acts as a virtual content manager for creators and marketing teams. It automates the entire content lifecycle, from ingestion and analysis to multi-channel distribution and performance logging. Multi-Source Ingestion: The workflow starts by ingesting new content from a trigger, such as a WordPress blog post or an RSS Feed from a YouTube channel. AI-Powered Analysis: The new content is sent to an OpenAI (GPT-4) node, which performs a series of high-value tasks. It instantly creates a summary, extracts keywords, analyzes the sentiment, and generates tailored post drafts for different social media platforms. Smart Distribution: A Buffer node then takes these AI-generated, platform-specific posts and schedules them for optimal times across your social media channels like Twitter, LinkedIn, and Facebook. Centralized Archiving: All of the content data, including the AI-generated summaries and insights, are automatically logged into a Google Sheets database. This creates a powerful, searchable archive and an analytics dashboard for tracking content performance. How to Set Up 🛠️ Import the Workflow: Copy the provided workflow JSON and import it into your n8n instance. Configure Credentials: OpenAI: Add your API Key. WordPress: Add your API credentials. Buffer: Add your API credentials. Google Sheets: Add your OAuth2 credentials. Customize Workflow Nodes: Node 1 (WordPress Trigger): Select your WordPress credential. You can also add other trigger nodes like RSS Feed Read Trigger if needed. Node 2 (OpenAI): You can customize the prompt to get different kinds of output or translate into more languages. Node 4 (Buffer): Select the social media profiles you want to post to. Node 5 (Google Sheets): Replace the placeholder [YOUR SPREADSHEET ID] and [YOUR CONTENT LOG SHEET NAME] with your own details and map the data columns. Save & Activate: Once all settings and credentials are configured, save the workflow and click the "Inactive" toggle in the top-right corner to make it live.

This is the workflow powering the n8n demo shown at StrapiConf 2022. The workflow searches matching Tweets every 30 minutes using the Interval node and listens to Form submissions using the Webhook node. Sentiment analysis is handled by Google using the Google Cloud Natural Language node before the result is stored in Strapi using the Strapi node. (These were originally two separate workflows that have been combined into one to simplify sharing.)