HumationHuman + Automation
Back to Catalog

Automate pet grooming posts & bookings with AI, Facebook & Telegram bot

Christian MoisesChristian Moises
860 views
2/3/2026
Google DriveAutomationEmailAttachmentPDF
Official Page

Telegram Pet Grooming Bot – Social Media & Booking Automation

This workflow automates Facebook posting and appointment booking directly from a Telegram bot, making it especially useful for pet grooming businesses that want to keep their social media active while also confirming new bookings in real time.

If you are managing posts manually and handling bookings through chat, this workflow replaces that with an integrated system that connects Telegram, Google Sheets, Facebook, Google Calendar, and AI models.

Use case: Perfect for grooming shops that want to streamline customer communication, reduce missed appointments, and keep a steady flow of engaging Facebook content.

How It Works

  1. Trigger Input

    • The workflow starts when a Telegram user sends either:

      • /post → to publish the next pending social media post.
      • /book → to schedule a grooming appointment.
      • Or when the workflow runs on a schedule for auto-posting.

  2. Social Media Posting

    • The workflow retrieves the first entry from a Google Sheet where Uploaded = Fa.
    • An AI model analyzes the pet image and generates a warm, engaging caption.
    • The post (image + caption) is published to your Facebook Page.
    • The Google Sheet is updated to mark the post as “Uploaded,” keeping the content queue organized.

  3. Appointment Booking

    • When a user sends /book, the bot collects booking details (pet name, date, and time).

    • The AI model interprets natural inputs like “next Friday at 2 pm” into a proper date-time format.

    • Availability is checked in Google Calendar.

      • If free → a new event is created, and the bot sends a confirmation.
      • If unavailable → the user receives a rejection message with alternative suggestions.

  4. Post Queueing

    • When a user sends an image with a caption, the workflow saves it to the Post Queue Google Sheet.
    • This keeps posts lined up for later scheduling.

Google Sheet Queue Structure

Example queue columns:

  • Image_URL
  • Pet_Name
  • Owner_Name
  • Uploaded (True/False)

Screenshot 20250820 204556.png (Refer to the attached screenshot for a sample queue format.)

How to Use

  1. Import this workflow into n8n.

  2. Connect your accounts in n8n:

    • Telegram Bot (via BotFather token).
    • Google Sheets (for the posting queue).
    • Google Calendar (for bookings).
    • Facebook Page (for publishing posts).
    • OpenAI / Google Gemini (for captioning and booking interpretation).

  3. Create a Google Sheet with the required columns (Image_URL, Pet_Name, Owner_Name, Uploaded).

  4. Start the workflow — your Telegram bot can now manage both posts and bookings automatically.

Requirements

  • Telegram Bot API Token (from BotFather).
  • Google Sheets + Calendar access (connected in n8n).
  • Facebook Page Admin access.
  • AI API Key (OpenAI or Google Gemini).
  • Basic knowledge of connecting credentials in n8n.

Customizing This Workflow

You can tailor this workflow to fit your business by:

  • Adding approval steps: Require admin approval before a queued post goes live.
  • Expanding queue fields: Track post type, hashtags, or scheduling time.
  • Custom booking logic: Adjust availability rules (e.g., block lunch breaks, add buffer time).
  • Integrating downstream apps: Sync confirmed bookings to CRM or send reminders via SMS/WhatsApp.

n8n Workflow: AI-Powered Pet Grooming Social Media Posts & Booking Management

This n8n workflow automates the creation of engaging social media posts for pet grooming services and manages booking requests received via Telegram. It leverages AI to generate creative content and integrates with Google Sheets, Google Calendar, and Facebook to streamline marketing and scheduling.

What it does

This workflow orchestrates several key processes:

  1. Triggers on Telegram Messages: It listens for incoming messages on a configured Telegram bot.
  2. Analyzes Telegram Commands: It uses a "Switch" node to differentiate between user commands, specifically looking for a "Book" command.
  3. Generates Social Media Posts (AI Agent):
    • If no specific command is detected, it uses an AI Agent (powered by OpenAI or Google Gemini) to brainstorm and generate creative ideas for pet grooming social media posts.
    • It then structures this AI-generated content into a consistent format using a "Structured Output Parser."
    • The generated post is then sent to a Google Sheet for review and storage.
    • Finally, the AI-generated post is published to a Facebook Page.
  4. Manages Booking Requests (AI Agent & Calendar):
    • If a "Book" command is detected in Telegram, an AI Agent (powered by OpenAI or Google Gemini) processes the booking request.
    • It extracts relevant details for a booking from the Telegram message.
    • It then creates a new event in Google Calendar based on the extracted booking information.
    • A confirmation message is sent back to the user via Telegram.
  5. Scheduled Social Media Posting: A "Schedule Trigger" can be configured to periodically run the social media post generation and publishing part of the workflow, ensuring a consistent online presence.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Telegram Bot Token: A Telegram bot configured with a token for the "Telegram Trigger" and "Telegram" nodes.
  • Google Account:
    • Google Sheets: A Google Sheet to store and manage AI-generated social media posts.
    • Google Calendar: A Google Calendar to manage booking appointments.
  • Facebook Page: A Facebook Page and a Facebook Graph API access token with appropriate permissions to publish posts.
  • AI Service:
    • OpenAI API Key OR
    • Google Gemini API Key
    • (The workflow is configured to use either OpenAI Chat Model or Google Gemini Chat Model and OpenAI or Google Gemini for AI Agent tasks.)

Setup/Usage

  1. Import the workflow: Download the JSON provided and import it into your n8n instance.
  2. Configure Credentials:
    • Set up your Telegram Bot API credential for both the "Telegram Trigger" and "Telegram" nodes.
    • Configure your Google OAuth credential for the "Google Sheets" and "Google Calendar" nodes.
    • Set up your Facebook Graph API credential for the "Facebook Graph API" node.
    • Configure your OpenAI API Key or Google Gemini API Key credentials for the respective AI nodes.
  3. Customize Nodes:
    • Telegram Trigger: Ensure the "Allowed Updates" and "Message Type" are configured as needed.
    • Google Sheets: Update the Spreadsheet ID and Sheet Name to your desired Google Sheet for social media posts.
    • Google Calendar: Update the Calendar ID where bookings should be created.
    • Facebook Graph API: Specify your Facebook Page ID and customize the message content for posts.
    • AI Agent / OpenAI Chat Model / Google Gemini Chat Model: Review the prompts and configurations for the AI models to ensure they generate content suitable for your pet grooming business.
    • Structured Output Parser: Adjust the schema if you want a different output structure from the AI.
    • Edit Fields (Set): Customize any data transformations as needed.
    • Schedule Trigger: If you want scheduled posts, configure the interval for the "Schedule Trigger" node.
  4. Activate the workflow: Once all credentials and configurations are set, activate the workflow.

This workflow provides a robust foundation for automating your pet grooming business's online presence and booking management, allowing you to focus more on your furry clients!

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.

Ranjan DailataBy Ranjan Dailata
161

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 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.

Le NguyenBy Le Nguyen
942