This article provides a complete, practical walkthrough of the Splitout Datetime Send Webhook n8n agent. It connects HTTP Request, Webhook across approximately 1 node(s). Expect a Intermediate setup in 15-45 minutes. One‑time purchase: €29.

What This Agent Does

This agent orchestrates a reliable automation between HTTP Request, Webhook, handling triggers, data enrichment, and delivery with guardrails for errors and rate limits.

It streamlines multi‑step processes that would otherwise require manual exports, spreadsheet cleanup, and repeated API requests. By centralizing logic in n8n, it reduces context switching, lowers error rates, and ensures consistent results across teams.

Typical outcomes include faster lead handoffs, automated notifications, accurate data synchronization, and better visibility via execution logs and optional Slack/Email alerts.

How It Works

The workflow uses standard n8n building blocks like Webhook or Schedule triggers, HTTP Request for API calls, and control nodes (IF, Merge, Set) to validate inputs, branch on conditions, and format outputs. Retries and timeouts improve resilience, while credentials keep secrets safe.

Third‑Party Integrations

• HTTP Request
• Webhook

Import and Use in n8n

1. Open n8n and create a new workflow or collection.
2. Choose Import from File or Paste JSON.
3. Paste the JSON below, then click Import.
4. Show n8n JSON

   Title:
   Automate Emailing Obsidian Notes with Attachments Using n8n
   
   Meta Description:
   Learn how to send your Obsidian notes via email, including attachments, using this powerful n8n workflow. This automation processes YAML front matter, handles base64 files, and integrates seamlessly with Gmail.
   
   Keywords:
   Obsidian, n8n, email automation, YAML frontmatter, send email from Obsidian, Obsidian Post Webhook, Gmail API, base64 attachments, markdown automation, note-sharing workflow
   
   Third-Party APIs Used:
   
   - Gmail (via OAuth2) – to send emails with or without attachments
   - Obsidian Post Webhook Plugin – used by Obsidian to trigger the workflow via HTTP POST request
   
   Full Article:
   
   Automate Sending Obsidian Notes via Email Using n8n
   
   Obsidian is a beloved note-taking app among knowledge workers, packed with customization features and plugins. Yet, while it excels in organizing information, sharing those notes—especially via email—can be a tedious manual process. Enter n8n.
   
   In this article, we’ll explore a powerful n8n workflow that allows you to send your Obsidian notes directly as emails, including any embedded attachments. Whether you're sharing project briefs with a team or forwarding ideas to your future self, this automation streamlines it all—from trigger to confirmation.
   
   Overview of the Workflow
   
   This n8n workflow listens for a webhook request from Obsidian—using the Post Webhook plugin—and processes the note content. It parses the YAML frontmatter for metadata like recipients, subject, and reply-to fields, and takes care of email formatting and attachment handling, automatically sending it via Gmail.
   
   Key Features at a Glance:
   
   - Trigger from Obsidian using the Post Webhook plugin
   - Parse YAML frontmatter to customize email metadata
   - Handle multiple attachments with base64 encoding
   - Send with or without attachments via Gmail
   - Append timestamp responses automatically to the original note
   
   Setting up the Webhook in Obsidian
   
   First, install the Obsidian Post Webhook plugin. This allows you to send your open note to any URL on demand. In this case, you’ll provide the URL of the webhook created by the n8n workflow.
   
   Configuration Steps:
   
   1. Set your webhook URL (available from the n8n Webhook node).
   2. Test the webhook using the plugin's built-in tool.
   3. Open any note in Obsidian and initiate the “Send to Webhook” command from the command palette.
   
   Structuring Your Notes with YAML
   
   To customize how your note is sent, this workflow uses YAML frontmatter. Here’s a sample you can replicate at the top of your note:
   
   ```yaml
   ---
   to: "recipient@example.com"
   cc: "cc@example.com"
   bcc: "bcc@example.com"
   subject: "Your Obsidian Note"
   sender-name: "Your Name"
   send-replies-to: "replies@example.com"
   ---
   Note content goes here...
   ```
   
   The metadata you insert here becomes the backbone of the email. The workflow reads this data and routes it appropriately to Gmail.
   
   Attachment Support via Base64
   
   Obsidian notes often include image links or file references. The workflow checks if any attachments exist using an If node with array validation. If attachments are present:
   
   1. They are split into individual items using the Split Out node.
   2. Each base64-encoded string is cleaned, removing header data.
   3. n8n converts these strings into binary files readable by email clients.
   4. All files are aggregated and attached to the outgoing email via the Gmail node.
   
   Emails Without Attachments
   
   If there are no attachments—or it’s simply a test send—the workflow detects this path. The email is still sent using Gmail, but without running the attachment conversion steps, making it efficient and fast for plain-text notes or brief memos.
   
   Smart Testing & Feedback
   
   The workflow includes logic to detect test runs (via a boolean test field). If it’s a test, it short-circuits the main email nodes and returns a simple “Test successful” message.
   
   For real emails, once they’re sent, n8n appends a timestamped response so that your Obsidian note includes a record of when it was shared. This is generated using the DateTime and Respond to Webhook nodes.
   
   Secure and Flexible
   
   The Gmail integration uses OAuth2, ensuring secure access to your Google account. You can also clone and modify this workflow to use other email services or platforms (e.g., Outlook, Mailgun, SendGrid) depending on your preference.
   
   Conclusion
   
   Through the integration of Obsidian and n8n, this workflow enables seamless publishing of notes via email—enriched with custom YAML metadata and robust file handling. Whether you’re distributing knowledge to a team or archiving ideas in your inbox, it saves time and eliminates repetitive email formatting.
   
   It’s a wonderful example of how powerful open-source tools can amplify your productivity through automation.
   
   Ready to enhance your workflow? Download or replicate the n8n setup, install the Post Webhook plugin in Obsidian, and experience email automation like never before.

