ℹ️ Replacing the initial nodes
Configured with HTTP Request. Review the connections and setup before adapting this template.
Node categories in this workflow
- Trigger
- Web / API
- Transform
Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.
Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.
How it works
The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.
| Node | Category | Type | Operation |
|---|---|---|---|
| When clicking "Execute Workflow" | Trigger | Manual Trigger | See node parameters |
| Get mailboxes | Web / API | HTTP Request | POST |
| Fetch API details | Web / API | HTTP Request | See node parameters |
| Format results | Transform | Edit Fields | See node parameters |
| Get unread messages | Web / API | HTTP Request | POST |
Setup
- Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
- Connect your own credentials through n8n’s credential store. Replace
REPLACE_WITH_*values with your resource identifiers. - Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
- Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.
Requirements
An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.
Credential types declared in the source
httpHeaderAuth
Workflow notes
ℹ️ Replacing the initial nodes
ℹ️ Replacing the initial nodes
These nodes fetch your account and mailbox IDs. Consider saving these values instead of querying them on every execution to improve performance and reduce the load on the JMAP API.
ℹ️ Credentials
ℹ️ Credentials
The JMAP standard does not limit the available authentication options. Fastmail (the sponsor of the standard) supports Bearer authentication as well as OAuth2.
In n8n you can implement the Fastmail Bearer authentication by creating Header Auth credentials with a name of Authorization and a value of Bearer $apiToken (replacing $apiToken with your actual token from Fastmail).
ℹ️ Replacing the initial nodes
ℹ️ Replacing the initial nodes
Purpose and structure
This folder contains the ℹ️ Replacing the initial nodes workflow. Its executable nodes use httpRequest, manualTrigger, set. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.
Setup
Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.
Entry points
When clicking "Execute Workflow"
Verification
Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.
Attribution
https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Manual/0374_Manual_Stickynote_Send_Webhook.json MIT; preserve source notices.