How to integrate Unify with Vitally
To integrate Unify with Vitally, configure a Unify Play Webhook action to call the documented API with POST, the required credentials, and the destination-specific JSON body. Use this connection to pass selected account context to Vitally for Customer Success.[1][2][3][4]
- Connection
- Via API
- Customer engagement
- Tool
- Vitally
- Vitally
- Data flow
- Unify → Vitally
- JSON payload
At a glance
- Via API: Vitally receives the handoff
- POST request with an explicit JSON contract and destination authentication
- Test scenario: Preserve lifecycle ownership
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
Customer Success benefits from context when it relates to an account they own. Define the transition that makes the handoff relevant, then preserve the same account identity across systems. Keep commercial observations distinct from customer-health conclusions.
A good fit when
Teams that want to pass selected account context to Vitally for Customer Success and have an owner for the receiving process. The destination account must permit the documented request and the chosen downstream action.
Reconsider the plan when
The receiving team has not agreed how this Vitally operation should behave when the same record arrives again. Resolve the matching rule before enabling retries.
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 |
|---|---|
| Business decision | Pass selected account context to Vitally for Customer Success |
| Receiving contract | Agree which of the 4 example data fields the receiving process actually needs. Set missing-value and identity rules in the field mapping below. |
| Execution boundary | Give one owner access to inspect the Vitally request and its resulting action. |
| Completion | Decide who can confirm the Vitally outcome and recover a failed or repeated handoff. Use the completion check below as the acceptance criterion. |
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.
Pass selected account context to Vitally for Customer Success
Start with one controlled record and one intended Vitally outcome. Keep the test destination separate from live operations.
The receiving owner must distinguish accepted input from completed work. Agree on the evidence required before treating this handoff as successful.
- Prepare the destination using the Vitally setup checklist
- Resolve the sample fields for one known record and inspect the request before sending it
- Trace that handoff through the receiving operation and compare the actual destination values with the source
Preserve lifecycle ownership
Preserve lifecycle ownership: update a controlled source trait while keeping CS-managed attributes outside the request. Inspect the account and confirm the intended identity was reused.
Decide whether this case should be held for review, corrected, or retried. Make that decision before running Vitally against live records.
- Isolate the test in a controlled destination and record the starting state
- Run the edge case described above and capture the actual response and destination state
- Recover the record once, then check that recovery did not create unintended additional work
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
Pass selected account context to Vitally for Customer Success
Inspect the matched Vitally account and its traits. Verify the handoff did not create a duplicate account or overwrite Customer Success-owned fields.
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 Vitally.
Which identity should the account message use?
Use a stable accountId agreed across the source and Vitally. The account endpoint creates or updates according to that identity, so inconsistent keys can fragment one company.[4]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + Vitally workflow.
POST / JSON
| Decision | What to know |
|---|---|
| Unify action | Outbound HTTP request with configurable method, authentication, headers, and body[1] |
| Receiving operation | Agree on the accountId used to represent the company and enable the intended Analytics API message type. Copy the generated authorization header.[4] |
| Response handling | Webhook response bodies are not available as inputs to later Unify Play actions[2] |
Technical setup reference
References and requirements for the Vitally connection.
Connection requirements and setup checklist
Before connecting
- A Unify Play with a Webhook action and a controlled record for testing
- Access to the intended Vitally environment and the permissions required by the cited API or trigger
- The destination identifiers, credentials, and schema used by the request below
- An agreed record identity, duplicate policy, and owner for failed handoffs
Configure the Unify request
Use POST, the endpoint and authentication below, and JSON body format in the Webhook action. Replace setup placeholders, then inspect Expand preview with a controlled record. The receiver must respond within 8 seconds; webhook response bodies are not exposed to later Play steps.[1][2]
Request configuration
- Method
POST- URL pattern
https://YOUR_SUBDOMAIN.api.vitally.io/analytics/v1/account- Headers
Content-Type: application/jsonAuthorization: Basic YOUR_VITALLY_ANALYTICS_AUTH- Authentication
- Use the Basic authorization header generated for the Vitally HTTPS Analytics API. Confirm the enabled message types and the correct endpoint for your account.
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
{
"accountId": "example-account-001",
"messageId": "example-handoff-001",
"traits": {
"name": "Example Company",
"domain": "example.com",
"handoff_source": "Unify"
}
}Fictional data. Replace sample values before using a real Play.
Illustrative JSON for the documented receiving operation. All prospect values are fictional. Replace credentials, identifiers, schema-specific fields, and fixed example values before a controlled test. 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.[1][2][3][4]
| Payload field | Value to send |
|---|---|
accountId | Map the stable identity used by this destination to the same person or company in your source. This example identifier is not a documented Unify variable. If missing: Hold the handoff rather than creating an anonymous or incorrectly matched record. |
messageId | Supply a stable identifier for this logical handoff. Reuse it on a retry, and use a different identifier for a genuinely new event. Do not assume Unify automatically creates this sample field. If missing: Hold the handoff until the receiver or upstream workflow can establish its identity. |
traits.name | Select the available company name field for the controlled person or company record in Unify. Keep the receiving field a string. If missing: Skip or hold the handoff if this value is required by the destination; omit it only when the destination contract permits omission. Do not send a guessed value. |
traits.domain | Select the available company domain field for the controlled person or company record in Unify. Keep the receiving field a string. If missing: Skip or hold the handoff if this value is required by the destination; omit it only when the destination contract permits omission. Do not send a guessed value. |
traits.handoff_source | Keep the literal "Unify" required by this example request; change it only when deliberately changing the receiving contract. If missing: Keep this configured value in the request; do not replace it with a blank prospect field. |
accountId is the durable account identity. traits contains selected attributes; a person email is not automatically the company’s identity.
Troubleshooting
Start with the stage where the expected data or action stops appearing.
The request is rejected
Use the Basic authorization header generated for the Vitally HTTPS Analytics API. Confirm the enabled message types and the correct endpoint for your account. Check the receiving account, permissions, endpoint, and required fields against the cited documentation.[3][4]
The values or destination are wrong
Compare the resolved JSON with the field-by-field contract in Example handoff payload. Check identifiers against the selected Vitally environment, and distinguish an absent source value from an intentional static value. Fix the mapping before repeating the write.[3][4]
Receipt does not match the expected result
Find the request in the receiving logs, then inspect the actual Vitally resource or execution. If the request was accepted but no result exists, investigate the destination failure before retrying. Keep the same logical handoff identity when recovering a repeat.[3][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
