Skip to content
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.

Trigger app
GitHub as the trigger

Workflows fire when something happens in GitHub.

Action app
ClickUp as the action

Workflows do something in ClickUp, instantly.

See all 9 actions →
Both directions

Pick the way that fits your stack.

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

GitHubClickUp

When something happens in GitHub, do it in ClickUp.

1 GitHub triggers wired to 9 ClickUp actions. Most-used pairing: New GitHub EventAdd Comment.

ClickUpGitHub

Or fire it the other way around.

6 ClickUp triggers wired to 23 GitHub actions downstream.

See ClickUpGitHub
Popular pairings

Common GitHub → ClickUp workflows.

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

Showing 4 of 9 combinations
How it works

Connect GitHub and ClickUp in five steps.

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

  1. 1
    Connect
    Authorize GitHub and ClickUp

    Open Tiny Command, authorize GitHub and ClickUp once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a GitHub trigger

    Drop the GitHub → New GitHub Event trigger onto the canvas. Tiny Command auto-registers the webhook.

    POST /v1/webhooks/github.trigger-event
  3. 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. 4
    Action
    Add the ClickUp action

    Drop the ClickUp → Add Comment action below it. Map fields from the GitHub payload into the ClickUp inputs.

    clickup.create-comment
  5. 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 GitHub + ClickUp.

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

Other apps that pair well with GitHub.


Wire GitHub to ClickUp in 2 minutes.

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