Pyloq logo

Connect ClickUp

Use a ClickUp List as your workspace's ticket tracker: Pyloq publishes approved requirements there as tasks, and runs standups, assignment briefings and QA alerts from its tasks.
Business plan or above. Pyloq links pull requests and branches to tasks by Custom Task ID (like PYL-406), and ClickUp only offers Custom Task IDs on its Business plan and above.

Before you start

  • A ClickUp Workspace on the Business plan or above.
  • Admin or owner access in ClickUp, to switch on a ClickApp (a one-off for the Workspace).
  • A Pyloq workspace with no other ticket tracker connected. To switch from Jira, disconnect Jira first under Connectors.

Setup instructions

1. Turn on Custom Task IDs

  1. In ClickUp, open Settings → App Center and click All ClickApps.
  2. Search for Custom Task IDs, switch it on, and choose the Space your team works in.
  3. Set a short prefix such as PYL. Tasks then get IDs like PYL-406.

2. Connect in Pyloq

  1. Open Pyloq, go to Connectors and click Connect on the ClickUp card.
  2. On ClickUp's screen, choose your Workspace and click Connect Workspace.

3. Pick your List

  1. Back in Pyloq, the ClickUp connection drawer opens. Under Selected List, choose the List your tickets live in (shown as Space › Folder › List).
  2. Click Save changes. Pyloq checks Custom Task IDs and registers a webhook for that List.
  3. Check the drawer says Custom Task IDs are on. If the List has no tasks yet, add one in ClickUp and click Check again.

4. Set your statuses (optional)

In Pyloq's Automations, pick your ClickUp statuses (for example in review or complete) for QA bounce alerts, cycle time, movement notices and assignment briefings.

What you get

  • Publishing: approved stories become ClickUp tasks, and their tickets become subtasks.
  • Standups: everyone with open tasks in the List is asked about their work. A task with several assignees asks each of them.
  • Assignment briefings:a new assignee gets the task's acceptance criteria in Slack or Teams.
  • QA alerts: a task moved back from QA sends the assignee a one-line summary of the QA comment.
  • Slack, Teams and AI tools: /pyloq my-tickets, /pyloq move PYL-406, and asking your AI assistant about tasks all work with ClickUp.
  • Branches & PRs: put the Custom Task ID in the branch name or PR title (for example feature/PYL-406-login) and Pyloq links the PR to the task.

How Pyloq maps ClickUp

In PyloqIn ClickUp
Where tickets liveOne List (Space › Folder › List)
Ticket keyCustom Task ID, e.g. PYL-406
StoryTask
TicketSubtask of the story’s task
To do / In progress / DoneStatus type: open / custom / closed
AssigneeEach assignee on the task

Limits

  • Releases: ClickUp has no built-in releases. Release notes, the Release Graph and deploy status work from GitHub; ticket-based release tracking for ClickUp is coming.
  • Sprints:adding published tasks to the current sprint isn't available for ClickUp yet.
  • One List:Pyloq works with tasks in the List you picked. Tasks in other Lists can't be moved or assigned from Pyloq.
  • Deeper nesting:subtasks under subtasks need ClickUp's Nested Subtasks ClickApp.
  • One Workspace: if you approve several ClickUp Workspaces on the sign-in screen, Pyloq uses the first.

FAQ

Pyloq says "Custom Task IDs are off"

Turn on the Custom Task IDs ClickApp for the Space your List is in (step 1), then click Check again in the ClickUp drawer.

"This workspace already uses Jira"

A workspace has one ticket tracker. Disconnect Jira under Connectors, then connect ClickUp.

Can I change the List later?

Yes. Open the ClickUp drawer, pick another List and save. The webhook moves with it; tasks already published stay where they are.

What happens if I disconnect?

Pyloq stops publishing and removes its webhook. Your ClickUp tasks aren't changed.