Automated Clerk Pending Invitation Chasing
Every morning, WebRun opens Clerk, lists organization invitations still pending, works out how long each has been outstanding and which are close to expiring, groups them by the customer organization that sent them, writes the list into Notion, and texts you the teams stalled mid rollout through Twilio.
How do I find customer team invitations that were never accepted?
WebRun chases stalled Clerk rollouts every morning. It lists organization invitations still pending with their role, days outstanding and expiry risk, groups them by the customer that sent them in a Notion tracker, and texts your success owner which teams are stuck mid rollout today.
- Stalled customer rollouts are visible the next morning
- Invitations get a nudge before they expire
- Nothing is resent or revoked without a person doing it
Built for customer success teams · growth engineers · SaaS founders · developer platform teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
dashboard.clerk.comin a real browser with your saved login - no setup, no API keys. -
1
Clerk - find invitations nobody accepted
clerk.com
WebRun opens Clerk to find invitations nobody accepted. - Open the Clerk dashboard and list organizations with pending invitations
- Capture each invitation with the organization, the role, and the date it was sent
- Work out days outstanding and flag any close to expiry
- Note organizations where the inviter is the only accepted member so far
- Do not resend, revoke or accept an invitation. Those stay human actions
Done when Every pending invitation is listed with its organization, role and days outstanding.
-
2
Notion - group them by customer organization
notion.so
WebRun opens Notion to group them by customer organization. - Open the account tracker in Notion
- Add or update a row per customer organization with its pending invitation count
- List the individual invitations with role and days outstanding under each
- Mark organizations where every invitation is unaccepted as stalled rollouts
- Drop rows that cleared since the last run so the list stays current
Done when Pending invitations are grouped by customer in Notion with stalled rollouts marked.
-
3
Twilio - text you the stalled rollouts
twilio.com
WebRun opens Twilio to text you the stalled rollouts. - Text the customer success owner the organizations stalled mid rollout
- Lead with any invitation about to expire and the days left
- Keep it to a count plus the two or three accounts worth a call today
- Only message your own team numbers. Never text an end user
Done when The owner knows which customer teams are stuck this morning.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it resend invitations to end users?
No. WebRun only reports which invitations are still pending. Resending, revoking, or emailing the invitee is done by your team, so no end user receives anything from the automation.
Does it read user data?
It reads only what the invitation list shows: the organization, the invited role, and the dates. It does not open user profiles or export personal details into the Notion tracker.
What counts as a stalled rollout?
An organization where invitations have gone out but none have been accepted, or where every pending invite is past your day threshold. Those are listed first because the account is stuck.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.