Skip to main content

Capture vendor status updates via tokenized email links and Google Sheets

Workflow preview

Workflow preview
100%
Capture vendor status updates via tokenized email links and Google Sheets preview
Open on n8n.io

1. Workflow Overview

Quick Overview This workflow sends scheduled vendor status ping emails with one click buttons, then captures responses via an n8n webhook and logs the selected status and timestamp to Google Sheets...

Best for

  • Project Management automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.scheduletrigger, n8n-nodes-base.code, n8n-nodes-base.googlesheets, n8n-nodes-base.filter, n8n-nodes-base.emailsend, n8n-nodes-base.webhook, n8n-nodes-base.if

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Patrick Graham.

Original n8n.io source

1.1 Workflow description

Title
Capture vendor status updates via tokenized email links and Google Sheets
Workflow name
Capture vendor status updates via tokenized email links and Google Sheets

Quick Overview

This workflow sends scheduled vendor status ping emails with one-click buttons, then captures responses via an n8n webhook and logs the selected status and timestamp to Google Sheets using a one-time token per ping cycle.

How it works

  1. Runs every Monday at 8am on a schedule.
  2. Reads all vendors from a Google Sheets “Vendors” tab and keeps only rows where status is set to Active.
  3. Generates a unique token per vendor, builds four status-link URLs (On Track, At Risk, Delayed, Needs PM Input), and timestamps the ping.
  4. Updates the matching vendor row in Google Sheets with the new token and ping timestamp and clears any prior response fields.
  5. Sends an HTML email to each vendor via SMTP with four one-click status buttons that link back to the n8n webhook.
  6. When a vendor clicks a button, the webhook validates the vendor_id, status value, and token against Google Sheets, writes the response status and timestamp back to the sheet (and clears the token), and returns either a confirmation page or an error page.

Setup

  1. Create a Google Sheet with a “Vendors” tab that includes the required columns (including vendor_id, status, contact_email, ping_token, response_status, and timestamps).
  2. Add a Google Sheets OAuth2 credential in n8n and replace YOUR_GOOGLE_SHEET_ID in all Google Sheets nodes.
  3. Add an SMTP email credential (for example, Gmail SMTP with an app password) and set the sender address used for the email.
  4. Set your public n8n webhook base URL and sender email in the Config code so the status links point to your production webhook URL.
  5. Activate the workflow and use the webhook’s Production URL in the outgoing emails (not the Test URL).

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Overview

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Branch 1 — Scheduled Ping

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Branch 2 — Vendor Response Capture

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 4 - Every Monday at 8am

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.1

Block 5 - Config

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 6 - Read Vendors from Sheet

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.4

Block 7 - Filter Active Vendors Only

Type / Role
n8n-nodes-base.filter - filter
Config choices
Version 2

Block 8 - Generate Tokens and Status Links

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 9 - Write Token to Sheet

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.4

Block 10 - Preserve Vendor Payload

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 11 - Send Ping Email to Vendor

Type / Role
n8n-nodes-base.emailSend - emailSend
Config choices
Version 2.1

Block 12 - When Vendor Clicks Status Link

Type / Role
n8n-nodes-base.webhook - webhook
Config choices
Version 2

Block 13 - Read Sheet to Validate Token

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.4

Block 14 - Validate Token and Status

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 15 - If Token is Valid

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2

Block 16 - Write Status to Sheet

Type / Role
n8n-nodes-base.googleSheets - googleSheets
Config choices
Version 4.4

Block 17 - Build Confirmation Page

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 18 - Show Confirmation Page to Vendor

Type / Role
n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices
Version 1

Block 19 - Build Error Page

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 20 - Show Error Page to Vendor

Type / Role
n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices
Version 1

3. Summary Table

Workflow Capture vendor status updates via tokenized email links and Google Sheets
Complexity advanced
Nodes 20
Categories Project Management
Author Patrick Graham
Published 27 May 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/15982/15982.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Capture vendor status updates via tokenized email links and Google Sheets do?

Quick Overview This workflow sends scheduled vendor status ping emails with one click buttons, then captures responses via an n8n webhook and logs the selected status and timestamp to Google Sheets...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Project Management use case.