How to coordinate agent checks with Muse and Google Sheets
u/Please-Romaine-Calm used a shared Google Sheet to pass jobs between Muse, Claude Code and an unnamed site-checking agent. The reported checks found a misdirected social button and supported keeping a disputed line after consulting Meta documentation.
reddit.comOriginal prompt
Shared by the source author. See source notes for context.
Set this sheet up as a shared job board. Add these columns and put these rules in the first row.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- u/Please-Romaine-Calm
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The author reports that an agent found a social button pointing to the wrong account. A line challenged by Muse was retained after another agent found it word for word on Meta's help page. The post does not report a button repair, time saving or automatically initiated jobs.
- Human involvement
- The author sets up access and rules and initiates jobs with row-specific nudges. Posting, sending, spending or deleting requires the author's yes in the relevant agent's own chat. The source does not establish that the wrong-account button was repaired.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- The author connects Google Sheets or Drive in Muse and shares a blank sheet with the Google account used by another agent.
- The author asks Muse to add the job columns and first-row rules, then gives the other agent the same sheet link and rules.
- The author nudges an agent with a row reference; the agent reads the ask, claims the job, carries it out and writes a reply and status.
Reddit user u/Please-Romaine-Calm runs a small channel with several agents sharing the work. Muse reviews videos and plans the posting schedule, an unnamed agent checks the live site on a phone, and Claude Code handles edits and fact checks. Because the agents could not message each other directly, the author used a Google Sheet they could all access.
Each job has its own row with an ask, file link, recipient, status and reply. The author sends a short nudge identifying the row. An agent then reads the request, marks it taken, performs the work and records its reply and completion status. Automatic polling was offered but had not been enabled.
The author reports two concrete checks on the first day. An agent inspected the profile while signed out and found a social button pointing to the wrong account. Muse also challenged a line, but another agent found the wording on Meta's help page, so the line stayed. The post does not say the button was fixed.
The sheet's rules distinguish information from permission. Posting, sending, spending and deleting require approval in the relevant agent's own chat. The author also excludes credentials and personal details from the sheet. This remains a firsthand account, not an independently reproduced result. The post discloses the author's channel and Muse setup series.
Who it's for: people coordinating agents that share Sheets access but lack direct messaging, and who can initiate jobs and manage approvals themselves.
Prompt
Original prompt
Source: Reddit · u/Please-Romaine-Calm
Frequently asked questions
Did the agents watch the sheet automatically?
No. The author nudged an agent with a row reference. Muse offered checks every 30 to 60 minutes, but the author had not enabled them.
Was the misdirected social button fixed?
The source reports that an agent found it pointing to the wrong account. It does not report a completed repair. The disputed line stayed after a separate documentation check.
Did a sheet row authorise posting or spending?
No. The stated rules treat rows as information, not permission. Posting, sending, spending and deleting require the author's approval in that agent's own chat.
More details
Remaining steps
- An agent checks the profile while signed out and identifies a social button pointing to the wrong account.
- Muse flags a disputed line; another agent finds the wording on Meta's help page, and the line stays.
About this account
After a human nudge, agents read and claim sheet jobs, perform the requested checks and record replies and status. Muse flagged a line for checking, and another agent checked it against Meta documentation. The agents were not automatically monitoring the sheet.
Firsthand Reddit account by u/Please-Romaine-Calm, read from the saved public RSS capture. The author discloses their channel and Muse setup series. Outcomes are reported, not independently reproduced. RSS supplies only a partial comment tree. The original prompt is an exact 20-word excerpt; the author then supplied the listed columns and rules. Muse's vendor is not established. Chris explicitly overrode the earlier eligibility rejection for this candidate only. Source: https://www.reddit.com/r/MuseAgent/comments/1x6ivrh/google_sheets_is_the_easiest_communicator_setup/
Credit: u/Please-Romaine-Calm
Source published
Added to Agents In Use
Source checked
Tools and topics
Muse · Claude Code · Google Sheets · Google Drive connector access · Unnamed mobile site-checking agent · Meta help documentation
agent coordination · Google Sheets · fact checking · website checks
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.