Workflow Templates

An automated workflow that scrapes Shopify store information and product data using the Shopify Scraper API from RapidAPI, triggered by a user submitting a website URL, then logs data into Google Sheets for easy access and analysis. Node-by-Node Explanation On form submission** Triggers when a user submits a Shopify store website URL. Store Info Scrap Request** Sends a POST request to shopify-scraper4.p.rapidapi.com/shopinfo.php to fetch store metadata (name, location, domain, etc.). Products Scarp Request** Sends a POST request to shopify-scraper4.p.rapidapi.com/products.php to retrieve detailed product data (titles, prices, tags, etc.). Append Store Info Google Sheets** Appends store metadata into the "Shop Info" sheet in Google Sheets. Append Products Data In Google Sheets** Appends product data into the "Products" sheet in Google Sheets. Use Case Ideal for businesses or analysts who want to quickly gather Shopify store insights and product catalogs without manual data collection, enabling data-driven decision-making or competitive analysis. Benefits Automates Shopify data extraction with the powerful Shopify Scraper API on RapidAPI. Saves time by collecting and organizing data automatically into Google Sheets. Easily scalable and adaptable for multiple Shopify stores. 🔑 How to Get API Key from RapidAPI Shopify Scraper Follow these steps to get your API key and start using it in your workflow: Visit the API Page 👉 Click here to open Shopify Scraper API on RapidAPI Log in or Sign Up Use your Google, GitHub, or email account to sign in. If you're new, complete a quick sign-up. Subscribe to a Pricing Plan Go to the Pricing tab on the API page. Select a plan (free or paid, depending on your needs). Click Subscribe. Access Your API Key Navigate to the Endpoints tab. Look for the X-RapidAPI-Key under Request Headers. Copy the value shown — this is your API key. Use the Key in Your Workflow In your n8n workflow (HTTP Request node), replace: "x-rapidapi-key": "your key" with: "x-rapidapi-key": "YOUR_ACTUAL_API_KEY" `

Community Node Disclaimer: This workflow uses KlickTipp community nodes. Introduction This workflow creates a complete two-way synchronization between KlickTipp and Google Calendar. When a contact in KlickTipp is tagged, an event is automatically created in Google Calendar. If event status changes or if attendees respond, their RSVP status and event status are reflected in KlickTipp — keeping your contact database, campaigns, and event insights always up to date. Perfect for marketers, coaches, or event organizers who want to automatically send event invites and instantly capture participation status without manual updates. How it works Google Calendar → KlickTipp: This template keeps your KlickTipp list in sync with Google Calendar across the full event lifecycle. For every incoming event, the workflow follows these steps: Watch Google Calendar events Listens for: Event Created Event Updated Event Cancelled Iterate through attendees Each attendee is handled as a separate item. This ensures accurate contact updates and tagging even for large events or webinars. Filter attendees (optional) Attendees from internal or excluded email domains can be filtered out before any processing. Check if the attendee already exists in KlickTipp If the contact exists → update the contact. If the contact does not exist → subscribe the contact (with Single or Double Opt-In, depending on action). Transfer event data to KlickTipp Event details (summary, description, location, start and end time) are written into KlickTipp custom fields. Contacts always reflect the most recent event information. Route by attendee response status Attendees are routed based on their responseStatus: needsAction → contact was added to an event accepted → event confirmed declined → event declined tentative → event considered Apply tags in KlickTipp Based on event type and attendee status, the workflow applies the corresponding tags: Event created / updated Event canceled Event confirmed Event declined Event considered KlickTipp → Google Calendar: Watches for a tag like “Send an event invitation via Google Calendar”. Creates an event in Google Calendar using mapped KlickTipp fields. Setup Instructions KlickTipp Preparation Prepare custom fields Google Calendar | event summary, data type: "Single line" Google Calendar | event description, data type: "Single line" Google Calendar | event location, data type: "Single line" Google Calendar | event start datetime, data type: "Datetime" Google Calendar | event end datetime, data type: "Datetime" Prepare tags: Google Calendar | event created/updated Google Calendar | event canceled Google Calendar | event declined Google Calendar | event confirmed Google Calendar | event considered Send an event invitation via Google Calendar Prepare outbound: Activation tag: Send an event invitation via Google Calendar Activation URL: webhook URL from trigger Credential Configuration Connect your Google Calendar account using Client ID and Client Secret from the Google Cloud. Authenticate your KlickTipp connection with username/password credentials (API access required). Customization Recommended poll frequency: every 1–5 minutes for near real-time updates. Adjust to your local timezone if necessary. Each trigger works independently, allowing partial deployments if only certain event types are needed. Ensure End > Start in your data. If you prefer a fixed duration, compute End from Start + minutes in a Date & Time node. If you want a Meet link, enable “Add Google Meet video conferencing” in the Calendar node instead of pasting a Calendar URL into Location.

