DenlyGitHub Issues
Import repository issues as Denly tasks and route them by GitHub assignee or a default member.
1. Create a GitHub token
In GitHub open Settings → Developer settings → Fine-grained personal access tokens. Create a repository-limited token named Denly, grant issue read/write and issue-comment write permissions, generate it, and copy it immediately. Read GitHub token documentation.
2. Create the Denly connection
Open Workspace → Integrations → Connect → GitHub Issues. Use owner/repository, GitHub’s API base URL, the token, trigger tag denly, and Plan first. Keep Trigger on create disabled initially.
Routing is optional. Leave Default Denly assignee blank for unassigned tasks, or choose one workspace member to own everything from this connection.
For per-person routing use Route by external assignee: each row pairs one person in the provider (left) with a workspace member (right), and + adds another row. Routing follows the item's assignee in the provider, not whoever created it, and a matching row beats the default above.
The left-hand value must be the identifier the provider actually sends, which the field's placeholder names for you. Matching ignores surrounding spaces and letter case, but nothing else: a near-miss routes nothing and looks the same as a broken integration.
3. Add the webhook
In the repository open Settings → Webhooks → Add webhook. Set the generated URL, choose application/json, paste the Denly inbound secret as the webhook secret, subscribe to Issues and Issue comments, save, and use Recent Deliveries → Redeliver for testing. Do not use the separate GitHub App lifecycle endpoint.
4. Test and troubleshoot
Open an issue and add denly. Check Recent events. Processed creates a task; Skipped means the repository, label, assignee or create rule declined it. An empty list means the webhook secret does not match, so X-Hub-Signature-256 never verified – GitHub's Recent Deliveries tab shows those attempts and can redeliver one. Comments containing #denly revise linked tasks.