Block 1 - When Executed by Another Workflow
- Type / Role
- n8n-nodes-base.executeWorkflowTrigger - executeWorkflowTrigger
- Config choices
- Version 1.1
This workflow is provided as-is. Please review and test before using in production.
This is a basic helper workflow to abstract the process of sending an alert email through Gmail. It takes in two parameters: Subject Lines (as an array of lines) You'll also need to fill in your em...
n8n-nodes-base.executeworkflowtrigger, n8n-nodes-base.gmail, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Kevin.
Original n8n.io sourceThis is a basic helper workflow to abstract the process of sending an alert email through Gmail.
It takes in two parameters:
You'll also need to fill in your email.
Notably, all emails it sends have ❗ n8n Alert: prefixed to the subject line, which makes them easy to identify and highlight in an email inbox.
In Gmail, this can be done by starring all messages that come in with ❗ n8n Alert: in the subject line, then using the Priority Inbox to push starreed messages to the top.
It's important to star the message rather than Mark As Important, because Gmail refuses to mark emails sent by automation as important.
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 | Send standardized alert emails via Gmail with custom subject and content |
|---|---|
| Complexity | beginner |
| Nodes | 4 |
| Categories | Personal Productivity |
| Author | Kevin |
| Published | 20 Jul 2025 |
Use the JSON export at /data/workflows/6189/6189.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.
This is a basic helper workflow to abstract the process of sending an alert email through Gmail. It takes in two parameters: Subject Lines (as an array of lines) You'll also need to fill in your em...
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 Personal Productivity use case.