Block 1 - Sticky Note — Main
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Overview Store, update, and retrieve contacts in a Notion database by sending a JSON payload to an n8n workflow. Email is used as the unique identifier — no Notion page IDs required. What this...
n8n-nodes-base.stickynote, n8n-nodes-base.manualtrigger, n8n-nodes-base.notion, n8n-nodes-base.if, n8n-nodes-base.respondtowebhook, n8n-nodes-base.switch
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Tejasv Makkar.
Original n8n.io sourceStore, update, and retrieve contacts in a Notion database by sending a JSON payload to an n8n workflow. Email is used as the unique identifier — no Notion page IDs required.
The workflow has three actions, controlled by a single action field in the payload:
| Column | Notion type |
|---|---|
| Name | Title |
| Phone | Phone number |
| Status | Select — suggested options: Lead, Contacted, Qualified, Customer, Closed |
| Notes | Text |
... top right → Connections → select your integration.Use these in the Manual Trigger to test each action:
Create a contact:
{
"action": "create",
"name": "Jane Doe",
"email": "[email protected]",
"phone": "+49 123 456 789",
"status": "Lead",
"notes": "Met at Berlin conference"
}
Update a contact:
{
"action": "update",
"email": "[email protected]",
"name": "Jane Doe",
"phone": "+49 123 456 789",
"status": "Customer",
"notes": "Signed contract on March 24"
}
Fetch a contact:
{
"action": "get",
"email": "[email protected]"
}
This workflow works as a backend API. Any frontend can send POST requests to the Webhook URL and display the response — no direct Notion API connection needed in the frontend.
What n8n handles so your frontend does not have to:
To wire up a frontend: replace the Manual Trigger with a Webhook node, point your form or dashboard at the Webhook URL, and read the JSON response to show feedback to the user. Works with React, Vue, plain HTML, or no-code tools like Webflow or Bubble.
status values are case-sensitive — send Lead not lead.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 | Add, update, and fetch contacts from a Notion database by email |
|---|---|
| Complexity | advanced |
| Nodes | 17 |
| Categories | CRM |
| Author | Tejasv Makkar |
| Published | 24 Mar 2026 |
Use the JSON export at /data/workflows/14304/14304.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.
Overview Store, update, and retrieve contacts in a Notion database by sending a JSON payload to an n8n workflow. Email is used as the unique identifier — no Notion page IDs required. What this...
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 CRM use case.