Family assistant: Schedule, meal & routine management with Email & Telegram
The FamilyFlow Assistant is your n8n-powered 🚀 companion designed to streamline daily parenting tasks, reduce mental load, and bring a bit more organization and fun into your family life. This versatile workflow automates reminders, generates helpful ideas, and provides gentle nudges to keep your household running smoothly.
Why FamilyFlow Assistant? 🤔
Parenting is a demanding (and rewarding!) job. Juggling schedules, meals, routines, and remembering everything can be overwhelming. FamilyFlow Assistant aims to:
- Reduce Mental Clutter: Offload common reminders and to-dos to an automated system.
- Enhance Organization: Keep track of activities, appointments, and important checks.
- Spark Joy & Creativity: Generate meal ideas, story starters, and positive thoughts.
- Promote Routine: Help establish and maintain consistent morning and evening routines.
- Save Time: Automate repetitive prompts and checks, freeing you up for what matters most.
Core Features & Automations 🧩
This workflow bundle comes packed with several independent yet complementary automations:
📅 Daily & Weekly Organization:
- Activity & Appointment Reminders: Get a daily heads-up on scheduled events for the family.
- Morning Routine Checklist: Start the day right with a friendly checklist for kids (or parents!).
- Bedtime Routine Nudge: A gentle reminder to begin the wind-down process.
- Evening “Did You Remember?” Scan: A quick mental checklist for common end-of-day to-dos.
- Weekly “Plan Ahead” Prompt: A Sunday reminder to review the upcoming week.
- School/Daycare Comms Check: Prompts to check for important updates.
💡 Inspiration & Well-being:
- Meal Idea Generator: Never wonder “what’s for dinner?” again (or at least, less often!).
- Positive Thought / Fun Fact Sender: A little daily dose of brightness.
- Story Starter / Quick Activity Prompt: Spark imagination or a quick family interaction.
- Weekly Wins & Gratitude Reminder: Encourage reflection on positive moments.
⏱️ Optional Helpers:
- Screen Time Break Reminder: (Disabled by default) A nudge for offline time.
Getting Started: Setup & Customization 🛠️
Make FamilyFlow Assistant truly yours with these simple steps:
- Import the Workflow: Add the provided
.jsonfile to your n8n instance. - Configure Credentials:
- Email: Set up your preferred email sending credential (e.g., SMTP, Gmail) in all “Email Send” nodes. You’ll likely use the same one for all.
- Personalize Content (Crucial!):
- Email Addresses: Update parents@example.com to your actual email(s) in all Email nodes.
- Schedules & Activities: Edit the “Define Daily Schedules” (Set node) with your family’s actual events.
- Meal Ideas: Customize the mealIdeas array in the “Generate Meal Idea” (Function node).
- Checklists & Prompts: Tailor the text/HTML in Email nodes for morning/bedtime routines, check-ins, story starters, etc., to fit your family’s style.
- Positive Thoughts/Facts: Update the lists in the “Get Positive Thought/Fact” (Function node).
- Adjust Triggers (Cron Nodes):
- Modify the “Rule” in each Cron node to set the exact time and frequency for each automation.
- Activate Automations:
- The main workflow and most automations are inactive by default. Toggle the “Active” switch ON for the entire workflow or for individual automations/nodes you wish to use.
- Remember, the “Screen Time Break Reminder” is disabled by default; enable its Email node if desired.
How Each Automation Works (Briefly) ⚙️
Each automation generally follows this pattern:
- TRIGGER: An event starts the flow (e.g., a scheduled time via Cron).
- PROCESS: Data is defined (e.g., list of activities, meal ideas) or generated (e.g., a random selection, a formatted message).
- RESPOND: An action is taken, typically sending an email with the relevant information or reminder.
For instance, the “Daily Activity Reminder” uses a Cron trigger, a Set node to hold your schedule, a Function node to filter for today’s events, an IF node to check if there are any, and finally an Email node to send the reminder.
Expanding Your Assistant 🚀
FamilyFlow Assistant is a great starting point. Consider these ideas to extend its capabilities:
- Integrate Calendars: Connect to Google Calendar or Outlook Calendar to fetch events dynamically.
- Use Different Notifiers: Send messages via Telegram, WhatsApp, Slack, or push notifications.
- Smart Home Integration: If you have smart home devices, trigger lights or announcements for routines.
- Shared To-Do Lists: Update a shared Todoist or Microsoft To Do list.
- Interactive Input: Use n8n forms or Telegram commands to add events or trigger specific actions.
Requirements 📋
- An active n8n instance (self-hosted or cloud).
- Email sending credentials configured in n8n.
- A little time to customize the content to perfectly match your family’s needs!
Embrace the flow and let your FamilyFlow Assistant help make parenting a little smoother!
Family Assistant: Schedule, Meal, and Routine Management with Email & Telegram
This n8n workflow provides a robust system for managing family schedules, meal plans, and daily routines, offering flexible notification options via both email and Telegram. It allows for scheduled reminders and the ability to trigger actions manually through Telegram commands.
What it does
This workflow automates the following tasks:
- Scheduled Reminders: At predefined intervals (e.g., daily, weekly), the workflow can trigger and send out routine reminders or information.
- Telegram Command Processing: It listens for specific commands or messages sent to a configured Telegram bot.
- Conditional Logic: Based on the received Telegram message, it applies conditional logic to determine the appropriate action.
- Information Extraction: It extracts relevant information (e.g.,
chat_id,text) from incoming Telegram messages. - Email Notifications: It can send detailed email notifications for scheduled events or in response to Telegram commands.
- Telegram Notifications: It can send messages back to the user via Telegram, confirming actions or providing requested information.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Email Account (SMTP): Configured SMTP credentials for sending emails (can be a generic email service or a specific one like Gmail).
- Telegram Bot: A Telegram bot token and a
chat_idfor the recipient(s) to send and receive messages. - Gmail Account (Optional): If you intend to use the Gmail node for sending emails, you'll need a Gmail API credential.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Telegram Trigger & Telegram Node: Set up your Telegram Bot API credentials. You will need your bot token and the
chat_idof the user or group you want to interact with. - Send Email Node: Configure your SMTP credentials (host, port, user, password, etc.).
- Gmail Node (Optional): If using the Gmail node, configure your Google OAuth2 credentials.
- Telegram Trigger & Telegram Node: Set up your Telegram Bot API credentials. You will need your bot token and the
- Customize the Cron Node: Adjust the "Cron" node (ID: 7) to your desired schedule for routine reminders. For example, set it to run daily at a specific time for daily routine notifications.
- Customize the Telegram Trigger Node: Ensure the "Telegram Trigger" node (ID: 50) is active and listening for messages. You may need to specify the allowed
chat_ids or message types. - Adjust the "If" Node: Modify the conditions in the "If" node (ID: 20) to match the Telegram commands or keywords you want to use to trigger specific actions (e.g., "meal plan", "schedule today").
- Update "Edit Fields" (Set) Nodes: The "Edit Fields" (Set) nodes (ID: 38) are placeholders for defining the content of your messages. Customize the
subject,text, andtofields for email and thetextfield for Telegram messages according to your family's needs. - Activate the Workflow: Once configured, activate the workflow to start receiving scheduled reminders and responding to Telegram commands.
This workflow provides a flexible foundation for automating various family management tasks, allowing for easy expansion with more complex logic and integrations.
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 invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.