SharePoint + Phantombuster, steady Instagram growth
Instagram growth sounds simple until you’re manually hunting accounts, copying profile URLs into a tool, and trying not to trip daily limits. One busy day turns into three. Then you “catch up” with a spike, and your account looks suspicious.
This is where Phantombuster Instagram growth automation helps most. Community managers feel the churn, but growth marketers and small brand owners get stuck in it too. The outcome is steady follow activity every hour, without needing you to babysit a CSV.
This workflow uses SharePoint as your source of truth, rotates Instagram session cookies, and runs Phantombuster agents on a schedule. You’ll see what it automates, what results to expect, and what to watch out for.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: SharePoint + Phantombuster, steady Instagram growth
flowchart LR
subgraph sg0["Schedule Flow"]
direction LR
n0@{ icon: "mdi:cog", form: "rounded", label: "Wait", pos: "b", h: 48 }
n1["<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/phantombuster.png' width='40' height='40' /></div><br/>Launch Agent"]
n2["<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/phantombuster.png' width='40' height='40' /></div><br/>Launch AC Agent"]
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/phantombuster.png' width='40' height='40' /></div><br/>Get Response"]
n4["<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/phantombuster.png' width='40' height='40' /></div><br/>Get Follower Collector"]
n5["<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/phantombuster.png' width='40' height='40' /></div><br/>Get Followers"]
n6@{ icon: "mdi:cog", form: "rounded", label: "Get List of Accounts", pos: "b", h: 48 }
n7["<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/phantombuster.png' width='40' height='40' /></div><br/>Get Autofollow Agent"]
n8@{ icon: "mdi:cog", form: "rounded", label: "Wait for result", pos: "b", h: 48 }
n9@{ icon: "mdi:swap-vertical", form: "rounded", label: "Set ENV Variables", pos: "b", h: 48 }
n10@{ icon: "mdi:play-circle", form: "rounded", label: "Schedule Trigger", pos: "b", h: 48 }
n11@{ icon: "mdi:brain", form: "rounded", label: "OpenAI Chat Model", pos: "b", h: 48 }
n12@{ icon: "mdi:cog", form: "rounded", label: "Get Available Session Cookies", pos: "b", h: 48 }
n13@{ icon: "mdi:cog", form: "rounded", label: "Extract Cookies", pos: "b", h: 48 }
n14@{ icon: "mdi:robot", form: "rounded", label: "Select Cookie", pos: "b", h: 48 }
n0 --> n5
n1 --> n0
n5 --> n7
n14 --> n9
n13 --> n14
n2 --> n8
n8 --> n3
n10 --> n12
n11 -.-> n14
n9 --> n4
n7 --> n2
n6 --> n1
n4 --> n6
n12 --> n13
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 n10 trigger
class n14 ai
class n11 aiModel
classDef customIcon fill:none,stroke:none
class n1,n2,n3,n4,n5,n7 customIcon
The Problem: Instagram growth breaks when it’s “manual but careful”
Following relevant accounts is still one of the most reliable ways to get on the radar of real people. The annoying part is doing it consistently. You start with a few seed profiles, open them one-by-one, scroll followers, follow a handful, and then try to remember where you left off. Miss a day and you feel behind. Overdo it and you get action blocks. Even if you use a growth tool, the setup often lives in random spreadsheets, outdated exports, or a teammate’s laptop. It’s brittle, and frankly, it gets messy fast.
None of these alone is the problem. Together, they are.
- Seed lists drift out of date, so you keep pulling followers from the same few accounts.
- Manual following forces you to choose between “consistent” and “safe,” because you can’t easily pace yourself hour by hour.
- Teams lose time tracking what was already processed, which leads to repeats and wasted follows.
- One login session is a single point of failure, so an expired cookie can stop growth without you noticing.
The Solution: SharePoint + Phantombuster automation that follows safely every hour
This workflow gives you a controlled, repeatable way to follow new, relevant Instagram profiles using Phantombuster, with SharePoint as the place you manage inputs. It starts on a Schedule Trigger that runs hourly, then pulls a text file of Instagram session cookies from a SharePoint folder. Those cookies get parsed, and the workflow selects a session to use (so you can rotate logins and avoid hammering one session all day). Next it downloads your seed list CSV from SharePoint, launches a Phantombuster “Follower Collector” run to fetch followers from each seed profile, and then passes a limited set of those followers into an Autofollow agent. Wait nodes pause between runs and poll until results are ready, which helps keep activity smooth instead of bursty.
The workflow begins with an hourly trigger and a cookie rotation decision. From there, it reads your SharePoint seed list, collects followers via Phantombuster, then follows a capped number per launch. Finally, it waits, checks run completion, and fetches the result data so you have a record of what happened.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you want steady outreach from 10 seed profiles. Manually, you might spend about 10 minutes per seed just to find fresh followers and follow a handful, which is roughly 100 minutes each time you do a “growth session.” With this workflow, you update one CSV in SharePoint (maybe 5 minutes), then it runs hourly on its own, following between 1 and 40 accounts per hour based on your limits. You’re no longer setting aside big blocks of time, and you stop getting the “oops, I overdid it” days.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Microsoft SharePoint to store cookies and seed CSVs.
- Phantombuster to collect followers and auto-follow.
- Phantombuster API key (get it from your Phantombuster account settings).
Skill level: Intermediate. You’ll connect credentials, edit a few environment variables, and confirm your SharePoint file formats.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
An hourly schedule kicks it off. n8n runs at a set minute each hour, so the activity stays smooth and predictable.
SharePoint provides the inputs. The workflow downloads instagram_session_cookies.txt (one cookie per line) and accounts_to_follow.csv (a profileUrl header plus one seed profile per row), so you can update growth targets without touching n8n.
Phantombuster does the heavy lifting. First, the follower collector agent fetches followers from your seed profiles (limited by your ENV settings). Then the autofollow agent follows a capped number per launch, with Wait nodes pausing and polling until each run completes.
Results are fetched after each run. Once Phantombuster signals completion, n8n pulls the result data so you can review what happened and spot failures quickly.
You can easily modify the seed source in SharePoint to Google Drive or Dropbox based on your needs. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Scheduled Trigger
Set when the workflow runs by configuring the time-based trigger that starts the automation.
- Add or open Scheduled Automation Trigger.
- Choose your desired schedule so the workflow runs automatically at your preferred frequency.
- Confirm Scheduled Automation Trigger connects to Fetch Session Cookies as the next step in the chain.
Step 2: Connect Microsoft SharePoint Sources
The workflow reads cookie and account data from SharePoint before processing.
- Open Fetch Session Cookies and connect it to your SharePoint file source that contains session cookies.
- Open Fetch Account Catalog and connect it to the SharePoint data source containing the account list.
- Ensure Fetch Session Cookies flows into Parse Cookie File, and Fetch Account Catalog flows into Start Agent Run.
Step 3: Parse Cookies and Configure the AI Session Chooser
The cookie file is parsed, then an AI agent selects a session to use.
- Open Parse Cookie File and verify it reads the cookie file output from Fetch Session Cookies.
- Open Choose Cookie Session to configure how the agent chooses a cookie session from the parsed data.
- Confirm the AI model connection: OpenAI Chat Engine is connected as the language model for Choose Cookie Session.
Step 4: Assign Environment Variables
Set up environment variables used by downstream PhantomBuster steps.
- Open Assign Environment Vars and add the fields needed by your PhantomBuster agents (e.g., session, API key, or target IDs).
- Confirm Choose Cookie Session outputs to Assign Environment Vars and then into Retrieve Follower Collector.
Step 5: Configure PhantomBuster Execution Chain
These nodes run the follower collection and autofollow sequence. There are multiple PhantomBuster nodes; configure them by function rather than one-by-one.
- Configure PhantomBuster credentials in all agent nodes: Retrieve Follower Collector, Start Agent Run, Retrieve Followers List, Load Autofollow Agent, Initiate AC Runner, and Fetch Result Data.
- Ensure the execution order follows the chain: Retrieve Follower Collector → Fetch Account Catalog → Start Agent Run → Pause Interval → Retrieve Followers List → Load Autofollow Agent → Initiate AC Runner → Await Result Signal → Fetch Result Data.
- Confirm all PhantomBuster nodes are set to the correct agent configurations in your PhantomBuster account.
Step 6: Configure Wait Nodes for Timing
These nodes introduce pauses and wait for completion signals to ensure each PhantomBuster run finishes before continuing.
- Open Pause Interval and set the delay that allows the initial PhantomBuster run to complete before fetching results.
- Open Await Result Signal and confirm it waits for the final agent to complete before triggering Fetch Result Data.
Step 7: Test and Activate Your Workflow
Run a manual test to verify the full automation before enabling it on a schedule.
- Click Execute Workflow and watch each node progress from Scheduled Automation Trigger through Fetch Result Data.
- Verify that Fetch Result Data returns follower results and that the PhantomBuster nodes complete successfully after the wait steps.
- Once the test is successful, toggle the workflow to Active so Scheduled Automation Trigger runs it on schedule.
Common Gotchas
- Microsoft SharePoint credentials can expire or need specific permissions. If things break, check your n8n credential status and SharePoint folder access first.
- If you’re using Wait nodes or external agent runs, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Phantombuster limits are real, and Instagram is touchy. Keep the follows between about 1 and 40 per hour like the workflow intends, and double-check your ENV variables before you “speed things up.”
Frequently Asked Questions
About 30–60 minutes if your SharePoint folder and Phantombuster account are ready.
No. You’ll mostly be connecting accounts and editing a few values like hourly limits and list locations.
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 a Phantombuster plan with API access (their Growth plan), which is the real requirement here.
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 you’ll swap the collection method. Replace the Phantombuster “Follower Collector” step with a Hashtag-to-Profiles style agent, then keep the same autofollow pacing. Most people also adjust the SharePoint CSV to store hashtags or campaign labels, and tighten the ENV limits at first to make sure targeting quality stays high.
Usually it’s an expired API key or a workspace permission issue inside Phantombuster. Regenerate the key, update it in n8n, and confirm your plan includes API access. If the workflow starts runs but never returns results, increase the Wait time and check the Phantombuster console for runs stuck in queue. Also check your Instagram session cookies file in SharePoint; a bad cookie can look like an API failure.
A lot, as long as you keep rate limits sane and your Phantombuster plan supports the volume. On n8n Cloud, your cap is mainly monthly executions; on self-hosted n8n, it’s mostly your server resources. In practice, this workflow is designed around steady hourly batches (1–40 follows per hour), not blasting through thousands in a day.
Often, yes, because this kind of flow needs waiting, polling, and branching when a run isn’t finished yet. n8n handles that without you paying extra for every conditional path, and self-hosting can remove execution anxiety completely. Zapier and Make are still great for simple “do X then Y” automations, but they can feel awkward when you need controlled pacing and long-running agent jobs. If you’re unsure, Talk to an automation expert and you’ll get a straight answer based on your volume and risk tolerance.
Set this up once, then let it run in the background. The workflow keeps your growth paced and consistent, so you can focus on content and conversations instead of another “follow session.”
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.
