This article explains what the integration does, how to set it up, and what to expect once it is running.
One-click task import
• As soon as you add the tag latchloop
to a ClickUp task, LatchLoop automatically imports that task (and its subtasks) into your LatchLoop workspace.
Automatic analysis
• When the task arrives in LatchLoop it is immediately analysed by the LatchLoop AI agent so that you can see estimates, code-plan drafts, and implementation notes without leaving your dashboard.
Optional “auto-build”
• If the Auto-build toggle is ON (in Settings → General), LatchLoop will go further:
– create a new branch in the linked GitHub repository,
– generate the first commit(s),
– open a Pull Request with the proposed changes,
– and keep you updated inside ClickUp with a comment if it needs more information.
• If Auto-build is OFF, the task is imported and analysed, but no code is written until you press Build from inside LatchLoop.
Status & feedback inside ClickUp
• Whenever the agent replies (for example, if it needs clarification or when it has opened a PR) the message is posted back to the original ClickUp task so the whole team can follow along without switching tools.
There are two ways:
A. Recommended – use the Webhook Settings widget (no coding):
B. Manual – from ClickUp Developer portal:
taskTagUpdated
taskCommentPosted
(optional; currently unused)That’s it! The connection is live.
latchloop
.Question | Answer |
---|---|
What if I remove the latchloop tag? | The task will remain in LatchLoop; removing the tag does not delete anything. |
Can I trigger different commands via comments? | Not at the moment – the current release only reacts to the latchloop tag. |
Who can add the tag? | Anyone in ClickUp with permission to edit tags can trigger the import. |
How does LatchLoop choose a Git branch name? | The branch starts with the task short-ID plus a slug of the title, e.g. LL-123-add-login . |
What if the agent needs more details? | The bot will leave a comment in ClickUp asking for clarification and will pause the build until you reply. |
Is my ClickUp key safe? | Yes – your key is encrypted at rest and is only sent to ClickUp when making API calls on your behalf. |
No task appears in LatchLoop
• Make sure the webhook shows “Active” in ClickUp.
• Verify that the latchloop
tag was added (edits to an existing tag will not retrigger).
Bot says “Invalid ClickUp API key”
• Regenerate the key in ClickUp → Apps and update it in LatchLoop settings.
Webhook error “Invalid signature”
• The secret stored in ClickUp must match the one stored in LatchLoop Webhook Settings.
Pull request never created (with Auto-build ON)
• Check that your GitHub repository is connected and the bot has permission to push branches.
If you are still stuck, send us the timestamp of the failing task and we will investigate the logs.
• API keys and webhook secrets are encrypted and scoped to your user account – no other team can see them.
• LatchLoop only requests task:read
and task:write
scopes in ClickUp; it does not access docs, goals, or time tracking.
• All traffic between ClickUp, LatchLoop, and GitHub travels over HTTPS.
Happy building! 🚀
Have questions? Reach out at [email protected]