Per-pair page

ClickUp + GitHub: tasks and PRs, kept in lockstep.

Create GitHub issues from ClickUp tasks for engineering execution; mirror PR status back as ClickUp custom field updates. PM and eng stay aligned.

Connect ClickUp and GitHub See reverse direction

Trigger app

ClickUp as the trigger

Workflows fire when something happens in ClickUp.

See all 6 triggers →

Action app

GitHub as the action

Workflows do something in GitHub, instantly.

See all 23 actions →

Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

ClickUp → GitHub

When something happens in ClickUp, do it in GitHub.

6 ClickUp triggers wired to 23 GitHub actions. Most-used pairing: Comment Posted → Add Labels.

GitHub → ClickUp

Or fire it the other way around.

1 GitHub triggers wired to 9 ClickUp actions downstream.

New GitHub Event

See GitHub → ClickUp →

Popular pairings

Common ClickUp → GitHub workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 138 combinations

When comment posted in ClickUp, add labels in GitHub.

Fires when a new comment is posted on a task in the selected ClickUp workspace. The webhook is registered automatically when the workflow is published. Use to mirror discussion to Slack or feed AI summaries.

When comment posted in ClickUp, create comment in GitHub.

When comment posted in ClickUp, create issue in GitHub.

When comment posted in ClickUp, create pull request in GitHub.

When new list in ClickUp, add labels in GitHub.

Fires when a new list is created in the selected ClickUp space. The webhook is registered automatically when the workflow is published. Useful for templated list provisioning or governance audit logs.

When new list in ClickUp, create comment in GitHub.

When new list in ClickUp, create issue in GitHub.

When new list in ClickUp, create pull request in GitHub.

When new task in ClickUp, add labels in GitHub.

Fires when a new task is created in the selected ClickUp workspace. The webhook is registered automatically when the workflow is published. The standard inbound hook for routing, enrichment, and notification flows.

How it works

Connect ClickUp and GitHub in five steps.

No code, no glue, no half-day setup. Each step is one click.

1
Connect
Authorize ClickUp and GitHub
Open Tiny Command, authorize ClickUp and GitHub once each. Both connections are available to every workflow on your account.
2
Trigger
Pick a ClickUp trigger
Drop the ClickUp → Comment Posted trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/clickup.trigger-comment-posted
3
Transform
Add a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
4
Action
Add the GitHub action
Drop the GitHub → Add Labels action below it. Map fields from the ClickUp payload into the GitHub inputs.
github.add-labels-to-issue
5
Publish
Publish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about ClickUp + GitHub.

How do I create a GitHub issue from a ClickUp task?

ClickUp Task Status Updated to "In Dev" → GitHub Create Issue in the right repo, title from task name, body with ClickUp URL. Save issue number in a ClickUp custom field for round-trip linking.

Can I mirror GitHub PR merge back into ClickUp?

Yes. GitHub PR Merged trigger → look up the matching ClickUp task by issue URL → ClickUp Update Task to status = "Shipped" and write merge date to a custom field. Closes the loop without manual updates.

How do I auto-label GitHub issues from ClickUp tags?

Pass ClickUp tags directly as GitHub labels on Create Issue. Labels must exist on the repo first; provision missing ones via a one-time workflow.

Can I map ClickUp assignees to GitHub usernames?

Maintain a lookup of clickup_user_email → github_username. Pass the matched username as assignees on Create Issue. Validate the username exists to avoid 422 errors.

How do I post GitHub PR comments as ClickUp comments?

GitHub PR Comment Created → look up the linked ClickUp task by PR URL → ClickUp Create Comment with the author and comment body. Useful for non-engineer stakeholders watching the task.

Which side owns engineering status?

GitHub, always. PR state is the source-of-truth. ClickUp mirrors it via the relevant GitHub triggers; eng never has to manually update ClickUp.

Other apps that pair well with ClickUp.

ClickUp + Gmail

ClickUp + Slack

Communication

ClickUp + Google Sheets

Spreadsheets & Databases

Wire ClickUp to GitHub in 2 minutes.

Free tier available. No credit card. No onboarding call.

Try for free Request a demo