http request and create random masked email and respond to webhook
Configured with HTTP Request, Respond To Webhook, Webhook. Review the connections and setup before adapting this template.
Node categories in this workflow
- Web / API
- 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 |
| create random masked email | Web / API | HTTP Request | POST |
| Respond to Webhook | Web / API | Respond To Webhook | See node parameters |
| get fields for creation | Transform | Edit Fields | See node parameters |
| prepare output | Transform | Edit Fields | 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
httpHeaderAuth
Workflow notes
create random masked email
https://api.fastmail.com/.well-known/jmap
https://api.fastmail.com/jmap/session
Template Description
Template Description
This n8n workflow template allows you to create a masked email address using the Fastmail API, triggered by a webhook. This is especially useful for generating disposable email addresses for privacy-conscious users or for testing purposes.
Workflow Details:
- Webhook Trigger: The workflow is initiated by sending a POST request to a specific webhook. You can include
stateanddescriptionin your request body to customize the masked email's state and description. - Session Retrieval: The workflow makes an HTTP request to the Fastmail API to retrieve session information. It uses this data to authenticate further requests.
- Create Masked Email: Using the retrieved session data, the workflow sends a POST request to Fastmail's JMAP API to create a masked email. It uses the provided state and description from the webhook payload.
- Prepare Output: Once the masked email is successfully created, the workflow extracts the email address and attaches the description for further processing.
- Respond to Webhook: Finally, the workflow responds to the original POST request with the newly created masked email and its description.
Requirements:
-
Fastmail API Access: You will need valid API credentials for Fastmail configured with HTTP Header Authentication.
-
Authorization Setup: Optionally set up authorization if your webhook is exposed to the internet to prevent misuse.
-
Custom Webhook Request: Use a tool like
curlor create a shortcut on macOS/iOS to send the POST request to the webhook with the necessary JSON payload, like so:curl -X POST -H 'Content-Type: application/json' https://your-n8n-instance/webhook/87f9abd1-2c9b-4d1f-8c7f-2261f4698c3c -d '{"state": "pending", "description": "my mega fancy masked email"}'
This template simplifies the process of integrating masked email functionality into your projects or workflows and can be extended for various use cases.
http request and create random masked email and respond to webhook
http request and create random masked email and respond to webhook
Purpose and structure
This folder contains the http request and create random masked email and respond to webhook workflow. Its executable nodes use httpRequest, respondToWebhook, set, 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/Http/0606_HTTP_Respondtowebhook_Create_Webhook.json MIT; preserve source notices.