Google Sheets to Prooftask Delivery Jobs via n8n + Slack

Turn your Prooftask delivery preparation into a one-click n8n flow—driven by a mapped payload and confirmed via Slack

This workflow helps you manually create and persist a draft client delivery job in Prooftask by sending your mapped project, criteria, and delivery materials to the Prooftask Agents API. Designed for n8n users who want reliable, repeatable delivery-job setup—with Slack notifications included.

What this workflow does

• Manual run: Start the workflow whenever you’re ready to prepare a delivery job.
• Builds a single delivery payload: It creates one request containing a persistent requestId, the target projectId, a workflowReference, and delivery materials mapped to agreed criterion IDs.
• Validates correctness: It checks that exactly one job is being prepared and that the requestId and projectId match the required ID formats.
• Creates & persists in Prooftask: Sends the payload to the Prooftask Agents API to create and save a saved delivery job.
• Returns created job details: The workflow outputs the created job information so you can record it.

Use cases

• Prepare a Prooftask delivery job for a client after your team finalizes deliverables and materials.
• Standardize submission structure by mapping delivery materials to agreed Prooftask criterion IDs.
• Retry safely by reusing the same requestId to re-prepare the same delivery preparation.

Technical details

• Integrations: Prooftask Agents API + Slack
• Auth: Requires an n8n HTTP Header Auth credential using Authorization: Bearer <token> for a Prooftask scoped Agent token.
• n8n nodes/components: if, code, no op, slack, crypto, and sticky note.

Setup requirements

You’ll need an existing Prooftask project with agreed delivery criteria, the relevant projectId and criterion IDs, plus Prooftask service availability/pricing handled separately. Replace the example values (requestId, projectId, workflowReference, summary, materials, references, and files) with your real delivery data.