How to integrate Unify with Activepieces
To integrate Unify with Activepieces, use the Catch Webhook trigger and send a Play’s JSON payload to its Live URL. Configure Header Auth with a shared header name and value. Capture sample data with the test URL, publish the flow, and verify an actual run before considering the connection ready.[1][3]
- Connection
- Via webhook
- Automation
- Tool
- Activepieces
- Activepieces Catch Webhook
- Data flow
- Unify → Activepieces
- JSON payload
At a glance
- Protect the trigger with an explicit shared header
- Capture and inspect the body before mapping actions
- Switch deliberately to the live published flow
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
A reusable automation should make its entry conditions visible. Separate sample collection from live execution and decide how an operator finds a rejected or incomplete handoff. This matters particularly for teams running their own Activepieces instance, where the installed version and connectivity are part of the operational setup.
A good fit when
Teams already maintaining Activepieces flows and destination app connections.
Reconsider the plan when
If nobody owns the instance, publishing process, or failed-run review, establish those responsibilities before adding prospect intake.
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 |
|---|---|
| Entry | Protect the trigger with an explicit shared header |
| Sample | Capture and inspect the body before mapping actions |
| Publish | Switch deliberately to the live published flow |
| Result | Trace the run through the destination action |
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.
Start a prospect review flow
Operations needs to transform incoming prospect data into a review action.
Validate required fields before allowing a destination write.
- Capture a fictional sample
- Add required-field checks
- Publish and inspect the live path
Diagnose a missing run
The sender reports a response but the team sees no result.
Inspect authorization and URL mode before retrying blindly.
- Compare test and live URLs
- Check the configured header secret
- Inspect run history with valid and invalid samples
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
A valid request starts the published flow and reaches the intended destination action.
Inspect run history and the destination result. The inspected trigger implementation drops failed authentication; a response alone is insufficient evidence of an authorized run.
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 Activepieces.
Which URL starts the flow?
The trigger’s Live URL starts the published flow.[3]
What does /test do?
It generates sample data without triggering that flow.[3]
Should this design use /sync?
No. Keep the request acknowledgement separate from the final action.[2]
Does an HTTP response prove an authorized run?
No. Inspect run history and account for the documented rejected-authentication behavior.[4]
Is the flow automatically bidirectional?
No. This page describes Unify’s outbound Webhook action.[2]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
- Authentication behavior should be validated against the installed Activepieces version
- Publishing and destination connections are required
- The example URL is a pattern; use the generated instance URL
- No live Activepieces flow was executed
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + Activepieces workflow.
Technical setup reference
References and requirements for the Activepieces connection.
Connection requirements and setup checklist
Before connecting
- A Unify Play with a Webhook action
- An accessible Activepieces instance and Catch Webhook trigger
- A published flow with configured destination connections
Choose the receiving trigger
Add Catch Webhook and configure Header Auth. Copy the generated URL from your instance rather than constructing it from the example.[3]
Capture sample data
Append /test to the Live URL to capture a sample without triggering the published flow. Inspect the received body and map fields to the next action.[3]
Request configuration
- Method
POST- URL pattern
https://YOUR_ACTIVEPIECES_HOST/api/v1/webhooks/YOUR_WEBHOOK_ID- Headers
Content-Type: application/jsonX-Unify-Webhook-Key: YOUR_WEBHOOK_SECRET- Authentication
- Select Header Auth in Catch Webhook. Set Header Name to X-Unify-Webhook-Key and choose a secret Header Value. Send the matching header from Unify.
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 }} |
Read fields from the captured trigger payload’s body. Keep authentication in headers and distinguish the sample-capture URL from the live execution URL.
Troubleshooting
Start with the stage where the expected data or action stops appearing.
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
