Skip to content
NEWMarketplace and the trig8n Agent: sell what you build, and get plans and changes that are tested before you see them. See what is new

Library / Tasks & Project Management

Tasks & Project Management

Review agency asset readiness and approvals from Google Sheets and Gmail

Run manually to read a Google Sheets tracker, calculate asset readiness and version approvals, and build an owner follow-up queue for a creative agency.

What it does

## Review agency input readiness and version approvals with Google Sheets ### Purpose and audience Help a small creative, web or marketing agency coordinator review missing assets, received work awaiting review, requested changes and approved current versions. This manual workflow reads a human-maintained Google Sheets tracker, calculates readiness from included required items, and produces an owner follow-up queue. Receipt, silence and approval of an older version never approve the current version. ### Connected apps and how it works Uses built-in n8n nodes and Google Sheets. A Manual Trigger loads private configuration and reads projects, items, decisions and send_ledger. JavaScript validates IDs, types, dates, receipts and version-specific decisions. A strict branch returns a readable preview with project readiness, item status and suggested owner actions. Invalid or conflicting input fails closed. Gmail is included only as an optional, disabled, separately approved synthetic test-send path. It reserves and rechecks an append-only ledger, current source data and explicit operator approval before sending. Its original email formatter differs from the readable preview proposal. ### Setup The workflow's yellow notes contain the complete sheet headers, data types, copyable fictional sample rows, configuration fields and operating steps. Create a synthetic workbook with the four exact tab names, enter the provided headers and your fictional records, select an authorized Google Sheets credential on every Sheets node, and set spreadsheet_id in Pilot configuration. Keep mode=preview, allow_test_send=false, all recipient/approval fields blank, single_operator_confirmed=false and Gmail disabled. No external sample file or private repository document is needed. ### Usage Run manually, one execution at a time, without activation or publication. Inspect Return preview only for evaluation, readable_items, proposed_subject and proposed_body. The preview writes no ledger rows and sends no email. A person maintains all receipts, versions, explicit decisions, owners and dates. Use the embedded example and fixed-clock instructions for a reproducible no-send check; restore the current clock afterward. ### Limitations and costs This is a synthetic single-operator pilot. It does not watch uploads, review file contents, authenticate reviewers, infer approval or contact clients.

The steps

  1. Run one approved test
  2. Pilot configuration
  3. Validate pilot setup
  4. Read projects
  5. Read items
  6. Read decisions
  7. Read ledger
  8. Gate reviewed preview
  9. Reserve before sending
  10. Recheck ledger
  11. Recheck projects
  12. Recheck items
  13. Recheck decisions
  14. Verify fresh data and reservation

21 steps in total.

Similar automations