Canny
Live audit of your Canny boards — confirms a feedback channel actually exists for users, and that it hasn't gone cold.
Why this matters
Canny extends the Usable pillar from “can users reach value quickly” to “can users tell you what’s missing?” The two failure modes that hurt: Canny is connected but no public board exists (so there’s no place for users to actually submit feedback), and boards exist but the last post is months old (the feedback channel has gone cold — users stopped submitting, or were never told it existed).
Connect Canny
Mint a Canny API key.
Canny → Settings → API → Show API key (or + New API key on accounts that scope per-key). Canny’s API key has read access across the workspace.
Paste into PulseLight.
From the project page, click the gear icon → Connected platforms → Canny. Paste the key. We probe the API once to confirm and surface your board list back.
First scan.
The next scan includes the Canny Connected Check findings — rolled up into the Usable pillar.
What we verify
At least one public board exists —
CONN-CANNY-BOARDS-001Canny is connected but no public board exists — the account is in place but users have nowhere to actually submit feedback. Common after a Canny trial where the founder set up the account but never published a board.
Feedback isn’t stale —
CONN-CANNY-STALE-001Boards exist with posts, but the most recent post is more than 60 days old. The feedback channel has gone cold — either users have stopped engaging (worth fixing) or they were never told the board existed (worth fixing differently). Either way, the founder can’t claim the feedback loop is working.
Privacy + scope
Your API key is encrypted at rest with KMS envelope encryption and decrypted only at scan time. We read board metadata and post timestamps. We never read post content, never read user records, never create or modify any content. Revoke the key in Canny’s Settings → API at any time; the next scan reports the integration as revoked.