How to integrate Unify with Front

To integrate Unify with Front, 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 create a Front contact with useful account context.[1][2][3]

By UnifyDocumentation reviewed September 15, 2026

Explore scenarios Technical setup Open Unify

Connection: Via API; Customer engagement
Tool: Front; Front
Data flow: Unify → Front; JSON payload

At a glance

Via API: Front receives the handoff
POST request with an explicit JSON contract and destination authentication
Test scenario: Preserve existing custom fields

When this workflow makes sense

Start with the decision your team needs to make, then choose the connection that supports it.

A shared inbox benefits from context that helps a teammate recognize the person behind a message. Keep the contact description factual and concise. Avoid replacing notes that belong to the support or sales team when refreshing source data.

A good fit when

Teams that want to create a Front contact with useful account context 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 Front 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	Create a Front contact with useful account context
Receiving contract	Agree which of the 3 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 Front request and its resulting action.
Completion	Decide who can confirm the Front 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.

Create a Front contact with useful account context

Start with one controlled record and one intended Front outcome. Keep the test destination separate from live operations.

The decision that matters

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 Front 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

Your validation checklistThe Front destination and record identity are correctThe required fields match the controlled recordThe completion evidence is saved and the next action has an owner

0 of 3 checks marked by you

Preserve existing custom fields

Preserve existing custom fields: read a test contact before applying a controlled update through a receiver. Compare all custom fields afterward rather than checking only the new one.

The decision that matters

Decide whether this case should be held for review, corrected, or retried. Make that decision before running Front 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

Your validation checklistThe intended edge case has an observable resultRecovery does not create unintended additional workThe Front owner has a documented recovery decision

0 of 3 checks marked by you

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

Create a Front contact with useful account context

Open the contact in Front and verify its email handle, description, and any explicitly configured list membership.

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 Front.

Does creating a Front contact start a conversation?

No. Contact creation adds a person and their handles. Conversation creation or messaging requires a separate operation.[3]

Limits & decisions

Check these boundaries before designing a live workflow around the connection.

When updating custom fields, Front warns that omitted custom fields can be erased. Read existing values and merge deliberately before implementing updates.[3]
API and trigger access depend on the destination account, permissions, and configuration. This request pattern is not a claim of native Unify sync.[3]

What the connection supports

Understand the connection, the data involved, and the behavior that matters for a Unify + Front workflow.

Connection flowVia API

Unify

Front

Prospect data

POST / JSON

Documented behavior at a glance
Decision	What to know
Unify action	Outbound HTTP request with configurable method, authentication, headers, and body[1]
Receiving operation	Choose the Front company and credential scope. Decide which contact description or custom fields the source may manage.[3]
Response handling	Webhook response bodies are not available as inputs to later Unify Play actions[2]

Technical setup reference

References and requirements for the Front connection.

Unify reference: Webhook action Front reference: official connection reference

Connection requirements and setup checklist

Before connecting

A Unify Play with a Webhook action and a controlled record for testing
Access to the intended Front 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

Prepare the Front destination
Choose the Front company and credential scope. Decide which contact description or custom fields the source may manage.[3]
Configure the destination action
Create a contact with at least one handle object containing handle and source. Avoid adding an avatar until multipart upload handling is deliberately implemented.[3]
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]
Validate the complete handoff
Run the success and edge-case scenarios in Explore the scenarios with a controlled record. Save the request identity and destination evidence, then apply the completion check before enabling live traffic.[3]

Request configuration

Method: POST
URL pattern: https://api2.frontapp.com/contacts
Headers: Content-Type: application/json
Authorization: Bearer YOUR_FRONT_TOKEN
Authentication: Use a Front API token with contacts:write in the intended company.

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

Example request body

{
  "name": "Alex Morgan",
  "description": "Prospect context from Unify for Example Company",
  "handles": [
    {
      "handle": "alex@example.com",
      "source": "email"
    }
  ]
}

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]

Payload field	Value to send
`name`	string / dynamic / Full nameSelect the available full 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.
`description`	string / dynamic / Message template plus selected person/company fieldsKeep the editorial message template and replace only its fictional person name, email, or company name with available source fields. Preserve JSON escaping. If missing: Remove optional missing context from the message; hold it if the receiving team cannot identify the record.
`handles.0.handle`	string / dynamic / EmailSelect the available email 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.
`handles.0.source`	string / static / Request configurationKeep the literal "email" 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.

The email goes in handles[].handle with source: email. A contact is separate from a conversation and this request does not send a message.

Troubleshooting

Start with the stage where the expected data or action stops appearing.

The request is rejected

Use a Front API token with contacts:write in the intended company. Check the receiving account, permissions, endpoint, and required fields against the cited documentation.[3]

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 Front environment, and distinguish an absent source value from an intentional static value. Fix the mapping before repeating the write.[3]

Receipt does not match the expected result

Find the request in the receiving logs, then inspect the actual Front 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]

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: 2026-09-16. Report a correction to Unify with the tool name, source URL, and behavior you observed.

How to integrate Unify with Front