n8n Integration

n8n is a workflow automation tool you can run on n8n Cloud or host yourself. Connecting it to Personyze lets you build workflows against your account — syncing contacts, segments, purchases and captured leads — with the option of keeping everything inside your own infrastructure.

Personyze does not ship a dedicated n8n app — you connect using n8n’s generic HTTP request module and a Personyze API key. That sounds like more work than it is: every Personyze endpoint is a plain HTTPS call with Basic authentication, so one configured connection gives you the whole API.

In the panel: Integrations › Marketplace › n8n.

Getting a key

1. Open Integrations › Marketplace and click Set up on the n8n card.
2. Click Generate new key and keep the value at hand.
3. Keep it safe — anyone holding a key can act as your account. Revoking a key here immediately stops anything still using it.

These are the same keys as the Full-featured API and Zapier. A key generated on any of those cards appears on all of them and authenticates any endpoint. Generating a separate key per automation is still worth doing, so you can revoke one without breaking the others.

Connecting in n8n

Add an HTTP Request node and create a Basic Auth credential:

• Authentication: Basic auth
• Username: api
• Password: the key you generated
• Base URL: https://app.personyze.com/rest/

Some tools prefer credentials embedded in the URL, which works too:

https://api:YOUR_API_KEY@app.personyze.com/rest/users/where/email=john@example.com

Store it as a reusable credential in n8n so every HTTP Request node in the workflow can select it, rather than entering the key in each node.

Self-hosting note. Personyze does not need to reach your n8n instance for these calls — your workflow calls out to Personyze, so a self-hosted n8n behind a firewall works without any inbound access. That only changes if you later add a Personyze webhook pointing at n8n, which does need a reachable URL.

What you can call

Anything in the REST API. The common automation shapes:

• Push a contact into Personyze — POST /rest/users with an email. Re-sending the same email merges rather than duplicating, so a workflow that runs repeatedly stays safe.
• Add someone to a segment — POST /rest/user_list_users with user_list_id and user_email.
• Report a purchase — POST /rest/products_interactions.
• Pull captured leads out — GET /rest/forms, paging on time.
• Pull campaign results — GET /rest/summary_actions.
• Delete a person — the Personyze node’s Visitor → Delete operation (POST /rest/privacy-delete): the full deletion of Data & privacy → Visitor requests, logged there, with the address added to your suppression list. A run that ran out of time fails and names what is left: run it again.

Full reference: REST API overview, path parameters, and errors, limits and retries. The integration guide covers the behaviours worth knowing before you build a sync loop.

Two things that will bite you otherwise

• Key your users on email. It is the identifier that matches an existing profile. A workflow keyed on your own internal_id creates a new user on every run.
• Error responses are plain text, not JSON. A module set to parse every response as JSON will throw on the error and hide the actual message. Check the status code: 400 means the request is wrong and retrying will not help, 503 is worth retrying with backoff.

Related

• Make Integration
• Zapier Integration
• Full-featured API