How to integrate Unify with n8n
To integrate Unify with n8n, configure a Webhook node and use its URL in a Unify Play’s Webhook action. Send a POST request with JSON and matching authentication. Test the received fields, then validate the Production URL after publishing the n8n workflow.[1][2][4]
- Connection
- Via webhook
- Automation
- Tool
- n8n
- Webhook node
- Data flow
- Unify → n8n
- JSON payload
At a glance
- Use a Unify Webhook action to send data to n8n
- Validate a fictional record before mapping live prospect values
- Check downstream completion separately from HTTP acceptance
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
The webhook is the entry point to a larger process. Agree what the incoming fields mean, what happens when one is missing, and which result proves the work is complete. Testing and production use different n8n URLs, so the move to a published workflow needs its own controlled check.
A good fit when
Teams that manage a custom receiving workflow in n8n and want it to start from a Unify Play.
Reconsider the plan when
If the workflow treats an immediate HTTP acknowledgement as proof that every node succeeded, add an explicit check of the intended downstream result.
Design the handoff
Use this framework to agree on the input, the next action, and who owns the result.
Suggested workflow design, based on the documented capabilities below.
| Stage | Decision to make |
|---|---|
| Input contract | Choose the prospect fields the receiving nodes require and define missing-data handling. |
| Receiving workflow | Validate the incoming body and authentication before mapping the next node. |
| Production handoff | Check the published workflow and Production URL with a controlled record. |
| Completion | Inspect the execution through the final intended node, not only the webhook acknowledgement. |
Explore the scenarios
Choose the situation that fits your team and work through the proposed plan.
Open a scenario to explore its plan. Checklists track your selections in this page only.
Build the first receiving workflow
You need to inspect the incoming prospect data before publishing the n8n workflow.
Use the test URL while the node is listening, and validate the authentication header on both sides.
- Configure the Webhook node and Header auth
- Listen for a test event and send the sample from Unify
- Map fields from body into the next node
Move the workflow to production
The test succeeds and you want the published workflow to receive future Play events.
A production URL change is a separate validation step. Keep checking the execution through its final node.
- Publish the n8n workflow
- Replace the test URL in Unify with the Production URL
- Send a controlled record and inspect Executions
Illustrative workflow, not a preconfigured automation. Complete these checks in your own account.
Define success before launch
Inspect the data and the intended outcome separately. Connection status is only the first check.
Expected, not tested
The Webhook node receives the sample under body, and the next node gets the mapped prospect values.
Review the n8n execution through its final node. With an immediate response, the HTTP response only confirms that the workflow started.
Documentation-based reference. This workflow has not been tested end to end. Use a record or event you control before enabling live activity.
Questions answered
Common decisions when connecting Unify and n8n.
How do I connect Unify to n8n?
Create the Webhook node in n8n, then configure a Webhook action in your Unify Play with its generated URL. Use POST and a JSON body for this recipe. Send a controlled sample, map its fields, and inspect the receiving workflow.[1]
Is this a native Unify n8n connector?
This article uses the outbound Unify Webhook action and a receiving webhook in n8n. It does not represent a separate native connector in the Unify integrations catalog.[1]
What authentication does the n8n webhook need?
Choose Header auth in the n8n Webhook node. Create an X-Unify-Webhook-Key header credential, then select API Key (Header) in Unify and use the same header name and secret. This header name is our example, not a required Unify convention.[4]
Does a successful HTTP response mean the n8n workflow finished?
Review the n8n execution through its final node. With an immediate response, the HTTP response only confirms that the workflow started.[4]
Where should I map the prospect fields in n8n?
The Webhook node exposes the incoming JSON under body. For example, the expression for the sample email in the next node is {{ $json.body.prospect_email }}. This is n8n syntax, not Unify syntax.[4]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
- This article documents an outbound webhook, not a two-way sync
- The sample is fictional; resolved variables, receiver permissions, retries, and downstream completion need account-level testing
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + n8n workflow.
POST / JSON
| Decision | What to know |
|---|---|
| Direction | Unify → n8n[1] |
| Receiving step | Webhook node[4] |
| Example request | POST with a JSON body[1] |
| Authentication | Choose Header auth in the n8n Webhook node. Create an X-Unify-Webhook-Key header credential, then select API Key (Header) in Unify and use the same header name and secret. This header name is our example, not a required Unify convention.[4] |
| Completion check | Review the n8n execution through its final node. With an immediate response, the HTTP response only confirms that the workflow started.[4] |
Technical setup reference
References and requirements for the n8n connection.
Connection requirements and setup checklist
Before connecting
- Access to a Unify Play with a Webhook action
- An n8n workflow with an HTTPS endpoint reachable from Unify
- Permission to configure webhook credentials and publish the n8n workflow
Request configuration
- Method
POST- URL pattern
https://YOUR_N8N_HOST/webhook-test/YOUR_WEBHOOK_PATH- Headers
Content-Type: application/jsonX-Unify-Webhook-Key: YOUR_SECRET- Authentication
- Choose Header auth in the n8n Webhook node. Create an X-Unify-Webhook-Key header credential, then select API Key (Header) in Unify and use the same header name and secret. This header name is our example, not a required Unify convention.
Choose JSON as the body format. Unify sets Content-Type automatically. The receiver must respond within Unify’s 8-second timeout; request responses are not passed to later Play steps.[2]
Replace URL placeholders with the actual receiver URL from your account or deployed application. These example URLs are not working endpoints.
Example handoff payload
Start with a fictional prospect. Validate the resolved values before using a real record.
Inspect the sample payload and field mapping
{
"event": "prospect_handoff",
"prospect_name": "Alex Morgan",
"prospect_email": "alex@example.com",
"company_name": "Example Company",
"company_domain": "example.com"
}Fictional data. Replace sample values before using a real Play.
The keys are an example handoff format, not required Unify field names. Use the field mapping to distinguish record data from fixed settings. Select available fields in your Play and inspect Expand preview; do not replace configuration values with prospect data.[2]
| Payload field | Value to send |
|---|---|
event | A fixed label you choose for this workflow |
prospect_name | Use {{ person.first_name }} and {{ person.last_name }} for the prospect name |
prospect_email | Use {{ person.email }}; decide how to handle missing values |
company_name | Use {{ company.name }} |
company_domain | Use {{ company.domain }} |
The Webhook node exposes the incoming JSON under body. For example, the expression for the sample email in the next node is {{ $json.body.prospect_email }}. This is n8n syntax, not Unify syntax.
Troubleshooting
Start with the stage where the expected data or action stops appearing.
The test URL stops responding
Select Listen for test event again. n8n documents a 120-second listening window for test webhooks.[4]
The production URL does not trigger a run
Verify that the workflow is saved and published and that Unify uses its Production URL. Look in Executions, rather than expecting production data in the editor.[4]
Authentication or mapping fails
Compare the header name and value on both sides. For empty fields, inspect body in the node output and map from that object.[4]
Sources & review
Official documentation reviewed on September 15, 2026.
Technical claims link to primary documentation from Unify and the destination tool. Scenarios, field choices, and recovery plans are editorial implementation examples. Documentation review is separate from execution testing.
Documentation reviewed; end-to-end execution not tested. No named technical reviewer has signed off on these articles yet.
Content updated: . Report a correction to Unify with the tool name, source URL, and behavior you observed.
Keep exploring
