How to integrate Unify with Langflow
To integrate Unify with Langflow, POST prospect JSON from a Play to a flow containing a Webhook component. Authenticate with the flow owner’s API key, parse the incoming fields, and connect the result to your chosen processing steps. The webhook acknowledgement confirms background execution started, not that the output is ready.[1][3]
- Connection
- Via webhook
- Automation
- Tool
- Langflow
- Langflow Webhook component
- Data flow
- Unify → Langflow
- JSON payload
At a glance
- Choose the prospect facts the flow needs and preserve their meaning
- Parse the incoming keys before constructing any model input
- Give the generated result an owner and a visible review destination
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
An AI-assisted review can help a rep organize known context before deciding what to do next. Define the output as a brief with supplied facts and suggested questions, then give a human responsibility for checking it. Sending more context is useful only when the flow preserves the difference between what the prospect record says and what a model infers.
A good fit when
Teams already using Langflow who need a controlled AI processing step and a reviewable output.
Reconsider the plan when
If the next action is a simple deterministic mapping, an AI step may add unnecessary ambiguity. Avoid designs that let unreviewed generated claims become customer-facing facts.
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 | Choose the prospect facts the flow needs and preserve their meaning |
| Processing | Parse the incoming keys before constructing any model input |
| Review | Give the generated result an owner and a visible review destination |
| Completion | Inspect the final artifact after the background task starts |
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.
Prepare a prospect review brief
A rep wants a concise review artifact before deciding on outreach.
Keep observed fields and generated suggestions separate.
- Choose the exact facts to include
- Map the fictional record into the Parser
- Review the output and label suggestions as such
Handle a prospect with missing context
Some records lack an email or company field.
Decide what can still be processed and what should require review.
- Define the required input fields
- Test a sample missing one field
- Inspect whether the flow produces an intentional fallback
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 flow receives the fictional prospect and produces the intended review artifact at the destination you configured.
Check parsed input and the final artifact separately. The documented background-start acknowledgement does not demonstrate successful model or destination execution.
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 Langflow.
How does Unify trigger a Langflow flow?
A Unify Webhook action sends a POST request to the flow’s webhook endpoint. The flow must include a Webhook component and connected processing steps.[3]
Which API key should Unify send?
Use a Langflow API key belonging to the flow owner in the x-api-key header. A provider key used by an AI component serves a different purpose.[4]
Does the webhook return the finished AI result?
The documented webhook response acknowledges a background task. Inspect the flow output separately to check whether its processing and destination steps completed.[3]
How do I turn the JSON into a prompt input?
Connect the Webhook Data output to a Parser and reference the incoming keys in its template. Validate the parsed text before connecting it to further processing.[3]
Is an AI-written prospect brief a verified fact source?
The webhook transports the fields configured in your Play. This example adds a review step for generated content; it does not establish new evidence about a prospect.[1]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
- Model and destination components must be configured in your own flow
- Account-specific hosting and access requirements must be checked
- A generated suggestion should stay distinguishable from incoming facts
- No live flow, model output, or destination delivery has been tested
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + Langflow workflow.
POST / JSON
| Decision | What to know |
|---|---|
| Receiver | Webhook component triggers the flow from an HTTP request[3] |
| Authentication | Webhook API-key validation checks the authenticated flow owner[4] |
| Mapping | Parser extracts selected values from the Webhook Data output[3] |
| Response | The documented response reports that processing started in the background[3] |
Technical setup reference
References and requirements for the Langflow connection.
Connection requirements and setup checklist
Before connecting
- A Unify Play with a Webhook action
- A reachable Langflow deployment and a flow with a Webhook component
- An API key belonging to the flow owner and credentials for any downstream components
- An explicit destination for the output and a person who reviews it
Prepare the flow
Add a Webhook component and connect its Data output to a Parser component. Map the expected prospect properties into the text your downstream components need. Save the flow and copy its webhook endpoint.[3]
Require the owner’s key
Keep LANGFLOW_WEBHOOK_AUTH_ENABLE enabled and use the owner’s Langflow API key in x-api-key. The key authenticates this request; credentials for model or destination components are configured separately.[4]
Inspect the actual output
Inspect the Parser output and the configured destination after execution. Decide which fields are facts and which are generated suggestions. Review failed component runs before enabling the Play.[3]
Request configuration
- Method
POST- URL pattern
https://YOUR_LANGFLOW_HOST/api/v1/webhook/YOUR_FLOW_ID- Headers
Content-Type: application/jsonx-api-key: YOUR_LANGFLOW_API_KEY- Authentication
- Keep webhook authentication enabled. In Unify, choose API Key (Header), name it x-api-key, and use a Langflow API key belonging to the flow owner. Use the endpoint from your own installation; hosted variants may have different access requirements.
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 }} |
Map prospect_name, prospect_email, company_name, and company_domain from the Webhook Data object into the Parser template. Langflow’s parser placeholders belong to Langflow; resolve Unify variables in the Play before sending the request.
Troubleshooting
Start with the stage where the expected data or action stops appearing.
The key is rejected
Confirm the API key belongs to the owner of this flow and webhook authentication settings match the deployment. Do not confuse a model-provider key with a Langflow API key.[4]
Parser fields are blank
Compare Parser template keys with the actual JSON properties received by the Webhook component. Inspect its connected Data output before investigating later model steps.[3]
The request starts a task but no artifact appears
Inspect the flow and its downstream components. A background-start response is only the first checkpoint; verify where the output is stored or delivered.[3]
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
