KonbiniAPI

Track Follower Changes in Pipedream

Detect the movement, decide in code whether it is worth an alert.

This workflow detects follower changes by reading the same public profile on a schedule and remembering the last value. The part worth thinking about is the threshold: a flat percentage alerts constantly on small accounts and never on large ones. In Pipedream that logic is a code step rather than a filter you fight with.

Before you start
  1. 1A KonbiniAPI accountThe free plan includes 100 credits, which is enough to run this a few times.
  2. 2Pipedream 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 Pipedream. The KonbiniAPI step is an MCP tool call, and it costs the same credits as the matching REST call.

Good for

  • Alert when a competitor’s audience moves more than its own normal range
  • Catch a follower spike early enough to look at what caused it
  • Track campaign-period audience growth for reporting
  • Keep a durable follower history in your own database
Workflow steps

Poll, compare against stored state, apply your own threshold logic in code, then alert. Pipedream’s data store holds the baseline between runs.

  1. 1Schedule triggerDaily for most accounts, hourly when something is actively happening.
  2. 2MCP tool call — profile tool for the selected platformRead the follower count using the matching TikTok, Instagram, X, or LinkedIn profile tool.
  3. 3Data store — read and writeFetch the previous reading, compute the change, and store the new value for the next run.
  4. 4Code step — thresholdDecide what counts as notable for this specific account. Scaling the threshold to the account’s own size is why this is code and not a filter.
  5. 5NotifySend to Slack or email only when the code step says it matters.

Run this in Pipedream.

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