Skip to main content
Use the n8n integration when you want qualified lead events from traxy to start an n8n workflow. n8n delivery uses a webhook-style connection. traxy sends a signed POST request to the n8n webhook URL you configure.

​
Before you connect n8n

Owners and admins can connect n8n and change delivery settings. Make sure you have:
  • an n8n workspace or instance
  • an n8n workflow with a webhook trigger ready to receive data
  • the n8n webhook URL
  • an optional bearer token if your webhook expects one
Use a secure https:// URL. traxy cannot send to insecure endpoints.

​
Connect n8n

  1. Open Integrations.
  2. Open n8n.
  3. Add an Integration Name.
  4. Paste the Webhook URL from n8n.
  5. Add an Auth Header if your n8n webhook expects one.
  6. Click Connect.
  7. Review the Qualified Lead Detected trigger.
  8. Choose whether to keep auto-send on.
  9. Set the ICP match threshold for automatic delivery.
  10. Decide whether to enable Send repeat engagement from qualified leads.
  11. Click Save Configuration.
  12. Click Send Test Payload before you rely on the workflow.
If you connect n8n but do not keep a valid webhook URL saved, n8n delivery stays disabled.

​
Choose manual or automatic delivery

n8n can work in two ways:
  • Manual delivery from the leads table when you want to review each lead first
  • Automatic delivery when you want traxy to send new qualified leads to n8n as soon as they meet your threshold
Automatic delivery is non-retroactive. It sends leads that qualify after auto-send is turned on. Repeat engagement delivery only works when the n8n trigger and auto-send are both enabled. If you turn auto-send off, repeat engagement delivery turns off too.

​
Send leads manually

Use manual delivery when you want to control which leads enter n8n.
  1. Open Leads.
  2. Select one or more leads.
  3. Choose the send action.
  4. Select n8n.
  5. Confirm the send.
traxy queues the selected leads for delivery to the configured n8n webhook.

​
Review the payload

The n8n integration page includes Payload & Help with sample JSON for first qualified lead delivery and repeat engagement delivery. The payload includes event metadata plus lead, profile, company, contact, and engagement data. Use the sample payload in traxy as the source of truth when you map fields in n8n.

​
Verify requests

n8n requests are signed. Each request includes X-Traxy-Signature and X-Traxy-Timestamp so your receiver can verify that it came from traxy. If you add an auth header, use the bearer format shown in the app.

​
Test and troubleshoot

Use Send Test Payload before you turn on an important workflow. The test is one immediate request. Lead deliveries can retry temporary failures. Automatic delivery may pause if repeated failures are not fixed. If you send manually from Leads, you may see states such as queued, delivered, or failed. Fix the underlying n8n issue first, then retry from the lead. Review automatic settings carefully before you enable them for a shared workspace.

​
Disconnect n8n

Use Disconnect when you want traxy to stop sending events to n8n. Disconnecting n8n does not change existing n8n workflows or execution history.