This article provides a complete, practical walkthrough of the Manual Stickynote 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:
   Automating Unread Email Retrieval from Fastmail Using n8n and JMAP
   
   Meta Description:
   Discover how to automate the process of fetching unread emails from Fastmail using n8n’s powerful workflow automation and the JMAP protocol. Learn how to build a real-time email workflow in just a few steps.
   
   Keywords:
   n8n workflow, Fastmail, JMAP API, unread email, email automation, Fastmail API, n8n httpRequest, workflow automation, n8n Fastmail integration, email parsing
   
   Third-party APIs Used:
   - Fastmail JMAP Session Endpoint (https://api.fastmail.com/jmap/session)
   - Fastmail JMAP API Endpoint (https://api.fastmail.com/jmap/api/)
   
   Article:
   
   Automating Email Fetching from Fastmail with n8n and JMAP
   
   In today’s digital-first landscape, businesses and personal productivity enthusiasts are constantly looking for tools that can automate repetitive tasks. If you're using Fastmail for communication, automating the retrieval of unread messages can dramatically improve how you process incoming mail.
   
   n8n, a powerful open-source workflow automation tool, can be integrated with Fastmail using the JSON Meta Application Protocol (JMAP) standard. In this guide, we’ll walk through how a custom n8n workflow connects to Fastmail, fetches your inbox ID and account information, and then retrieves a list of unread messages—all without having to write and deploy custom scripts.
   
   🔧 Tools Used
   
   This workflow makes use of several core components:
   - Fastmail’s JMAP-compliant API
   - n8n’s built-in HTTP Request, Set, and Manual Trigger nodes
   - Generic authentication via HTTP headers (Bearer Token)
   
   📬 Step-by-Step Breakdown of the Workflow
   
   This workflow is composed of six primary functional steps. Let's explore each component in detail.
   
   1. Manual Trigger: Executing the Workflow
   Node: When clicking “Execute Workflow”
   
   The workflow is manually triggered via this node. It’s perfect for testing and debugging purposes before transitioning the setup into a scheduled or event-driven automation.
   
   2. Fetch API Details
   Node: Fetch API details  
   Endpoint: https://api.fastmail.com/jmap/session
   
   This first HTTP request fetches essential session metadata, including the account ID tied to your Fastmail account. We leverage this information to make subsequent JMAP requests specific to your user session.
   
   3. Get Mailboxes
   Node: Get mailboxes  
   Endpoint: https://api.fastmail.com/jmap/api/
   
   Using data from the session request, this node sends a POST request to retrieve all mailboxes associated with your account. We’re primarily interested in the mailbox with the "inbox" role, which is identified programmatically in the response.
   
   4. Format Results
   Node: Format results
   
   Here, we extract such useful elements as:
   - The Fastmail-specific account ID
   - The inbox mailbox ID (used later to filter unread emails)
   
   This is achieved using n8n’s Set node and simple JavaScript expressions to reference previously fetched JSON objects.
   
   Example:
   - account_id is extracted from $('Fetch API details').first().json.primaryAccounts.
   - mailbox_id is extracted by searching the response for a mailbox where the role is set to "inbox.”
   
   5. Retrieve Unread Messages
   Node: Get unread messages  
   Endpoint: https://api.fastmail.com/jmap/api/
   
   This HTTP request is the most pivotal step. It issues two related JMAP method calls in a single request:
   
   - Email/query:
     Filters all emails in the "inbox" mailbox that do not have the $seen keyword (i.e., are unread). The response is sorted by received date and limited to the top 3 results.
     
   - Email/get:
     With the IDs returned from the query above, this method call fetches additional attributes for each email: ID, sender, subject line, keywords, and time of receipt.
   
   The result is a concise yet information-rich response you can use to notify users, populate dashboards, or forward summaries to another app.
   
   🛡️ Authentication Notes
   
   Authentication is handled via n8n’s HTTP Header Auth mechanism. For Fastmail, you can use your API token by configuring a credential with:
   
   - Header Name: Authorization  
   - Value: Bearer YOUR_FASTMAIL_API_TOKEN
   
   This approach keeps your API token secure and ensures compatibility with JMAP’s standard authentication flow.
   
   📌 Optimization Hint
   
   While this workflow makes real-time API calls to fetch mailbox and account information, it’s worth noting that those values don’t typically change. As advised in the embedded sticky note within the n8n workflow, consider storing the accountId and mailboxId values as persistent variables or in an external database to improve performance and reduce unnecessary API calls.
   
   🎯 Use Cases
   
   This type of workflow can be expanded or adjusted for several use cases:
   - Automated daily morning unread email digests
   - Real-time Slack/Telegram notifications for new unread messages
   - Keyword-based email filters to trigger conditional workflows
   - Integration with CRM systems to track new leads or support tickets
   
   Conclusion
   
   By leveraging n8n and Fastmail’s JMAP-compatible API, you can set up a powerful email automation workflow in minutes. This example workflow provides just a glimpse into the potential of integrating open standards like JMAP with modern automation platforms like n8n.
   
   Whether you're managing business communications or just want to stay better organized, automating unread email fetching is a small change that can have a big impact.
   
   Ready to get started? Fire up n8n and give this workflow a try—or fork and evolve it to fit your unique needs.

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.