Back to Catalog

Airtable batch update / insert rows (send faster + save API call requests)

Simon MayerhoferSimon Mayerhofer
487 views
2/3/2026
Official Page

This workflow allows you to batch update/insert Airtable rows in groups of 10, significantly reducing the number of API calls and increasing performance.

πŸš€ How It Works

  1. Copy the 3 Nodes
    Copy the three nodes inside the red note box into your workflow.

  2. Set Your Fields
    In the Set Fields node, define the fields you want to update.
    ➀ Only include fields that match column names in your Airtable table.
    ➀ Make sure the field names are spelled exactly as they appear in Airtable. ➀ Make sure the field type are correctly set. So numbers columns in Airtable need numbers type set as the field.

  3. Configure the Airtable Batch Node

    • Enter your Airtable Base ID The part with app... in the URL: airtable.com / app8pqOLeka1Cglwg / tblnXZOdy8VtkAAJD/...

    • Enter your Airtable Table ID The part with tbl... in the URL: airtable.com / app8pqOLeka1Cglwg / tblXXZOdy8VtkAAJD /...

    • Set Matching Fields (fieldsToMergeOn)
      Provide a string array that tells Airtable how to match existing rows. Examples:

      • Match by one field (e.g. TaskID):
        {{["TaskID"]}}
      • Match by multiple fields (e.g. firstname and lastname):
        {{["firstname", "lastname"]}}
    • Choose the Mode (mode field)
      Available options:

      • upsert: Update if a record exists, otherwise insert a new one
      • insert: Always insert as new records
      • update: Only update existing records (you must provide a field named id)

n8n Airtable Batch Update/Insert Workflow

This n8n workflow demonstrates an efficient way to perform batch updates or inserts into Airtable, significantly reducing API call requests compared to processing items individually. It's designed to handle a list of records, determine if each record should be updated or inserted, and then process them in optimized batches.

Description

The workflow streamlines the process of synchronizing data with Airtable by intelligently grouping records for batch operations. It takes a collection of items, identifies whether each item requires an update (based on a unique ID) or a new insert, and then executes these operations in batches to conserve API request limits and improve performance.

What it does

  1. Receives Data: Starts by receiving a collection of data items, typically from a preceding node or a manual trigger.
  2. Splits into Batches: Divides the incoming data into smaller, manageable batches for processing.
  3. Processes Each Item: For each item in a batch:
    • Determines Action: Uses a "Switch" node to check if the item has a unique airtableId.
    • Routes for Update or Insert:
      • If airtableId exists, the item is routed for an "Update" operation.
      • If airtableId does not exist, the item is routed for an "Insert" operation.
  4. Aggregates for Batch Operations:
    • Items marked for "Update" are collected into a single batch for a bulk update API call.
    • Items marked for "Insert" are collected into a single batch for a bulk insert API call.
  5. Executes Sub-workflows:
    • Triggers an "Execute Workflow" node for the "Update" batch, likely calling a sub-workflow specifically designed for batch updates in Airtable.
    • Triggers another "Execute Workflow" node for the "Insert" batch, likely calling a sub-workflow specifically designed for batch inserts in Airtable.
  6. Waits for Completion: After executing the sub-workflows, the main workflow waits for a short period.
  7. Aggregates Results: Combines the results from both the update and insert operations.
  8. Final Output: Provides a final consolidated output of the processed records.

Prerequisites/Requirements

  • n8n Instance: A running n8n instance.
  • Airtable Account: An Airtable account with a base and table configured where data will be updated or inserted.
  • Airtable Credentials: Configured Airtable credentials in your n8n instance.
  • Sub-workflows for Airtable Update/Insert: This workflow relies on two sub-workflows (not included in this JSON) that handle the actual batch update and batch insert operations for Airtable. These sub-workflows would typically accept an array of records and use the Airtable node to perform the respective batch operations.

Setup/Usage

  1. Import the workflow: Import the provided JSON into your n8n instance.
  2. Configure Sub-workflows: Ensure you have two sub-workflows named "Airtable Update" and "Airtable Insert" (or similar, matching the names in the "Execute Workflow" nodes) that are designed to handle batch operations for Airtable. These sub-workflows should:
    • Have an "Execute Workflow Trigger" node as their starting point.
    • Accept an array of records as input.
    • Use the Airtable node to perform batch updates or inserts.
  3. Connect Data Source: Connect a node to the "Loop Over Items" node that provides the data you wish to process. This could be a database query, a webhook, a CSV reader, etc.
  4. Define airtableId: Ensure your incoming data items have a property (e.g., airtableId) that uniquely identifies existing Airtable records for update operations. If this property is missing or null, the item will be treated as a new record for insertion.
  5. Activate the workflow: Once configured, activate the workflow to start processing data. You can manually trigger it or set up a trigger node (e.g., a Cron node, Webhook node) to run it automatically.

Related Templates

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

Automate Gmail responses with GPT and human-in-the-loop verification

Try It Out! This n8n template uses AI to automatically respond to your Gmail inbox by drafting response for your approval via email. How it works Gmail Trigger monitors your inbox for new emails AI Analysis determines if a response is needed based on your criteria Draft Generation creates contextually appropriate replies using your business information Human Approval sends you the draft for review before sending Auto-Send replies automatically once approved Setup Connect your Gmail account to the Gmail Trigger node Update the "Your Information" node with: Entity name and description Approval email address Resource guide (FAQs, policies, key info) Response guidelines (tone, style, formatting preferences) Configure your LLM provider (OpenAI, Claude, Gemini, etc.) with API credentials Test with a sample email Requirements n8n instance (self-hosted or cloud) Gmail account with API access LLM provider API key Need Help? Email Nick @ nick@tropicflare.com

Nick CanfieldBy Nick Canfield
88