Workflow Overview This workflow benefits anyone who: wants to automate writing new contacts (with an associated 'Newsletter' tag) in CentralStationCRM to a Rapidmail list Tools in this workflow CentralStationCRM, the simple and intuitive CRM for small teams. Here is our API documentation if you want to modify the workflow. Slack, brings people and information together Rapidmail, the really good newsletter software Workflow Screenshot Workflow Description This workflow consists of: a schedule trigger (set to 5 pm/daily) three HTTP Requests to the CentralStationCRM API two if-Nodes as logic gates a Slack node a "Do nothing, end workflow" node The schedule trigger The schedule trigger is set to trigger at 5 pm, every day. The thinking here: If you added new contacts into CentralStationCRM during your workday, the workflow will collect them afterwards. You can of course set your own time. First HTTP Request: Get new people of the day This node talks to the CentralStationCRM API and gets every newly created person of the day. Included are the tags, adresses, associated companies, and emails of the person. First if-gate: Does the person have a "Newsletter" tag? If you tagged your person with "Newsletter" in CentralStationCRM after creating it, this if-node will see it. -> if true: go to last HTTP Request (Rapidmail list) -> if false: go to Slack node Slack node: ask if the person should get a "Newsletter" tag Pretty much what the title says. The slack user sees a private message with the question "Should <person> be on your newsletter list" and can click "yes" or "no". second if-gate: Did the user click the "Yes"-button? -> if false: end workflow (do nothing node) -> if true: go to second HTTP request node second HTTP request: give person a "Newsletter" tag in CentralStationCRM This node again talks to the CentralStationCRM API and creates a new tag for the person, called "Newsletter". This is so you know later that this person is also receiving your newsletter. last HTTP request node: write person's name and email on Rapidmail list This node uses the Rapidmail API and the Rapidmail list ID to write a person with the "Newsletter" tag on a pre-created Rapidmail list for your newsletter. Customization ideas With this workflow, you could change the interval the workflow triggers, i.e. to once per week. you'd have to change the JSON code in the second node to fetch all the new people per week instead of per day customize the slack approval message to include more information on the person than the name, i.e. the company the person works for take the beginning - give tag to person in CentralStationCRM, trigger workflow, check for tag, ask for approval in slack - and then do something else with the last node, i.e. write the person a mail in Gmail or write their info in a Google sheet or do a web research with ai on the person. Go experiment ab bit! Preconditions For this workflow, you need: a CentralStationCRM account with API access an n8n account with API access a Rapidmail account with API access a Rapidmail recipient list Have fun with our workflow!

This workflow transforms raw marketing data from Google Sheets into a pivot-like summary table. It merges lookup data, groups spend by name, and appends the results into a clean reporting tab — all automatically, without needing to manually build pivot tables in Sheets. 🧑‍💻 Who’s it for Marketing analysts who track channel spend across campaigns Small businesses that rely on Google Sheets for reporting Teams that need automated daily rollups without rebuilding pivot tables manually ⚙️ How it works Get Marketing Data (Google Sheets) – Pulls raw spend data. Vlookup Data (Google Sheets) – Brings in reference/lookup fields (e.g., channel labels). Merge Tables – Joins marketing data and lookup data on the Channel column. Summarize – Groups data by Name and sums up Spend ($). Clear Sheet – Wipes the reporting tab to avoid duplicates. Append to Pivot Sheet – Writes the aggregated results into the "render pivot" sheet. The result: a pivot-style summary table inside Google Sheets, automatically refreshed by n8n. 🔑 Setup Instructions 1) Connect Google Sheets (OAuth2) In n8n → Credentials → New → Google Sheets (OAuth2) Sign in with your Google account and grant access In each Google Sheets node, select your Spreadsheet and the appropriate Worksheet: data (raw spend) Lookup (channel reference table) render pivot (output tab) 2) Configure Summarize Node Group by: Name Summarize: Spend ($) → sum 3) Test the Workflow Execute the workflow manually Check your "render pivot" tab — it should display aggregated spend by Name 🛠️ How to customize Change grouping fields (e.g., by Channel, Campaign, or Region) Add more aggregations (e.g., average CPC, max impressions) Use the Merge node to join extra data sources before summarizing Schedule execution to run daily for fresh rollups 📋 Requirements n8n (Cloud or self-hosted) Google Sheets account with structured data in data and Lookup tabs 📬 Contact Need help customizing this (e.g., filtering by campaign, sending reports by email, or formatting your pivot)? 📧 rbreen@ynteractive.com 🔗 Robert Breen 🌐 ynteractive.com