5. Set credentials for each API node (keys, OAuth) in Credentials.
6. Run a test via Execute Workflow. Inspect Run Data, then adjust parameters.
7. Enable the workflow to run on schedule, webhook, or triggers as configured.

Tips: keep secrets in credentials, add retries and timeouts on HTTP nodes, implement error notifications, and paginate large API fetches.

Validation: use IF/Code nodes to sanitize inputs and guard against empty payloads.

Why Automate This with AI Agents

AI‑assisted automations offload repetitive, error‑prone tasks to a predictable workflow. Instead of manual copy‑paste and ad‑hoc scripts, your team gets a governed pipeline with versioned state, auditability, and observable runs.

n8n’s node graph makes data flow transparent while AI‑powered enrichment (classification, extraction, summarization) boosts throughput and consistency. Teams reclaim time, reduce operational costs, and standardize best practices without sacrificing flexibility.

Compared to one‑off integrations, an AI agent is easier to extend: swap APIs, add filters, or bolt on notifications without rewriting everything. You get reliability, control, and a faster path from idea to production.

Best Practices

• Credentials: restrict scopes and rotate tokens regularly.
• Resilience: configure retries, timeouts, and backoff for API nodes.
• Data Quality: validate inputs; normalize fields early to reduce downstream branching.
• Performance: batch records and paginate for large datasets.
• Observability: add failure alerts (Email/Slack) and persistent logs for auditing.
• Security: avoid sensitive data in logs; use environment variables and n8n credentials.

FAQs

Can I swap integrations later? Yes. Replace or add nodes and re‑map fields without rebuilding the whole flow.

How do I monitor failures? Use Execution logs and add notifications on the Error Trigger path.

Does it scale? Use queues, batching, and sub‑workflows to split responsibilities and control load.

Is my data safe? Keep secrets in Credentials, restrict token scopes, and review access logs.