ClickUp Troubleshooting

Common issues and how to resolve them.

Tasks Not Being Detected

If Jasper isn't detecting task IDs from your PRs:

  • Verify the task ID pattern - Check that your pattern matches your ClickUp task IDs in Settings → ClickUp
  • Ensure the task exists - The task must exist in a mapped ClickUp space
  • Put the ID in the title - Jasper only reads the pull request title, so check that PR Title is ticked under Search In. The branch name and description aren't searched.
  • Wait for the review - Tasks are linked after Jasper's AI review finishes

Common Pattern Issues

Issue Solution
Pattern too strict Use CU-[a-zA-Z0-9]+ instead of CU-[0-9]+
Missing prefix Ensure your pull request title includes the CU- prefix

Task Status Doesn't Change

This is expected. Jasper doesn't change a task's status when a pull request opens or merges, even with Sync PR status to tasks ticked in the repository mapping. Move the task yourself in ClickUp or from the desktop app, after you connect your own ClickUp account in Tasks.

OAuth Connection Issues

If you're having trouble connecting to ClickUp:

  • Try reconnecting - Disconnect and reconnect the integration
  • Check permissions - Connect with a ClickUp owner or admin account so Jasper can see every space
  • Verify app access - Third-party app access must be enabled in ClickUp settings
  • Clear browser cache - Clear cookies and try again in an incognito window

Webhooks Not Appearing in Logs

If webhooks aren't showing up in Webhook Logs:

  • Verify endpoint URL - Must be exactly:
    https://heyjasper.ai/webhooks/clickup
  • Check webhook status - Ensure the webhook is active in ClickUp (not paused or errored)
  • Confirm workspace connection - Your ClickUp workspace must be connected to Jasper via OAuth
  • Test with an action - Update a task in ClickUp and check logs within a few seconds

Webhook Signature Verification Failures

If you see 401 errors or signature verification failures:

  • Check your secret - Go to Settings → ClickUp → Webhook Settings and verify your secret is configured
  • Match secrets exactly - The secret in Jasper must match the secret used when creating the webhook in ClickUp
  • No extra characters - Check for trailing whitespace or extra characters
  • Regenerate if needed - Click "Regenerate Secret" in Jasper and update the webhook in ClickUp

Tip: If you don't need signature verification, you can click "Remove secret" in the Webhook Settings section. This will accept all webhooks without verification (not recommended for production).

Auto Comments Not Posting

If review comments aren't appearing on ClickUp tasks:

  • Check the toggle - Ensure Post review comments on tasks is ticked in the repository mapping
  • Verify task detection - The PR must have detected and linked task IDs
  • Check ClickUp permissions - The connected account needs permission to post comments
  • Review wasn't completed - Comments only post when reviews complete successfully

Quick Links

Still Need Help?

If you're still experiencing issues:

Was this page helpful?
Next Krisp.ai Integration