Daily X follower and engagement tracker

By General Input

Every weekday at 9am, log follower counts and engagement on the latest 10 posts for your handle and your competitors into a Google Sheet so you can chart growth over time.

Integrations

  • TwitterAPI.io
  • Google Sheets

Type

Deterministic Code

Categories

  • Marketing
  • Operations

Build a deterministic code workflow (no LLM step) that logs daily X (Twitter) KPIs for my handle and a configurable list of competitors into a Google Sheet so I can chart growth over time.

Trigger: cron, every weekday (Mon-Fri) at 9:00am in the workspace timezone.

Inputs (configurable at the top of the workflow): a list of X handles (mine plus 5 to 10 competitors), the target Google Sheet spreadsheetId, and the target sheet/tab name.

For each handle in the list, do the following in order:

1. Call TwitterAPI.io "Get User Info" with the handle to read followers, following, statusesCount, and isBlueVerified from the UserInfo response.

2. Call TwitterAPI.io "Get User Last Tweets" for the same handle to fetch the most recent 10 tweets. Sum likeCount, retweetCount, replyCount, and viewCount across that batch of (up to) 10 tweets. If fewer than 10 tweets are returned, sum across whatever was returned and proceed.

3. Append one row to the Google Sheet via the Google Sheets "Append Values" operation with these columns, in this order: date (YYYY-MM-DD in the workspace timezone), handle, followers, following, tweets_total (statusesCount), likes_sum_last10, retweets_sum_last10, replies_sum_last10, views_sum_last10.

Process handles sequentially (small list, no need to parallelize). Use valueInputOption USER_ENTERED so the date column is interpreted as a real date by Sheets. If a handle fails (404, unavailable account, rate limit), log the failure and continue with the next handle rather than aborting the whole run.

Output expectations: one new row per handle per run, appended to the existing log. The sheet should accumulate a daily time series that the user can chart with Sheets charts or a pivot table. Keep credit usage in mind (roughly 30 to 35 TwitterAPI.io credits per handle per day across the two read calls). No AI/LLM step is needed anywhere in this workflow.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentLocal listing health board for every location you manageLet support send one-off Loops emails without an engineerStop cold emails to anyone with a live deal in PipedriveiMessage campaign console with pre-flight checks and delivery boardLinkedIn Ads budget pacing dashboard for every client accountFront desk appointment confirmation board for the next 3 daysGive your team Looker numbers without buying more seatsBuild audience segments from product usage and push to LoopsTurn the people who engage with your posts into Pipedrive leads