๐ฌ 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.
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.
| Node | Category | Type | Operation |
|---|---|---|---|
| Create data pix | Transform | Edit Fields | See node parameters |
| Create img bin | Transform | Convert To File | toBinary |
| Respond to Webhook | Web / API | Respond To Webhook | See node parameters |
| Request img | Trigger | Webhook | See node parameters |
| Do anything to log | Routing | No Op | 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
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
-
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
idto identify the recipient.
- Path:
-
Set Base64 Data (
Create data pix)- Creates a variable
datacontaining a Base64-encoded transparent PNG image (1x1 pixel).
- Creates a variable
-
Convert to Binary (
Create img bin)- Converts the Base64
datastring into a binary file. - Sets MIME type to
image/png.
- Converts the Base64
-
Respond to Webhook (
Respond to Webhook)- Sends the binary image file in the HTTP response.
-
Logging (
Do anything to log)- Placeholder node to log or process the
idor request metadata. - You can access the
idusing{{$json["query"]["id"]}}. - You can also use any parameter you want
- Placeholder node to log or process the
โ๏ธ 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.