This article provides a complete, practical walkthrough of the Code Schedule Import Scheduled n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:  
   Automating Daily Fundraising Data Capture with n8n and Piloterr
   
   Meta Description:  
   Learn how to use n8n and Piloterr to build an automated workflow that fetches the latest startup fundraising data—including Series A, B, and Seed rounds—and stores it directly in Google Sheets for real-time insights.
   
   Keywords:  
   n8n workflow, Piloterr API, fundraising automation, Crunchbase, startup funding, Series A fundraising, Seed rounds, Google Sheets automation, enrich company data, no-code automation, startup intelligence
   
   Third-Party APIs Used:
   
   1. Piloterr Crunchbase API  
      - Endpoint: /api/v2/crunchbase/funding_rounds  
      - Purpose: Fetches recent fundraising data of startups by investment type (Seed, Series A, Series B)
   
   2. Piloterr Crunchbase Company Info API  
      - Endpoint: /api/v2/crunchbase/company/info  
      - Purpose: Enriches company data with additional details like website, employee count, SEMrush traffic, and LinkedIn URL
   
   3. Google Sheets API via n8n's Google Sheets Integration  
      - Purpose: Appends or updates fundraising data in a Google Sheet with structured company and funding round information
   
   Article:
   
   Automating Startup Fundraising Reports Using n8n and Piloterr
   
   In the supercharged world of startups and venture capital, timing and access to fresh fundraising data is everything. Whether you're a journalist, investor, or sales professional prospecting for high-growth opportunities, tracking daily funding activity across multiple companies can be tedious and time-consuming—that is, unless it’s automated.
   
   With the power of n8n, a workflow automation tool, and Piloterr’s Crunchbase API, you can create a no-code solution that scrapes daily funding rounds and enriches them with company intelligence, all while keeping a living record in Google Sheets. Let’s break down how this powerful setup works and how it can streamline your startup monitoring process.
   
   🔁 The Goal
   
   This workflow is designed to run each morning at 8 a.m., pulling in the most recent funding rounds from Crunchbase announced in the previous 24 hours. It collects data across three primary funding stages: Seed, Series A, and Series B. After compilation, the data is enriched with key company metrics like location, traffic, employee count, and LinkedIn profile. The final dataset is automatically stored (or updated) in a connected Google Sheet for real-time access.
   
   🧰 Workflow Architecture Explained
   
   1. Scheduled Trigger  
   Everything starts with a scheduled node that triggers the full sequence each day. You can customize the execution time, but the current workflow uses 8 a.m. as the default.
   
   2. Fetching Daily Fundraising Data  
   Three HTTP Request nodes hit the Piloterr API, each targeting a different investment type—Seed, Series A, and Series B. For each call, the query parameter "days_since_announcement" is set to 1, ensuring only events within the last day are retrieved.
   
   3. Splitting Results  
   Since the API responses may include an array of fundraises, a Split Out node ensures each funding event is treated individually. This granular handling is essential for accurate enrichment and formatting downstream.
   
   4. Preparing Basic Data  
   A "Set" node is used to extract useful properties from each fundraising item. It captures elements such as:
      - Investment type
      - Date announced
      - Company name and permalink
      - Event link
      - Amount raised
   
   5. Enriching Company Profiles  
   Each company link is sent through another HTTP request to Piloterr’s /company/info endpoint, which fetches rich metadata from Crunchbase including:
      - Website URL
      - Total funding
      - SEMrush monthly traffic
      - LinkedIn URL (extracted from social network objects in a dedicated "Code" node)
      - Number of employees
      - Country of operation
      - Year founded
   
   6. Data Normalization  
   An additional “Set” node reshapes the enriched data to keep only selected fields that match the columns in the targeted Google Sheet.
   
   7. Merging Datasets  
   A “Merge” node combines the data from the fundraising API with the enrichment dataset, aligning them by position (ensuring each fundraise line item matches the enriched metadata correctly).
   
   8. Save to Google Sheets  
   The final data is appended or updated in a predefined Google Sheet. The workflow uses the unique event link as the matching column to avoid redundant entries.
   
   📊 Why This Is Powerful
   
   This workflow doesn’t just automate one task—it builds a dynamic fundraising intelligence tool. Here’s why it’s useful:
   - Tracks new fundraises daily without manual work
   - Enriches raw funding data with company details critical for analysis, outreach, or investment intelligence
   - Automatically deduplicates and updates existing entries in your spreadsheet
   - Highly customizable—tweak it to target specific geographies, funding stages, or publish alerts
   
   By maintaining this live dataset, users can act on funding insights before competitors even pull the latest Crunchbase report.
   
   🔧 What You Need
   
   To replicate this setup, you’ll need:
   - An n8n instance (self-hosted or cloud)
   - A Piloterr account and API key
   - An authenticated Google Sheets account in n8n
   - A predefined Google Sheet with the correct schema headers (the workflow manages column mappings)
   
   📝 Final Thoughts
   
   If you want to stay up to date on startup fundraising events without wasting hours scraping sites or pulling reports, this n8n + Piloterr stack is your solution. It's a case study in the power of no-code tools for real-time, data-driven workflows. With just one setup, you’ll have investor-grade insights delivered to a spreadsheet every single day.
   
   For the full guide and template workflow setup, visit:  
   https://lempire.notion.site/Get-recent-fundraising-in-Google-Sheets-dafbbda2635544b4925c4fb04abac8f5?pvs=74
   
   Start automating. Stay ahead.
   
   —  
   Written by Your AI Assistant 👨‍💻 powered by n8n and Piloterr

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.