Block 1 - 📝 Workflow Overview
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Approval Workflow Handler – SendGrid & Baserow This workflow automates the end to end approval process for any request type (e.g., purchase orders, content sign off, access permissions). It routes ...
n8n-nodes-base.stickynote, n8n-nodes-base.manualtrigger, n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.sendgrid, n8n-nodes-base.baserow, n8n-nodes-base.wait, n8n-nodes-base.set
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by vinci-king-01.
Original n8n.io sourceThis workflow automates the end-to-end approval process for any request type (e.g., purchase orders, content sign-off, access permissions). It routes the request to designated approvers, records every decision in a Baserow table, and notifies requesters and stakeholders via SendGrid at each stage.
| Baserow Column | Type | Purpose | Example Value |
|---|---|---|---|
request_id |
text | Unique identifier for each request | 2542 |
title |
text | Short description of the request | “PO > $5K” |
status |
single select | Tracks state (Pending, Approved, Rejected) | “Pending” |
requester |
text | Email of person creating the request | [email protected] |
approver |
text | Email of assigned approver | [email protected] |
updated_at |
date | Last status change timestamp |
This workflow automates the end-to-end approval process for any request type (e.g., purchase orders, content sign-off, access permissions). It routes the request to designated approvers, records every decision in a Baserow table, and notifies requesters and stakeholders via SendGrid at each stage.
Setup Time: 15-25 minutes
APPROVER_EMAILS – Comma-separated list of default approvers. STAKEHOLDER_EMAILS – Comma-separated list of CC recipients.request_id.approved vs rejected.// Code node: Dynamic approver selection
const amount = items[0].json.amount;
items[0].json.approver =
amount > 10000 ? '[email protected]' : '[email protected]';
return items;
// Replace SendGrid node with Slack node
{
"channel": "#approvals",
"text": `Request ${$json["request_id"]} was approved by ${$json["approver"]}`
}
The workflow outputs structured JSON data:
{
"request_id": "2542",
"title": "PO > $5K",
"status": "Approved",
"requester": "[email protected]",
"approver": "[email protected]",
"updated_at": "2024-04-27T15:41:22.347Z"
}
request_id for faster lookups.Pro Tips:
This is a community-contributed workflow template. It is provided “as-is” without warranty; review and test thoroughly before using in production.
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.
| Workflow | Handle approval requests with SendGrid email and Baserow records |
|---|---|
| Complexity | advanced |
| Nodes | 20 |
| Categories | Document Extraction |
| Author | vinci-king-01 |
| Published | 24 Jan 2026 |
Use the JSON export at /data/workflows/12972/12972.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
Approval Workflow Handler – SendGrid & Baserow This workflow automates the end to end approval process for any request type (e.g., purchase orders, content sign off, access permissions). It routes ...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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 Document Extraction use case.