HumationHuman + Automation
Back to Catalog

Scrape TikTok profile & transcript with Dumpling AI and save to Google Sheets

YangYang
2392 views
2/3/2026
automationwebhookdata-exportfile-generationcsv
Official Page

Who is this for?

This workflow is built for marketers, researchers, and content analysts who need to monitor TikTok content, analyze user data, or track trends across influencers. It's useful for agencies that manage creators or want to keep an organized record of profile performance and video content for reporting or outreach.

What problem is this workflow solving?

Instead of manually checking TikTok profiles or watching videos to understand performance or content, this workflow automates everything. It extracts both profile statistics and full video transcripts, then logs them in Google Sheets for easy access, filtering, and segmentation.

What this workflow does

The automation watches for new TikTok video URLs added to a Google Sheet. When a new row is detected:

  1. It extracts the username from the URL.
  2. Sends the username to Dumpling AI to get full profile data (followers, likes, videos).
  3. Sends the video URL to Dumpling AI to extract the full transcript.
  4. Appends all this information back into the same sheet.

Everything happens automatically after a new URL is added to the sheet.

Setup

  1. Google Sheets Trigger

    • Connect your Google account and select the spreadsheet where TikTok links will be added.
    • The workflow will trigger on each new row.
    • Example sheet column: USERNAME Video

  2. Extract Username

    • This Set node uses RegEx to extract the username (handle) from the TikTok video URL.
    • No need to change anything unless TikTok URL formatting changes.

  3. Dumpling AI Profile Scraper

    • Go to Dumpling AI
    • Sign in and retrieve your API key
    • Create an agent using the get-tiktok-profile endpoint
    • Paste your API key into the httpHeaderAuth field in n8n

  4. Dumpling AI Transcript Scraper

    • Also uses Dumpling AI
    • Make sure the endpoint get-tiktok-transcript is enabled in your Dumpling account
    • Connect using the same API key

  5. Save to Google Sheets

    • The final node appends data back to your original Google Sheet
    • Required columns: USERNAME Video, Username, Follower count, Following Count, heart count, Video Count, Transcript

How to customize this workflow to your needs

  • Add a filter node to only save profiles with a minimum follower count
  • Add sentiment analysis for the transcript using OpenAI
  • Connect Airtable or Notion instead of Google Sheets
  • Use GPT to summarize or classify transcripts for research

⚠️ Notes

  • Requires a Dumpling AI account and API key
  • Make sure Google Sheets API is connected and has the correct permissions
  • TikTok usernames must start with @ for RegEx to work

n8n Workflow: Scrape TikTok Profile and Transcript with Dumpling AI, Save to Google Sheets

This n8n workflow automates the process of scraping TikTok profile data and video transcripts using a custom API (likely "Dumpling AI") and then saving the extracted information into a Google Sheet. It's designed to streamline data collection from TikTok for analysis or record-keeping.

What it does

  1. Triggers on Google Sheet Row Addition: The workflow starts whenever a new row is added to a specified Google Sheet. This new row is expected to contain the TikTok profile URL to be processed.
  2. Scrapes TikTok Profile Data: It makes an HTTP request to an external API (referred to as "Dumpling AI" in the directory name, but the JSON only shows a generic HTTP Request node) to scrape data from the provided TikTok profile URL.
  3. Extracts Video Transcripts: The same API call is used to obtain the transcripts of videos associated with the TikTok profile.
  4. Formats Data: An "Edit Fields (Set)" node is used to transform and prepare the scraped data into a structured format suitable for storage.
  5. Saves to Google Sheets: Finally, the processed TikTok profile data and transcripts are appended as a new row to another specified Google Sheet.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance (self-hosted or cloud).
  • Google Account: A Google account with access to Google Sheets.
  • Google Sheets Credentials: Configured Google Sheets OAuth2 or API Key credentials in n8n.
  • External API (e.g., Dumpling AI): Access to an external API capable of scraping TikTok profiles and extracting video transcripts. This API will need to be configured within the "HTTP Request" node.

Setup/Usage

  1. Import the Workflow: Import the provided JSON into your n8n instance.
  2. Configure Google Sheets Trigger:
    • Select your Google Sheets credential.
    • Specify the Spreadsheet ID and Sheet Name that will act as the trigger (where you add TikTok profile URLs).
    • Set the "Operation" to "Row Added".
  3. Configure HTTP Request Node:
    • Update the "URL" field to point to your TikTok scraping API endpoint (e.g., "Dumpling AI").
    • Configure the "Method" (likely GET or POST) and any necessary "Headers" (e.g., API keys) or "Query Parameters" to pass the TikTok profile URL from the Google Sheets trigger.
    • Map the TikTok profile URL from the Google Sheets trigger to the appropriate parameter for your API.
  4. Configure Edit Fields (Set) Node:
    • Adjust the fields to extract and rename the data received from the HTTP Request node as needed. This ensures the data is in the correct format before being written to Google Sheets.
  5. Configure Google Sheets Node:
    • Select your Google Sheets credential.
    • Specify the Spreadsheet ID and Sheet Name where the scraped data should be saved.
    • Set the "Operation" to "Append Row".
    • Map the output fields from the "Edit Fields (Set)" node to the corresponding columns in your target Google Sheet.
  6. Activate the Workflow: Once configured, activate the workflow. It will now automatically process new rows added to your trigger Google Sheet.

A "Sticky Note" node is included in the workflow, likely for documentation or instructions within the n8n canvas itself.

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.

Matt@VeraisonLabsBy Matt@VeraisonLabs
208

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

RapiwaBy Rapiwa
183

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.

Rahul JoshiBy Rahul Joshi
31