โ† All N8N workflows
Messaging & emailConvert To FileNo OpRespond To WebhookEdit FieldsWebhook

๐Ÿ“ฌ Workflow: Transparent Tracking Pixel for Email Open Detection

Configured with Convert To File, Respond To Webhook, Webhook. Review the connections and setup before adapting this template.

Workflow preview
TransformCreate data pixEdit FieldsTransformCreate img binConvert To FileWeb / APIRespond to WebhookRespond To WebhookTriggerRequest imgWebhookRoutingDo anything to logNo Op

Node categories in this workflow

  • Transform
  • Web / API
  • Trigger
  • Routing

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.

Workflow node names, types, and operations
NodeCategoryTypeOperation
Create data pixTransformEdit FieldsSee node parameters
Create img binTransformConvert To FiletoBinary
Respond to WebhookWeb / APIRespond To WebhookSee node parameters
Request imgTriggerWebhookSee node parameters
Do anything to logRoutingNo OpSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8nโ€™s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. 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

None declared. HTTP requests and Code nodes may still need configuration.

Workflow notes

๐Ÿ“ฌ Workflow: Transparent Tracking Pixel for Email Open Detection

๐Ÿ“ฌ Workflow: Transparent Tracking Pixel for Email Open Detection

๐Ÿ“Œ Description

This workflow serves a 1x1 transparent PNG image via a webhook, which can be embedded in an email to track when the email is opened. When the image is loaded by the recipient's email client, the webhook is triggered, optionally capturing a userId to identify who opened the email.


๐Ÿ“‚ Workflow Steps

  1. Webhook Trigger (Request img)

    • Path: /webhook/change-with-your-id
    • Triggered by an HTTP request (e.g. when the image is loaded in an email).
    • Accepts a query parameter id to identify the recipient.
  2. Set Base64 Data (Create data pix)

    • Creates a variable data containing a Base64-encoded transparent PNG image (1x1 pixel).
  3. Convert to Binary (Create img bin)

    • Converts the Base64 data string into a binary file.
    • Sets MIME type to image/png.
  4. Respond to Webhook (Respond to Webhook)

    • Sends the binary image file in the HTTP response.
  5. Logging (Do anything to log)

    • Placeholder node to log or process the id or request metadata.
    • You can access the id using {{$json["query"]["id"]}}.
    • You can also use any parameter you want

โœ‰๏ธ How to Use in Emails

Embed the image in an HTML email like this:

<img src="https://<your-n8n-instance>/webhook/db4880e7-2134-4994-94e5-a4a3aa120440?id=1234" width="1" height="1" style="display:none;" alt="" />

When the email is opened and the image is loaded, the workflow will be triggered.


๐Ÿ› ๏ธ Notes

  • Some email clients block images by default; this may prevent tracking.
  • You can enhance the workflow to store open events in a database, log the timestamp, IP, or user agent.
  • Make sure to comply with data privacy and consent regulations (e.g. GDPR).
๐Ÿ“ฌ Workflow: Transparent Tracking Pixel for Email Open Detection

๐Ÿ“ฌ Workflow: Transparent Tracking Pixel for Email Open Detection

Purpose and structure

This folder contains the ๐Ÿ“ฌ Workflow: Transparent Tracking Pixel for Email Open Detection workflow. Its executable nodes use convertToFile, noOp, 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

Request img

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/0914_Webhook_Respondtowebhook_Create_Webhook.json MIT; preserve source notices.

More in Messaging & email