Skip to content

Spoken site update to daily report

Turns a short spoken end of day update from a crew lead into a structured daily report. Plain rules, not the AI, decide who hears about each issue.

OperationsWorks with n8n · Make+1Community example
Build your promptSee requirements

What it does

  • Asks a follow up when site, crew size, safety or weather is missing
  • Writes the report with work done, delays, safety issues and material needs
  • Routes safety, material and delay items by fixed rules you can read
  • Adds a row to the daily log sheet

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Sending alerts and the owner summary
  • Placing any material order

You decide what happens next.

More about this workflow

This setup is for operators and managers who keep the busywork moving. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it asks a follow up when site, crew size, safety or weather is missing. Next, it writes the report with work done, delays, safety issues and material needs. Then it routes safety, material and delay items by fixed rules you can read. Finally, it adds a row to the daily log sheet. It works with your email, spreadsheets and automation platform, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before sending alerts and the owner summary and placing any material order, and says plainly if a step cannot be undone.

“The AI listens and writes. Plain rules decide who gets alerted.”
nigamgoyal nigamgoyal on GitHub · Oct 12, 2026
Before you startEmail · Spreadsheets accessScoped permissionsn8n or Make
Explore required tools and model recommendations

Tools and access

  • Gmail

    Handles the email part of this job. Grant read-only plus compose (drafts) scopes.

    API required: Yes. Needs a Google Cloud project with an OAuth app and the Gmail API turned on. The agent signs in through OAuth with only the scopes you pick.

    Sign up: Google Workspace

  • Google Sheets

    Handles the spreadsheets part of this job. Grant access to the single sheet it needs.

    API required: Yes. Needs a Google Cloud OAuth app or a service account with the Sheets API turned on.

    Sign up: Google Workspace

  • n8n

    Handles the automation platform part of this job. Grant create workflows, left inactive until reviewed.

    API required: Yes. Needs an n8n API key from settings. New workflows should stay inactive until you review them.

    Sign up: n8n

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

GPT-6.1 Sol

Cheap cached input suits jobs that rerun the same instructions each week.

$2 per million input tokens, $10 per million output tokens, for prompts up to 272K tokens. Longer prompts cost $4 in and $15 out.

OpenAI docs as of October 11, 2026

Cheaper backup

Gemini 3.5 Flash-Lite

Low cost for simple data pulls and matching.

$0.30 per million input tokens, $2.50 per million output tokens.

Google docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

e.g. crew by trade, hours lost

2Your prompt

4 of 4 still empty
Fill these in before you run it: [YOUR SITES AND PROJECTS] [WHO GETS SAFETY, MATERIAL AND DELAY ALERTS] [YOUR DAILY LOG SHEET] [REPORT FIELDS YOU NEED: e.g. crew by trade, hours lost] You are the Spoken site update to daily report agent. Turns a short spoken end of day update from a crew lead into a structured daily report. Plain rules, not the AI, decide who hears about each issue. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Asks a follow up when site, crew size, safety or weather is missing - Writes the report with work done, delays, safety issues and material needs - Routes safety, material and delay items by fixed rules you can read - Adds a row to the daily log sheet What you must never do without a yes from a person: - Sending alerts and the owner summary - Placing any material order Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: n8n, Make, Claude Code

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect Gmail with its own login, not yours. Grant read-only plus compose (drafts) scopes.
  2. 2Connect Google Sheets with its own login, not yours. Grant access to the single sheet it needs.
  3. 3Connect n8n with its own login, not yours. Grant create workflows, left inactive until reviewed.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  6. 6Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: sending alerts and the owner summary, placing any material order.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope16 / 20

Runs on its own login across 3 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 78.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Spoken site update to daily report](https://trustcase.dev/badge/spoken-site-update-to-daily-report.svg)](https://trustcase.dev/use-cases/spoken-site-update-to-daily-report)
HTML
<a href="https://trustcase.dev/use-cases/spoken-site-update-to-daily-report"><img src="https://trustcase.dev/badge/spoken-site-update-to-daily-report.svg" alt="Trustcase trust score for Spoken site update to daily report" height="20"></a>

More operations workflows

  • Business expense report builder

    Reads your credit card statements and pulls out the charges that look like business expenses. Sure items and unsure items go on separate tabs so you only review the doubtful ones.

  • Monthly contractor invoice builder

    Builds your monthly invoice and timesheet PDF from weekly timesheet screenshots. It checks the hours before filling your template.

  • Daily delivery app sales log

    Reads yesterday's sales from each delivery app and your point of sale every morning. Writes the totals into one sales sheet.

  • Project risk escalation brief

    When a project risk turns critical, it writes a one page brief with the impact, the options and a recommendation. The project lead decides and sends it.