Block 1 - Send Gmail as Alias
- Type / Role
- n8n-nodes-base.httpRequest - httpRequest
- Config choices
- Version 4.2
This workflow is provided as-is. Please review and test before using in production.
This n8n template allows you to send emails with a custom alias from your Gmail account Since the native Gmail node has some limitations regarding use of email aliases, this template allows you to ...
n8n-nodes-base.httprequest, n8n-nodes-base.code, n8n-nodes-base.splitout, n8n-nodes-base.if, n8n-nodes-base.webhook
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Jacob @ vwork Digital.
Original n8n.io sourceSince the native Gmail node has some limitations regarding use of email aliases, this template allows you to set up your own internal endpoint/sub-workflow to send emails as an email alias .
This workflow uses a Code node and the Gmail API via an HTTP node to format the email content and send using an alias on your Gmail account.
{
"senderName": "SENDER NAME HERE",
"fromEmail": "FROM EMAIL HERE",
"replyTo": "REPLY TO EMAIL HERE",
"toEmail": "[email protected]",
"subject": "SUBJECT LINE HERE",
"htmlBody": "HTML BODY HERE - MUST BE JSON STRINGIFIED",
"file_urls": [
"FILE URLS FOR ATTACHMENTS HERE"
]
}
Only the following are required fields:
You can easily convert this to a sub-workflow by swapping out the Webhook trigger for a "When executed by another workflow" trigger
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 Gmail messages with custom aliases and attachments via API |
|---|---|
| Complexity | intermediate |
| Nodes | 6 |
| Categories | Personal Productivity |
| Author | Jacob @ vwork Digital |
| Published | 02 Jul 2025 |
Use the JSON export at /data/workflows/5613/5613.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 n8n template allows you to send emails with a custom alias from your Gmail account Since the native Gmail node has some limitations regarding use of email aliases, this template allows you to ...
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.