feat(clerk): expand Clerk integration with org, membership, moderation, and security tools#5364
feat(clerk): expand Clerk integration with org, membership, moderation, and security tools#5364waleedlatif1 wants to merge 2 commits into
Conversation
…n, and security tools - fix 4 validate-integration warnings: missing .trim() on org/session IDs, incomplete session-status dropdown, missing list_users/list_organizations filter subBlocks - add organization update/delete tools - add organization membership CRUD (list, add, update role, remove) - add organization invitation create/list - add user ban/unban/lock/unlock and OAuth access token retrieval - add allowlist/blocklist identifier management - add JWT template list/get - add actor token create/revoke (impersonation) - add matching webhook triggers for session ended/removed/revoked, organization updated/deleted, and membership updated/deleted - wire all 23 new tools into the block, tool registry, and trigger registry
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
PR SummaryHigh Risk Overview New workflow capabilities include user moderation (ban/unban/lock/unlock), OAuth access token retrieval, full organization update/delete, membership CRUD and invitations, allowlist/blocklist identifiers, JWT template list/get, and actor tokens for impersonation. The Clerk block’s operation dropdown, conditional subBlocks, Webhook triggers now cover Smaller fixes: Reviewed by Cursor Bugbot for commit 818b5f2. Configure here. |
Greptile SummaryThis PR significantly expands the Clerk integration by adding 23 new tools and 8 new webhook trigger types. It closes coverage gaps across organization management, membership CRUD, invitations, user moderation, allow/blocklist management, JWT templates, and actor tokens, while also fixing pre-existing validation gaps (missing
Confidence Score: 5/5Safe to merge — all 23 new tools follow the established pattern with correct endpoint URLs, proper nullable field handling, and consistent error propagation; the block param mapping is complete and the trigger registry is fully wired. The change is a large but mechanically regular feature expansion: each new tool file, trigger file, and block subBlock follows the same well-tested pattern as the existing Clerk integration. API shape decisions (bare-array vs. paginated responses) are explicitly justified and consistent with the codebase. No logic or data-flow issues were found after full review. No files require special attention. Important Files Changed
Reviews (2): Last reviewed commit: "feat(clerk): expand Clerk integration wi..." | Re-trigger Greptile |
|
@cursor review |
|
@cursor review |
There was a problem hiding this comment.
✅ Bugbot reviewed your changes and found no new issues!
Comment @cursor review or bugbot run to trigger another review on this PR
Reviewed by Cursor Bugbot for commit 818b5f2. Configure here.
- remove dead limit/offset params from list_blocklist_identifiers (Clerk API accepts zero params on this endpoint, verified across 6 spec versions) - expose publicMetadata on OAuth access token output (was silently dropped) - expose inviter email/first/last name (public_inviter_data) on organization invitation create/list outputs - add missing orderBy param to list_organization_invitations
Summary
.trim()on organization/session ID params, an incomplete session-status dropdown (missing Removed/Replaced), and missing List Users/List Organizations filter subBlocks that the tools already supported but the UI didn't exposeproviderUserIdfield that would always resolve tonull, a missingclerk_create_organizationcondition on the metadata subBlocks, and several output-catalog completeness gaps including anexpiresAt/expireAtnaming mismatch for sessions)Type of Change
Testing
bun run lint, full-projecttsc --noEmit, andbun run check:api-validation:strictall pass cleanclerk.test.tswebhook provider suite passes (6/6)@clerk/backendSDK source across 4 independent verification passesChecklist