Integrate Instagram follower changes via API
Monitor public creator or brand accounts up to 150,000 followers. Reuse one task from your API and receive confirmed new and lost follower rows.
Input
Output fields
Sign up on Apify or log in
The Instagram Follower Changes Tracker & Monitor Actor is ready to run with the inputs already set for "Integrate Instagram follower changes via API". Sign up or log in and you'll land in Apify Console with a copy of this exact task.
Start the "Integrate Instagram follower changes via API" task
The Instagram Follower Changes Tracker & Monitor Actor will start running based on the input automatically. You can also change all the input fields, like instagram accounts to track and track new followers & unfollowers, to match your specific use case.
Receive the "Integrate Instagram follower changes via API" output
Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as tracked account, change type, list, and more.
Integrate into your workflow
The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also run the "Integrate Instagram follower changes via API" task via API.
Integrate "Integrate Instagram follower changes via API" into your workflow
Connect "Integrate Instagram follower changes via API" with 100+ integrations, or run it via API or MCP.
Webhook
n8n
Make
Zapier
Airbyte
Keboola
IFTTT
Hubspot
GDrive
Gmail
Apify MCP
GitHub
Slack
LangChain
LlamaIndex
Flowise
Pinecone
OpenAI
Mastra
Clay
Copy this task, replace the demo handle with your accounts, and call your copied task through the Apify API on your own cadence. From the third call on, the dataset rows hold confirmed new and lost followers.
The run response gives the default dataset ID; fetch its items for the rows. The RUN_SUMMARY record in the run's key-value store holds counts, stage, cost and the next action.
The first call writes tracked rows, one per current follower, and saves the baseline. The second call verifies the list, and from the third call on you receive confirmed new and lost rows.
Yes. Use an Apify Schedule for a fixed cadence, or an Actor webhook to send each completed run to your own system. Each observation is billed separately.
Yes, on a paid plan. Add several public usernames to the copied task; every row carries target_username so you can tell the accounts apart.