DenlyGitLab Issues
Import GitLab issues and notes from GitLab.com or self-managed GitLab.
1. Create a GitLab token
In GitLab open User settings → Access tokens or create a project access token. Name it Denly, grant api, set an expiration, create it, and copy it immediately. Read GitLab access tokens.
2. Create the Denly connection
Open Workspace → Integrations → Connect → GitLab Issues. Use the full project path, such as group/platform/api, the GitLab HTTPS base URL, token, trigger label denly, and Plan first. Leave 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 GitLab open Project → Settings → Webhooks. Paste the Denly URL and inbound secret into Secret token, enable Issues events and notes/comments, save, and run Test → Issues events. Self-managed GitLab must be publicly reachable over HTTPS.
4. Test and troubleshoot
Add denly to an issue and inspect Recent events. Processed creates a task; Skipped means the project, label, assignee or create rule declined it. An empty list means X-Gitlab-Token is wrong; GitLab's webhook page keeps its own delivery log. Notes containing #denly revise linked tasks.