Apify to Google Sheets, Instagram profiles logged
Copying Instagram profile details into a spreadsheet sounds simple until you’ve done it for 50 accounts, realized half the bios changed, and now your “research” is already outdated.
This is the kind of Apify Sheets logging automation that saves marketing teams hours, keeps agency owners from shipping messy lead lists, and gives founders a research system they can actually trust.
You’ll see how this n8n workflow pulls a list of usernames from Google Sheets, scrapes full public profiles through an Apify actor, logs clean rows into a second sheet, then flags each username as done.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Apify to Google Sheets, Instagram profiles logged
flowchart LR
subgraph sg0["Schedule Flow"]
direction LR
n0@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
n1@{ icon: "mdi:cog", form: "rounded", label: "Aggregate", pos: "b", h: 48 }
n2@{ icon: "mdi:database", form: "rounded", label: "get usernames", pos: "b", h: 48 }
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>call apify actor"]
n4@{ icon: "mdi:cog", form: "rounded", label: "Limit", pos: "b", h: 48 }
n5@{ icon: "mdi:database", form: "rounded", label: "Append full profiles on sheet", pos: "b", h: 48 }
n6@{ icon: "mdi:database", form: "rounded", label: "mark user name as scraped", pos: "b", h: 48 }
n4 --> n1
n1 --> n3
n2 --> n4
n0 --> n2
n3 --> n5
n3 --> n6
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n2,n5,n6 database
class n3 api
classDef customIcon fill:none,stroke:none
class n3 customIcon
The Problem: Instagram research gets messy fast
Instagram profile research usually starts with good intentions. Then it turns into tabs everywhere, inconsistent notes, and a spreadsheet full of “close enough” data that no one wants to own. You copy follower counts that change tomorrow, paste bios with broken line breaks, and miss obvious context like category, external links, or a new name. Worse, manual work encourages shortcuts, so you stop updating the sheet and it slowly becomes a museum of old profiles. Honestly, the mental load is the killer: you can’t scale research when each profile requires attention like a tiny one-off project.
The friction compounds. Here’s where it breaks down most often.
- Researchers spend about 5 minutes per profile just collecting the basics, and that time doubles when they need to double-check accuracy.
- Teams end up with mismatched formats because one person pastes emojis, another strips them, and now sorting and filtering becomes unreliable.
- It’s easy to scrape the same username twice, which clutters your dataset and makes reporting feel untrustworthy.
- When a stakeholder asks, “Is this current?”, the honest answer is usually “not really,” because there’s no consistent refresh cycle.
The Solution: Scheduled Apify scrapes that log clean rows
This workflow turns Instagram profile research into a repeatable system. On a schedule (every few minutes, or whatever cadence you choose), n8n opens your Google Sheet and pulls a queue of Instagram usernames from a tab called Usernames. It grabs up to 20 at a time so you don’t overload your scraping or your sheet, then bundles those usernames into a batch request. Next, it calls your custom Apify actor to scrape full public profile data, which comes back as structured results instead of random copy-paste text. Finally, the workflow appends cleaned profile records into a second tab (called fullprofiles) and marks the source usernames as scraped = TRUE so they don’t get processed again.
The workflow starts with a timed trigger and a Google Sheets read. Then Apify handles the actual Instagram profile scrape in one call per batch. Google Sheets gets two writes at the end: one to log the profile rows, and one to flag the usernames as completed.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you’re tracking 200 Instagram accounts for influencer outreach. Manually, even 5 minutes per profile is about 16 hours of busywork, and that’s before anyone formats the sheet. With this workflow, you can process 20 usernames per run; if it runs every 10 minutes during a typical workday, you refresh about 900 profiles’ worth of capacity without touching a browser. Realistically, you’ll finish your 200 in an afternoon, and then you’re just keeping the dataset current.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Google Sheets for the username queue and output table
- Apify actor to scrape public Instagram profiles
- Apify API token (get it from your Apify account settings)
Skill level: Beginner. You’ll connect Google Sheets, paste an API token, and confirm your sheet columns match the workflow.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
A scheduled trigger runs the workflow. You choose the cadence (every few minutes is common), which means research stays fresh without anyone remembering to “update the sheet.”
Usernames are pulled from Google Sheets. n8n reads the Usernames tab, then limits the run to 20 records so you get predictable batches and fewer surprises.
Those usernames are sent to Apify for scraping. The workflow aggregates the batch and calls the Apify actor through an HTTP request, then receives structured profile data back (names, bios, follower counts, and more depending on your actor’s output).
Clean rows are logged and the queue is updated. Results are appended to the fullprofiles sheet, and the original usernames are marked as scraped so they don’t get reprocessed next time.
You can easily modify the schedule to run hourly instead of every few minutes based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Schedule Trigger
Set the workflow to run automatically on a recurring schedule.
- Add and open Scheduled Automation Trigger.
- Under Rule → Interval, set Field to
minutesto match the existing schedule rule. - Connect Scheduled Automation Trigger to Retrieve Usernames Sheet.
Step 2: Connect Google Sheets
Pull usernames from your spreadsheet and prepare the workflow’s Google Sheets connections.
- Open Retrieve Usernames Sheet and set Document to
[YOUR_ID]and Sheet toUsernames(valuegid=0). - In Retrieve Usernames Sheet, keep the filter on scraped via Filters → lookupColumn set to
scraped. - Credential Required: Connect your googleSheetsOAuth2Api credentials for Retrieve Usernames Sheet.
- Credential Required: Connect your googleSheetsOAuth2Api credentials for Append Profile Records and Flag Usernames Processed.
Step 3: Set Up Processing Nodes
Limit batch size and aggregate usernames into a single payload for the API call.
- Open Cap Item Count and set Max Items to
20. - Open Combine Usernames and ensure Fields to Aggregate includes fieldToAggregate set to
username. - Connect Retrieve Usernames Sheet → Cap Item Count → Combine Usernames.
username, Combine Usernames will output empty data and the API call will fail.Step 4: Configure Output and API Actions
Send usernames to the scraping API and write results back to Google Sheets.
- Open Run Profile Scrape API and set URL to
https://api.apify.com/v2/acts/mohamedgb00714~instagram-full-profile-scraper/run-sync-get-dataset-items?token=[CONFIGURE_YOUR_TOKEN]. - In Run Profile Scrape API, set Send Body to
true, Body Content Type tojson, and JSON Body to={ "instagramUsernames": [ {{ $json.username.map(item => `"${item}"`) }} ] }. - Open Append Profile Records and set Operation to
append, Document to[YOUR_ID], and Sheet tofullprofiles(value458127000). - Open Flag Usernames Processed and set Operation to
update, Sheet toUsernames(valuegid=0), and map Columns with scraped set toTRUEand username set to={{ $json.username }}. - Connect Combine Usernames → Run Profile Scrape API.
- Run Profile Scrape API outputs to both Append Profile Records and Flag Usernames Processed in parallel.
[CONFIGURE_YOUR_TOKEN] with your valid Apify token or the API will return authorization errors.Step 5: Test and Activate Your Workflow
Validate that usernames are scraped, appended, and flagged correctly before running on schedule.
- Click Execute Workflow to run the flow manually from Scheduled Automation Trigger.
- Confirm Append Profile Records adds new rows to the
fullprofilessheet and Flag Usernames Processed marksscrapedasTRUEfor those usernames. - If results are correct, switch the workflow to Active to enable scheduled runs.
Common Gotchas
- Google Sheets credentials can expire or need specific permissions. If things break, check the connected Google account and the n8n credential status first.
- If your Apify actor takes longer on some batches, processing times vary. Increase the schedule interval (or add wait time) if you see partial results or empty responses getting appended.
- Apify API tokens are easy to paste wrong, and a single missing character will cause silent failures. Re-copy the token from Apify, then confirm the HTTP Request node is using the correct header or query field.
Frequently Asked Questions
About 30 minutes if your sheet and Apify token are ready.
No. You’ll mostly connect Google Sheets and paste your Apify API token into the HTTP request node.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Apify usage, which depends on the actor and how often you run it.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, but only within what your Apify actor can legally and technically return. You can swap the fields you store by adjusting what you send in the “Run Profile Scrape API” HTTP Request and by mapping columns in “Append Profile Records.” Common customizations include adding extra output columns (like website URL), changing the batch size from 20 to a lower number, and running the schedule hourly instead of every few minutes.
Most of the time it’s an invalid or expired Apify API token, so regenerate it in Apify and update the HTTP Request node. It can also be a wrong actor endpoint, or the actor expects a slightly different input format than what the workflow is sending. If it fails only on bigger runs, you may be hitting rate limits or actor capacity, so reduce the batch size and slow down the schedule. Also check the last execution output in n8n; the HTTP response body usually tells you what Apify didn’t like.
In each scheduled run, this workflow processes up to 20 usernames, and you can scale that by running it more often or increasing the cap. On n8n Cloud, your monthly execution limit depends on your plan; if you self-host, there’s no execution cap, but your server and Apify actor throughput become the real limits.
Often, yes, because this workflow relies on batching, branching, and sheet updates that get expensive or awkward in Zapier and Make. n8n makes it easier to read a queue, process a batch, write results, then mark items as done in the same run. You also get the self-hosting option, which matters when you’re running frequent schedules. That said, if you only need a tiny “one username in, one row out” flow, Zapier or Make can feel simpler. Talk to an automation expert if you want help choosing.
Once this is running, your spreadsheet stops being “best effort” and starts being reliable. The workflow handles the repetitive parts, so you can spend your time making decisions from the data instead of collecting it.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
