DenlyMattermost
Create tasks from Mattermost slash commands and route them by Mattermost user.
1. Create the Mattermost slash command
In Mattermost open Integrations → Slash Commands → Add Slash Command. Choose the team, set trigger denly, set the Request URL to Denly’s generated URL, and copy the generated command token. Read Mattermost integrations.
2. Create the Denly connection
Open Workspace → Integrations → Connect → Mattermost. Use the team or server ID, the incoming webhook URL for notifications, the command alias, and the channel-to-project mapping. Paste the token from step 1 into Mattermost command token – every command is verified against it, and the secret Denly generates is unused here.
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.
Map keys can be Mattermost user IDs or usernames: the payload carries both, and Denly tries each.
3. Verify the request
Save the command and run /denly fix the failing test. Mattermost sends the command token in the form body. Keep Denly on a public HTTPS URL.
4. Test and troubleshoot
Processed means Denly created the task and replied in the channel; Skipped means the command, project mapping or message text did not match. An empty list means the command token stored in Denly is not the one Mattermost generated.