---
title: "Meta conversion workflows with n8n and Make | Plainrouter"
description: "Use n8n or Make HTTP workflows with Plainrouter for eligible website conversions. Map consent, preserve event IDs, and inspect Meta delivery beyond a green run."
canonical: https://plainrouter.com/solutions/automation
last_updated: 2026-09-23
---

[All solutions](/solutions)

# Meta conversion tracking for n8n and Make.

Trace website conversions from your n8n or Make workflow through to Meta delivery. Plainrouter shows event acceptance and delivery results so you can investigate what happened after a successful HTTP step.

HTTP integration · no native connector required

[Try the n8n sandbox recipe](/library/meta-capi-without-gtm#try-an-n8n-request-without-sending-a-real-conversion) · [See pricing](/pricing)

## From your workflow to Meta

- **Verified purchase** — Original order and website context
- **n8n or Make** — Consent check and event mapping
- **Plainrouter** — Receipt and delivery diagnostics
- **Meta** — Eligible conversion delivery

Your workflow orchestrates the request. Plainrouter’s event receipt and Meta’s delivery response are separate checkpoints.

## What Plainrouter adds

### Make retries recognizable

Preserve the original event ID and purchase time across retries. A rerun of the workflow should not invent another business event.

### Keep consent in the decision

Load the real consent record and check withdrawal before each send, including queued retries. Stop the advertising path when required permission is missing.

### Investigate the delivery outcome

Retain the API response and inspect the event’s deliveries. A green node, an accepted event, and an attributed conversion are different outcomes.

## Is this a fit for your setup?

For automation builders handling verified website purchases who need stable request identity, consent mapping, and a place to investigate delivery outcomes.

[Explore Signals](/product/signals)

### When your existing setup is enough

Use a native Meta module or a direct Graph API request when it already solves your workflow. Plainrouter adds a separate event and delivery layer; basic HTTP connectivity alone is not a reason to switch.

[Compare tracking approaches](/library/server-side-tracking-tools)

## How n8n and Make conversion tracking works

### Start with fictional data

Import the existing n8n sandbox starter and run its success, rejection, and repeat exercises. It validates a synthetic request without storing a conversion or contacting Meta.

### Build a separate production flow

Read the Conversion API contract and map a verified website purchase with its original consent and visitor context. Changing only the sandbox endpoint is insufficient.

### Use the HTTP step deliberately

In n8n, use an HTTP Request node; in Make, use an HTTP module. Send Plainrouter’s event object, store the Server secret in managed credentials, and preserve the event ID on retry.

### Follow the receipt

A new production event returns 202; an accepted duplicate returns 200. Inspect acknowledgement warnings and the event’s deliveries before treating a successful run as successful Meta delivery.

## n8n and Make conversion tracking FAQ

### Does Plainrouter have native n8n or Make connectors?

These workflows use the HTTP capabilities of n8n and Make. The downloadable starter is an n8n sandbox workflow, not a native connector or a Make blueprint.

### Can I send an arbitrary CRM record as a conversion?

This solution covers eligible website events with the required consent and visitor context. A changed CRM status or a valid JSON body cannot manufacture a missing observed or attributed website visit.

### Does the sandbox prove production delivery?

No. Its simulated response proves only that the synthetic request passed validation. Production authentication, consent, visitor joins, deduplication, and Meta delivery require separate checks.

## Implementation guides

- [Map the production event](/library/meta-capi-without-gtm#adapt-an-automation-workflow-for-a-real-website-event)
- [Read the Conversion API contract](https://plainrouter.com/docs/api/conversions)
- [Diagnose missing or duplicate events](/library/meta-capi-missing-duplicate-events)

Reference documentation: [n8n HTTP Request node](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/) · [Make HTTP module](https://apps.make.com/http)

[Sending directly from a Next.js application?](/solutions/nextjs)

## Ready to build your production workflow?

Start with the synthetic sandbox exercise, then create a workspace for the separately authenticated production flow. Preserve the original event identity, consent and website context.

[Get started](/register) · [See pricing](/pricing)