Automate face swapping for GIFs with Fal.run AI and Google Services
This workflow allows you to automatically swap faces in animated GIFs using AI, without writing a single line of code.
By simply inserting the URL of a face image and a GIF into a Google Sheet, the automation takes care of everything: it sends the data to AI platform, monitors the processing status, retrieves the final face-swapped GIF, uploads it to Google Drive, and updates the Google Sheet with the result.
This solution is perfect for content creators, marketers, or developers looking to integrate AI-powered GIF editing into their workflows in a fast and scalable way.
Whether used manually or on a scheduled basis, the workflow turns a tedious creative task into a fully automated pipeline.
This workflow automates GIF face-swapping by integrating Google Sheets for input/output and Fal.run for AI processing, ensuring seamless execution via scheduled or manual triggers.
Example
Face image:

Gif Image:

Result:

How It Works
-
Trigger:
- The workflow can be triggered manually ("When clicking ‘Test workflow’") or automatically via a scheduled trigger ("Schedule Trigger") set to run at intervals (e.g., every 5 minutes).
-
Data Retrieval:
- The "Google Sheets" node fetches data from a predefined Google Sheet, which includes two columns:
FACE IMAGE: URL of the face image to swap.GIF IMAGE: URL of the target GIF.
- The "Google Sheets" node fetches data from a predefined Google Sheet, which includes two columns:
-
API Request:
- The "Set data" node formats the retrieved URLs into variables (
face_imageandgif_image). - The "Create Image" node sends a POST request to the Fal.run API (
easel-gifswapendpoint) with these URLs to initiate the face-swapping process. The API returns arequest_id.
- The "Set data" node formats the retrieved URLs into variables (
-
Status Check:
- The "Wait 60 sec." node pauses execution for 60 seconds to allow processing time.
- The "Get status" node queries the Fal.run API using the
request_idto check if the task isCOMPLETED. - If completed, the "Get Url image" node retrieves the final GIF URL.
-
Output Handling:
- The "Upload Image" node saves the resulting GIF to Google Drive.
- The "Update result" node writes the output GIF URL back to the Google Sheet under the
RESULTcolumn.
Set Up Steps
-
Prepare Google Sheet:
- Create a Google Sheet with columns:
FACE IMAGE,GIF IMAGE, andRESULT. - Populate the first two columns with image URLs. Leave
RESULTempty for the workflow to fill.
- Create a Google Sheet with columns:
-
Configure API Key:
- Sign up to obtain an API key.
- In the "Create Image" node, set HTTP header authentication:
- Name:
Authorization - Value:
Key YOURAPIKEY
- Name:
-
Schedule Execution:
- Link the "Schedule Trigger" node to run periodically (e.g., every 5 minutes) or trigger manually for testing.
-
Test and Deploy:
- Run the workflow to verify face-swapping functionality.
- Monitor the Google Sheet for the
RESULTcolumn updates with the processed GIF URL.
Need help customizing?
Contact me for consulting and support or add me on Linkedin.
Automate Face Swapping for GIFs with Google Services
This n8n workflow provides a framework for automating tasks that involve Google Sheets, Google Drive, and making HTTP requests to external services. While the specific logic for "face swapping for GIFs with Falrun AI" is not explicitly defined in the provided JSON, this workflow is structured to integrate with such a service. It allows for manual or scheduled initiation, conditional processing, data manipulation, and interaction with Google's cloud storage and spreadsheet services.
What it does
This workflow is a foundational template that demonstrates how to:
- Trigger the workflow: It can be initiated manually or on a predefined schedule.
- Interact with Google Sheets: Read or write data to a Google Sheet.
- Make HTTP Requests: Send requests to external APIs (e.g., a Falrun AI face-swapping service).
- Process data conditionally: Use an 'If' node to route data based on specific criteria.
- Transform and set data: Manipulate data fields using the 'Edit Fields (Set)' node.
- Interact with Google Drive: Store or retrieve files from Google Drive.
- Introduce delays: Use a 'Wait' node to pause execution for a specified duration.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n instance: A running n8n instance to import and execute the workflow.
- Google Account: For Google Sheets and Google Drive integration, you will need a Google account with appropriate permissions and n8n credentials configured for Google OAuth.
- External API (e.g., Falrun AI): If you intend to integrate with a specific face-swapping service, you will need access to its API and any necessary API keys or authentication details for the 'HTTP Request' node.
Setup/Usage
- Import the workflow:
- Copy the provided JSON code.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the copied JSON.
- Click "Import".
- Configure Credentials:
- For the "Google Sheets" and "Google Drive" nodes, you will need to set up Google OAuth2 credentials. Follow the n8n documentation for Google OAuth Single Service Account to create and connect your Google account.
- For the "HTTP Request" node, configure any necessary authentication (e.g., API keys, bearer tokens) required by the external service you are calling.
- Customize Nodes:
- Google Sheets (Node 18): Configure the spreadsheet ID, sheet name, and operation (e.g.,
read,append,update) as per your requirements. - HTTP Request (Node 19): Define the URL, method (e.g.,
POST), headers (e.g.,Authorization), and body (e.g., containing image URLs or other data for the face-swapping service). - If (Node 20): Set up the conditions to filter or route data based on the output of previous nodes.
- Edit Fields (Set) (Node 38): Add or modify fields in the incoming data.
- Google Drive (Node 58): Configure the operation (e.g.,
upload,download), file path, and folder ID. - Wait (Node 514): Adjust the duration of the pause if needed.
- Schedule Trigger (Node 839): If you want the workflow to run automatically, configure the schedule (e.g., daily, hourly).
- Google Sheets (Node 18): Configure the spreadsheet ID, sheet name, and operation (e.g.,
- Activate the Workflow:
- Once configured, save the workflow.
- Toggle the "Active" switch in the top right corner to enable it.
- Execute:
- You can manually execute the workflow by clicking "Execute Workflow" with the "Manual Trigger" node (Node 838) enabled.
- If the "Schedule Trigger" node (Node 839) is enabled, the workflow will run automatically according to its defined schedule.
Related Templates
Two-way property repair management system with Google Sheets & Drive
This workflow automates the repair request process between tenants and building managers, keeping all updates organized in a single spreadsheet. It is composed of two coordinated workflows, as two separate triggers are required — one for new repair submissions and another for repair updates. A Unique Unit ID that corresponds to individual units is attributed to each request, and timestamps are used to coordinate repair updates with specific requests. General use cases include: Property managers who manage multiple buildings or units. Building owners looking to centralize tenant repair communication. Automation builders who want to learn multi-trigger workflow design in n8n. --- ⚙️ How It Works Workflow 1 – New Repair Requests Behind the Scenes: A tenant fills out a Google Form (“Repair Request Form”), which automatically adds a new row to a linked Google Sheet. Steps: Trigger: Google Sheets rowAdded – runs when a new form entry appears. Extract & Format: Collects all relevant form data (address, unit, urgency, contacts). Generate Unit ID: Creates a standardized identifier (e.g., BUILDING-UNIT) for tracking. Email Notification: Sends the building manager a formatted email summarizing the repair details and including a link to a Repair Update Form (which activates Workflow 2). --- Workflow 2 – Repair Updates Behind the Scenes:\ Triggered when the building manager submits a follow-up form (“Repair Update Form”). Steps: Lookup by UUID: Uses the Unit ID from Workflow 1 to find the existing row in the Google Sheet. Conditional Logic: If photos are uploaded: Saves each image to a Google Drive folder, renames files consistently, and adds URLs to the sheet. If no photos: Skips the upload step and processes textual updates only. Merge & Update: Combines new data with existing repair info in the same spreadsheet row — enabling a full repair history in one place. --- 🧩 Requirements Google Account (for Forms, Sheets, and Drive) Gmail/email node connected for sending notifications n8n credentials configured for Google API access --- ⚡ Setup Instructions (see more detail in workflow) Import both workflows into n8n, then copy one into a second workflow. Change manual trigger in workflow 2 to a n8n Form node. Connect Google credentials to all nodes. Update spreadsheet and folder IDs in the corresponding nodes. Customize email text, sender name, and form links for your organization. Test each workflow with a sample repair request and a repair update submission. --- 🛠️ Customization Ideas Add Slack or Telegram notifications for urgent repairs. Auto-create folders per building or unit for photo uploads. Generate monthly repair summaries using Google Sheets triggers. Add an AI node to create summaries/extract relevant repair data from repair request that include long submissions.
Send WooCommerce cross-sell offers to customers via WhatsApp using Rapiwa API
Who Is This For? This n8n workflow enables automated cross-selling by identifying each WooCommerce customer's most frequently purchased product, finding a related product to recommend, and sending a personalized WhatsApp message using the Rapiwa API. It also verifies whether the user's number is WhatsApp-enabled before sending, and logs both successful and unsuccessful attempts to Google Sheets for tracking. What This Workflow Does Retrieves all paying customers from your WooCommerce store Identifies each customer's most purchased product Finds the latest product in the same category as their most purchased item Cleans and verifies customer phone numbers for WhatsApp compatibility Sends personalized WhatsApp messages with product recommendations Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Customer Segmentation: Automatically identifies paying customers from your WooCommerce store Product Analysis: Determines each customer's most purchased product Smart Recommendations: Finds the latest products in the same category as customer favorites WhatsApp Integration: Uses Rapiwa API for message delivery Phone Number Validation: Verifies WhatsApp numbers before sending messages Dual Logging System: Tracks both successful and failed message attempts in Google Sheets Rate Limiting: Uses batching and wait nodes to prevent API overload Personalized Messaging: Includes customer name and product details in messages Requirements WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) How to Use — Step-by-Step Setup Credentials Setup WooCommerce API: Configure WooCommerce API credentials in n8n (e.g., "WooCommerce (get customer)" and "WooCommerce (get customer data)") Rapiwa Bearer Auth: Create an HTTP Bearer credential with your Rapiwa API token Google Sheets OAuth2: Set up OAuth2 credentials for Google Sheets access Configure Google Sheets Ensure your sheet has the required columns as specified in the Google Sheet Column Structure section Verify Code Nodes Code (get paying_customer): Filters customers to include only those who have made purchases Get most buy product id & Clear Number: Identifies the most purchased product and cleans phone numbers Configure HTTP Request Nodes Get customer data: Verify the WooCommerce API endpoint for retrieving customer orders Get specific product data: Verify the WooCommerce API endpoint for product details Get specific product recommend latest product: Verify the WooCommerce API endpoint for finding latest products by category Check valid WhatsApp number Using Rapiwa: Verify the Rapiwa endpoint for WhatsApp number validation Rapiwa Sender: Verify the Rapiwa endpoint for sending messages Google Sheet Required Columns You’ll need two Google Sheets (or two tabs in one spreadsheet): A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: Both must have the following headers (match exactly): | name | number | email | address1 | price | suk | title | product link | validity | staus | | ---------- | ------------- | ----------------------------------------------- | ----------- | ----- | --- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur dohs | 850 | | Sharp Most Demanding Hoodie x Nike | https://yourshopdomain/p-img-nike | verified | sent | Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Product Availability: The workflow recommends the latest product in a category, but doesn't check if it's in stock. Consider adding stock status verification. Testing: Always test with a small batch before running the workflow on your entire customer list. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen
Track SDK documentation drift with GitHub, Notion, Google Sheets, and Slack
📊 Description Automatically track SDK releases from GitHub, compare documentation freshness in Notion, and send Slack alerts when docs lag behind. This workflow ensures documentation stays in sync with releases, improves visibility, and reduces version drift across teams. 🚀📚💬 What This Template Does Step 1: Listens to GitHub repository events to detect new SDK releases. 🧩 Step 2: Fetches release metadata including version, tag, and publish date. 📦 Step 3: Logs release data into Google Sheets for record-keeping and analysis. 📊 Step 4: Retrieves FAQ or documentation data from Notion. 📚 Step 5: Merges GitHub and Notion data to calculate documentation drift. 🔍 Step 6: Flags SDKs whose documentation is over 30 days out of date. ⚠️ Step 7: Sends detailed Slack alerts to notify responsible teams. 🔔 Key Benefits ✅ Keeps SDK documentation aligned with product releases ✅ Prevents outdated information from reaching users ✅ Provides centralized release tracking in Google Sheets ✅ Sends real-time Slack alerts for overdue updates ✅ Strengthens DevRel and developer experience operations Features GitHub release trigger for real-time monitoring Google Sheets logging for tracking and auditing Notion database integration for documentation comparison Automated drift calculation (days since last update) Slack notifications for overdue documentation Requirements GitHub OAuth2 credentials Notion API credentials Google Sheets OAuth2 credentials Slack Bot token with chat:write permissions Target Audience Developer Relations (DevRel) and SDK engineering teams Product documentation and technical writing teams Project managers tracking SDK and doc release parity Step-by-Step Setup Instructions Connect your GitHub account and select your SDK repository. Replace YOURGOOGLESHEETID and YOURSHEET_GID with your tracking spreadsheet. Add your Notion FAQ database ID. Configure your Slack channel ID for alerts. Run once manually to validate setup, then enable automation.