See llms.txt for all machine-readable content.

Back to Templates

Prepare client delivery review jobs from Google Sheets with Prooftask and Slack

Created by

Created by: prooftask || prooftask
prooftask

Last update

Last update 2 days ago

Categories

Quick overview

Read a Google Sheets delivery queue, check material mappings and current project access, then prepare saved Prooftask jobs for internal review. Write preparation results back to the sheet and notify the internal Slack review channel before a separate, deliberate delivery submission.

How it works

  1. Run manually to read ready delivery tasks from Google Sheets. Validate unique task IDs, criterion-specific material mappings, HTTPS reference formats and required file metadata, then check current project access and agreement requirements. This workflow does not fetch original files or independently verify supplied digests.
  2. Persist each request ID and complete request JSON in the sheet, then read them back before calling Prooftask. Retrying an unchanged task reuses the saved request; previously saved jobs are resumed instead of prepared again.
  3. Prepare and save the delivery job through the Prooftask Agents API, write its result back to the queue, and send a review reminder to the responsible team in its Slack channel. Record the confirmed notification marker; an uncertain Slack response can still produce a duplicate reminder.
  4. Stop for a human to inspect the frozen request_json and original materials in the queue; read the saved job by ID as needed. Deliberately submit that same job using the separate send-job example. The authorized buyer decides acceptance in Prooftask. A separate status-sync example refreshes the original queue afterwards. This published template stops at preparation and internal review; it does not submit, accept, sign or pay.

Setup

  1. Use an existing Prooftask project with current agreed criteria and an Agent grant authorizing SUBMIT_MATERIALS. Configure HTTP Header Auth with Authorization: Bearer <token> on all three Prooftask HTTP nodes. The grant must cover the selected project.
  2. Import the delivery queue CSV linked below into Google Sheets and select the same spreadsheet, tab and Google Sheets credential throughout the workflow. Set spreadsheetId, numeric sheetId and slackChannelId in the Configuration node. Map actual file metadata and one material entry per agreed criterion.
  3. Connect a Slack bot credential with chat:write permission and add the bot to the responsible team's internal review channel. Mark only reviewed queue rows ready and run one manual execution per queue at a time, including any companion status sync. Read the setup and complete-loop guides before using real project materials.

Requirements

  • Google Sheets and Slack credentials, an existing Prooftask project with agreed criteria, and a scoped Prooftask Agent token. Uses standard n8n nodes; no community node installation is required. Prooftask service availability and pricing apply separately.

Customization

  • Adapt the queue, criterion-to-material mapping and internal review message to your agreed delivery process. Keep persisted request identity, explicit submission and buyer acceptance separate.

Additional info

Setup and recovery guide: https://github.com/cognitive-emergence/prooftask-integrations/blob/main/n8n/DELIVERY_QUEUE.md

Complete delivery loop (prepare and review -> deliberate submission -> buyer review -> result writeback): https://github.com/cognitive-emergence/prooftask-integrations/blob/main/n8n/DELIVERY_LOOP.md

Queue CSV: https://github.com/cognitive-emergence/prooftask-integrations/blob/main/n8n/delivery-queue-example.csv

Separate submission workflow: https://github.com/cognitive-emergence/prooftask-integrations/blob/main/n8n/send-job.json

Separate queue status-sync workflow: https://github.com/cognitive-emergence/prooftask-integrations/blob/main/n8n/sync-job-status.json

The submission and status-sync examples are separate from this marketplace-approved preparation template. The preparation template skips already-notified rows; it is not an ongoing acceptance-status poller. Configure the sync using the original Agent grant and the documented review_* columns, then run it manually after submission and buyer actions. It updates the same task row, leaves preparation identities unchanged and writes UNKNOWN on failed or revoked reads. A status observation does not establish signing, record issuance or payment.

Validated with a real n8n 2.39.8 engine and an isolated Prooftask API, including preparation, replay and recovery, deliberate submission, exact-job acceptance readback and revoked-grant UNKNOWN. Google Sheets and Slack transport used synthetic responses. Real-service OAuth, actual destination writeback and customer acceptance require separate observed production acceptance; see the complete-loop guide. No API token or customer data is included.