Easily ensure your n8n workflows are never lost! This template automates the process of backing up all your n8n workflows to a GitHub repository every 6 hours. Set it up once and enjoy worry-free workflow versioning and disaster recovery! 🔄✨ 📝 What This Workflow Does Schedules backups**: Triggers the workflow automatically every 6 hours—no manual steps needed. ⏰ Exports all current workflows**: Collects a JSON snapshot of every workflow in your n8n instance. 📦 Pushes backups to GitHub**: Commits each backup file to your specified GitHub repository with a time-stamped commit message for easy tracking. 🗂️🚀 Smart file handling**: Checks if a backup file already exists and creates or updates as needed, keeping your repository clean and organized. 🤖 ⚡️ Why Use This Template? Automate your workflow backups – never miss a backup again!** Seamless integration with GitHub** for team collaboration, change management, and rollback. Simple, reliable, and fully customizable** to match your backup intervals and repository setup. Peace of mind** that your critical automation assets are always protected. 📦 How the Template Works: Step-by-step Overview Scheduled Trigger: Fires every 6 hours to launch the backup sequence. Get All Workflows: Uses the HTTP Request node to fetch all n8n workflows from your instance as JSON data. Move Binary Data: Converts the JSON into a binary format, ready for GitHub storage. Edit/Create Backup File: Attempts to edit (update) an existing backup file in your GitHub repo. If the file does not exist, the workflow will create a new one. Conditional Logic: Checks after each run whether the backup file exists and ensures previous versions can be recovered or merged as needed. Repeat: The process auto-loops every 6 hours—no further intervention required! 🔧 How To Set Up On Your Server Import the template into your n8n instance. Configure your GitHub credentials in the workflow nodes. Update the GitHub repository details (owner, repository, and filePath) to use your own repo and desired file path. Set your n8n API key and update the API endpoint URL to match your deployment. Save and activate the workflow—now your backups are on autopilot! 👨‍💻 Example Use Cases Version control for rapidly changing automation environments. Safeguarding business-critical automation assets. Easy rollback in case of workflow corruption or accidental deletion. Team collaboration through GitHub's pull request and review process. 🌟 Pro Tips Adjust the backup interval in the Schedule Trigger node if you require more/less frequent backups. Use GitHub branch protection rules for enhanced workflow security. Pair this backup workflow with notifications (e.g., Slack or Email) for backup alerts. Protect your n8n workflows with automated, reliable, and versioned GitHub backups—set it and forget it! 🚦🔒

🎬 Auto Add AI Captions to Videos from Google Drive with ZapCap Description Stop wasting hours on video captioning. Upload your videos to a Google Drive folder, and ZapCap automatically generates professional subtitles for you. Download the finished video from your Google Drive and it’s ready to post. Fast, simple, and effortless. How It Works Google Drive Trigger – Watches your folder for new uploads. Send to ZapCap – Instantly creates accurate subtitles. Wait & Check Status – Automatically tracks progress. Download Captioned Video – Get your finished, captioned video. Upload Back to Drive – Saves it where you need it, ready to share. Why You’ll Love It 🚀 Save time — captions are added automatically. ⚡ Speed up content creation — get post-ready videos in minutes. 🎯 Professional results — subtitles are accurate and consistent. ☁️ Fully cloud-based — no local software, no manual work. Requirements ZapCap account & API key** — get your free API key here Google Drive account** (with OAuth credentials) n8n** (Cloud or self-hosted) Support Need help? Join our ZapCap Discord or email us at hi@zapcap.ai for assistance.

Gmail Attachment Extractor to Google Drive Description: This workflow monitors your Gmail inbox for new emails, specifically those with attachments, and automatically saves those attachments to a designated folder in your Google Drive. Use Case: Automatically archive invoices, client documents, reports, or photos sent via email to a structured cloud storage. How It Works This workflow operates in three main steps: Gmail New Email Trigger: The workflow starts with a Gmail Trigger node, set to monitor for new emails in your specified Gmail inbox (e.g., your primary inbox). It checks for emails that contain attachments. Conditional Check (Optional but Recommended): An If node checks if the email actually has attachments. This prevents errors if an email without an attachment somehow triggers the workflow. Upload to Google Drive: A Google Drive node receives the email data and its attachments. It's configured to upload these attachments to a specific folder in your Google Drive. The attachments are named dynamically based on their original filenames. Setup Steps To get this workflow up and running, follow these instructions: Step 1: Create Gmail and Google Drive Credentials in n8n In your n8n instance, click on Credentials in the left sidebar. Click New Credential. Search for and select "Gmail OAuth2 API" and follow the authentication steps with your Google account. Save it. Click New Credential again. Search for and select "Google Drive OAuth2 API" and follow the authentication steps with your Google account. Save it. Make note of the Credential Names (e.g., "My Gmail Account", "My Google Drive Account"). Step 2: Create a Destination Folder in Google Drive Go to your Google Drive (drive.google.com). Create a new folder where you want to save the email attachments (e.g., Email Attachments Archive). Copy the Folder ID from the URL (e.g., https://drive.google.com/drive/folders/YOUR_FOLDER_ID_HERE).

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,

Tagged with: , , , ,