KonbiniAPI

Track Follower Changes in Make

Polling stands in for the webhook these platforms do not offer.

Public follower tracking is a polling job: read the same profile regularly, keep the previous value, and compare the two. That is a scenario Make runs well — a schedule, a lookup, a stored value, and a filter.

Before you start
  1. 1A KonbiniAPI accountThe free plan includes 100 credits, which is enough to run this a few times.
  2. 2Make connectedOAuth or API key.
  3. 3A real targetA public account, post, or keyword to run it against — the placeholders below are not live values.

Wire it up.

Each step below is a node or action in Make. The KonbiniAPI step is an MCP tool call, and it costs the same credits as the matching REST call.

Good for

  • Alert the team when a competitor’s audience moves sharply in either direction
  • Catch the follower spike that signals something went viral
  • Track a creator’s audience across the length of a campaign
  • Keep a long-term follower history for any public account
Workflow steps

Poll, compare against the stored baseline, write the new value back, and notify only on a material change. The data store is the whole mechanism — without it, every run looks identical.

  1. 1ScheduleDaily suits most accounts. Hourly is available if you are watching something during a launch.
  2. 2MCP Client module — profile tool for the selected platformRead the follower count using the matching TikTok, Instagram, X, or LinkedIn profile tool.
  3. 3Data store — get and setRead the previous value, compute the delta, then write the new one back so the next run has a baseline.
  4. 4FilterLet the scenario continue only when the delta clears your threshold. Without this you get a notification every single run.
  5. 5NotifySlack, email, or a webhook into whatever already pages the right person.

Run this in Make.

One API key works for MCP and the REST API. The free plan includes 100 credits and no credit card.