Playbook Β· Google Sheets Β· 15 min
Keep your creator roster up to date automatically in Google Sheets
Agencies, talent managers and ambassador programmes whose creator roster lives in a Google Sheet and goes stale between pitches.
Connect the roster sheet in Radar once, open Runs β Profile metrics β Google Sheet, point it at the tab and the column with handles, pick a first output column and the metrics you want (followers, following, posts, average reel views over the last 12, engagement rate, verified, category, name), leave the last row blank so new rows are picked up, keep overwrite on, and schedule it as a workflow: daily at 06:00 for an active roster, weekly for a quiet one. Every run rewrites the metric columns in place and writes errors such as a private or renamed account to a notes column. Your own columns are untouched. The refresh costs 250 credits per 1,000 profiles, so a 400-row roster is 100 credits a run.
You need
- A Google Sheet with one handle or profile URL per row in a single column
- A Radar workspace; scheduling on Growth or Scale
- Editor access for the Radar service account on the sheet
Step by step in Zaver
- 1
Connect the sheet once
Radar β Google Sheets β Connect. Paste the sheet link and share the sheet with the Radar service account as an editor. The sheet then appears in the "Connected sheet" dropdown of every Sheets tool.
- 2
Open the run form
Radar β Runs β Profile metrics β Google Sheet. The form is shown below exactly as it is in the product: connected sheet, tab name, the column with profile URL or @username, first data row, last row, first output column, metrics, overwrite, notes column, notification emails.
- 3
Point it at the roster
Tab name: your roster tab. Column with handles: usually A. First data row: 2 if row 1 is a header. Last row: leave blank, which means "until the first empty cell", so rows you append later are refreshed automatically.
- 4
Choose where and what to write
First output column: the first free column to the right of your own columns, for example F. Metrics: tick Followers, Avg reel views (last 12) and Engagement rate % at minimum; add Posts, Category, Name, Verified or Following if the roster uses them. Metrics are written left to right from the output column in the order shown.
- 5
Keep overwrite on and add a notes column
Overwrite replaces last run's values so the roster always shows this morning's numbers. The notes column (for example L) receives "private", "not found" or "renamed" per row instead of failing the run. Add your email under notifications to get a message when the run finishes.
- 6
Schedule it as a workflow
Click "β¦or schedule it as a workflow" instead of Queue run. Daily at 06:00 suits an active agency roster; weekly suits an ambassador list. The schedule reuses every setting on the form. Check the Runs page for delivered rows, credits debited and a log line per handle.
- 7
Turn the numbers into flags
Keep a Baseline followers column from the day each creator was added. Add Ξ vs baseline (=F2/E2-1), an engagement floor per tier on a Floors tab, and a Flag column: "check account" if the notes cell is filled, "dropping" if Ξ is under β5%, "below floor" if engagement is under the tier floor. Conditional formatting colours it.
Or ask it in ChatGPT or Claude
With Zaver connected as an MCP server, the whole job is one message. Your assistant calls run_data_tool behind the scenes.
connect my Roster sheet and schedule a daily 06:00 refresh of followers, average reel views and engagement rate for every handle in column A, writing from column F with errors in column Lget_run returns the status, units and files of any run; the schedule itself is set in Radar.
Not connected yet? Set it up in about a minute.
Where it is in Google Sheets
The menu path, step by step. Labels match the Zaver.one add-on.

1 Radar β Runs β Profile metrics β Google Sheet. The whole set-up is this one form; "β¦or schedule it as a workflow" makes it recurring. 
2 Radar β Runs: progress, log, credits debited and the CSV for every run. 3 Any cell: =ZAVER(handle or link, metric).
What you get
Input: Roster tab Β· 400 handles Β· daily 06:00 Β· output from F Β· notes in L
| Handle | Baseline | Followers | Ξ vs baseline | Avg reel views | Eng. rate | Notes | Flag |
|---|---|---|---|---|---|---|---|
| @fit*****ayla | 41,200 | 43,118 | +4.7% | 12,400 | 2.1% | ||
| @glo*****skin | 88,900 | 83,210 | β6.4% | 9,870 | 1.4% | dropping | |
| @run*****ella | 19,800 | renamed | check account | ||||
| @lif*****maya | 120,400 | 121,050 | +0.5% | 31,500 | 0.6% | below floor |
Followers, Avg reel views, Eng. rate and Notes are written by the run every morning. Baseline is typed once; Ξ and Flag are formulas.
Illustrative sample. Handles are masked; numbers show the shape of a real result, not a specific account.
Cost
250 credits per 1,000 profiles per run. A 400-row roster refreshed daily is about 3,000 credits a month (Growth); weekly is about 430 (Starter). Scheduling is free on Growth and Scale.
Limits
- Instagram profiles; YouTube channels are coming
- Average reel views and engagement rate fetch each profile's recent reels, one extra request per profile
- Runs pause when credits run out and resume after a top-up
- The run writes only to the output columns and the notes column; it never edits your own columns
Questions
Will it overwrite my own columns?
No. It writes from the first output column rightwards, one column per metric ticked, plus the notes column if you set one. Put your own columns to the left of the output column or further right than the last metric.
What happens to rows I add later?
With "Last row" left blank, the run reads until the first empty cell in the handle column, so appended rows are refreshed on the next run without touching the schedule.
What if a creator changes handle or goes private?
The row gets "renamed", "private" or "not found" in the notes column and the run continues. Find the creator by name in Radar, fix the handle, and the next run fills it.
Can I keep a history instead of overwriting?
Overwrite off keeps existing values and fills only empty cells. For a dated history, run a second schedule into a History tab with a new first output column each month, or copy the live columns into a History tab on the first of the month.
Daily or weekly?
Daily for an agency roster that feeds pitches every day; weekly for an ambassador or alumni list. Cost scales with rows times runs: 250 credits per 1,000 profiles each time.
Do I need Claude or ChatGPT for this?
No. The form and the schedule live in Radar. With Zaver connected over MCP, the same set-up is one ask, and the morning check (who dropped, who errored) is another.
Related playbooks
Turn your influencer scouting sheet into a live trackerTrack creator follower growth weeklyAudit an inherited creator list in an afternoonRun any data tool on a schedule and get the file emailedCreator trackingAll playbooks