How to integrate Unify with ClickUp
To integrate Unify with ClickUp, send a Play webhook to the create-task endpoint for a specific List. Supply the task name, description, and an authorized token in the Authorization header. If the List relies on required Custom Fields, enable check_required_custom_fields and supply applicable values before considering intake ready.[1][3]
- Connection
- Via webhook
- Team collaboration
- Tool
- ClickUp
- ClickUp List task
- Data flow
- Unify → ClickUp
- JSON payload
At a glance
- Choose the team’s actual intake location
- Enforce required fields and task-type compatibility
- Review who can see the task and who is notified
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
A List often encodes how a team works through required fields and task types. Keep that contract intact when introducing automated intake. The integration should reduce the effort of creating usable work, not bypass the information a reviewer depends on.
A good fit when
Teams with an established ClickUp review List and explicit intake requirements.
Reconsider the plan when
If the List is overloaded with unowned tasks, define ownership and a useful selection threshold first.
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 |
|---|---|
| List | Choose the team’s actual intake location |
| Contract | Enforce required fields and task-type compatibility |
| Audience | Review who can see the task and who is notified |
| Repeat | Decide whether another selection means another task |
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 complete review task
A team wants selected prospects in its established List.
Respect the existing intake contract.
- Inspect the required fields
- Map one complete fictional record
- Review the task from the owner’s view
Catch incomplete prospect intake
A record lacks information the team needs.
Keep the requirement visible instead of bypassing it.
- Enable required-field validation
- Test an incomplete sample
- Correct the input and inspect the result
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 task appears in the intended List with the context required by the reviewer.
Inspect the task fields, visibility, and notification recipients. Test missing required values before using the live audience.
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 ClickUp.
Which URL receives the request?
Use the task endpoint for the actual List ID.[3]
Should I prepend Bearer to a personal token?
The documented personal-token header is Authorization: {personal_token}.[4]
Are required Custom Fields enforced by default?
No. Opt in with check_required_custom_fields: true.[3]
Can I use this token for someone else’s app installation?
ClickUp documents an OAuth flow for applications used by others.[4]
Does a created task prove the review is done?
No. Unify’s outbound request and the team’s follow-up are separate stages.[2]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
- The sample requires adaptation to actual List requirements
- Task creation is not an upsert
- Notifications require review of the chosen assignees and watchers
- No live ClickUp task was created
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + ClickUp workflow.
POST / JSON
Technical setup reference
References and requirements for the ClickUp connection.
Connection requirements and setup checklist
Before connecting
- A Unify Play with a Webhook action
- A ClickUp token with access to the intended List
- List requirements and applicable Custom Field IDs
Choose the List and schema
Copy the List ID and inspect the task type and applicable Custom Fields. Select a concrete review action for the task name.[3]
Authorize the request
Send a personal token in the Authorization header for your internal setup. Use the documented OAuth flow when building for other users.[4]
Enforce the intake requirements
The sample opts into check_required_custom_fields. Add required values for the List before sending; an incomplete sample may deliberately fail validation.[3]
Review the task and audience
Inspect the task and its fields. Review assignees and watchers: notify_all is not a switch that disables all notifications.[3]
Request configuration
- Method
POST- URL pattern
https://api.clickup.com/api/v2/list/YOUR_LIST_ID/task- Headers
Content-Type: application/jsonAuthorization: YOUR_CLICKUP_TOKEN- Authentication
- For an internal setup, use your ClickUp personal API token directly in Authorization: YOUR_CLICKUP_TOKEN. The documented personal-token format does not use a Bearer prefix.
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
{
"name": "Review Avery Morgan",
"description": "Check the fictional prospect avery@example.com before follow-up.",
"check_required_custom_fields": true
}Fictional data. Replace sample values before using a real Play.
Fictional task. Supply applicable required Custom Fields before sending to a List that requires them. 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][3]
| Payload field | Value to send |
|---|---|
name | Map the intended review action and person |
description | Map useful review context |
Map the person and action into name and description. Keep the real List ID in the endpoint. Custom Field values must use their documented IDs, types, and applicability rules.
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
