http request and get all masked emails and create random masked email
Configured with Html, HTTP Request, Respond To Webhook, Switch, and additional nodes. Review the connections and setup before adapting this template.
Node categories in this workflow
- Web / API
- Routing
- Transform
- Trigger
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 |
|---|---|---|---|
| Session | Web / API | HTTP Request | See node parameters |
| get all masked emails | Web / API | HTTP Request | POST |
| create random masked email | Web / API | HTTP Request | POST |
| Respond to Webhook | Web / API | Respond To Webhook | See node parameters |
| Switch | Routing | Switch | See node parameters |
| disabled | Web / API | HTTP Request | POST |
| delete | Web / API | HTTP Request | POST |
| gather masked email list | Transform | Edit Fields | See node parameters |
| create html template | Transform | Html | See node parameters |
| Webhook | Trigger | Webhook | See node parameters |
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
httpBasicAuthhttpHeaderAuth
Workflow notes
get all masked emails
https://api.fastmail.com/.well-known/jmap
https://api.fastmail.com/jmap/session
Template Description
Template Description
This n8n workflow is designed to manage Fastmail masked email addresses using the Fastmail API. The workflow provides the following functionalities:
- Retrieve all masked emails: Fetches all masked email addresses associated with the Fastmail account.
- Create masked email: Allows creating a new masked email with a specified state (
pending,enabled, etc.). - Update masked email state: Updates the state of a masked email such as enabling, disabling, or deleting it.
- Generate HTML template: Constructs an HTML table to display the masked emails in a user-friendly format.
Steps to Make it Work
-
Webhook Node:
- This node listens for incoming requests to manage masked emails.
- Needs Basic Authentication credentials to secure the endpoint.
-
Session Node:
- Sends a request to obtain session information from Fastmail's API.
- Requires an HTTP Header Auth credential with your Fastmail API token.
-
Switch Node:
- Routes the workflow based on the state of the incoming masked email request (
pending,enabled,disabled,deleted).
- Routes the workflow based on the state of the incoming masked email request (
-
HTTP Request Nodes:
- These nodes handle various Fastmail API calls for masked emails (get, set, update, delete).
- All HTTP Request nodes require an HTTP Header Auth credential attached, using the Fastmail API token.
-
Set Node:
- Gathers the retrieved masked email list into an array for further processing.
-
HTML Node:
- Generates an HTML template to render the masked email addresses in a table format.
-
Respond to Webhook Node:
- Sends back the HTML table to the client in response to the webhook request.
Needed Credentials
- Fastmail Masked E-Mail Addresses:
- An API token from Fastmail's API.
- Each HTTP call to Fastmail requires this credential for authentication.
Note
- Ensure that you correctly configure authentication for the API calls and webhook security.
- Use your actual Fastmail API credentials with the correct scope.
- The workflow assumes that the Fastmail API is correctly configured and accessible from your n8n instance.
- Update URLs and credentials IDs according to your n8n configuration.
http request and get all masked emails and create random masked email
http request and get all masked emails and create random masked email
Purpose and structure
This folder contains the http request and get all masked emails and create random masked email workflow. Its executable nodes use html, httpRequest, respondToWebhook, set, switch, webhook. 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
Webhook
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/Webhook/0591_Webhook_Respondtowebhook_Create_Webhook.json MIT; preserve source notices.