Turn Clerk signups into onboarding emails
Send Clerk webhooks to Loops and every new user becomes a contact. Signups, profile changes, deletions, and waitlist entries can each start a workflow.
user.createduser.updateduser.deletedwaitlistEntry.created+ 1 moreWelcome aboard, Sam
Three quick steps and you’re set up.
- 1Create your first project
- 2Invite your team
- 3Connect your data
Start an onboarding sequence when someone signs up, from the Onboarding drip template.
Waitlist entries sync too. Give them a user group so they’re easy to email when you open up.
When someone changes their name or email in Clerk, the matching contact updates in Loops.
Setup is a webhook in Clerk and its secret in Loops. The Clerk docs walk through each step.
Create a webhook endpoint in Loops, then add its URL in Clerk and pick the events to send.
Does this change Clerk’s sign-in emails?
No. Loops reads Clerk webhook events to sync contacts and start workflows. Clerk keeps sending its own authentication emails.
How are Clerk users matched to contacts?
By Clerk user ID. If no contact has that ID, Loops creates one with the user’s email address and name. Waitlist entries sync by email, and the user ID is added once the person finishes signing up.
Which Clerk events does Loops accept?
user.created, user.updated, user.deleted, waitlistEntry.created, and waitlistEntry.updated. Loops ignores anything else.
Can I send product events for Clerk users?
Yes. Send events from your backend with the Loops API and pass the Clerk user ID as userId, so each event lands on the same contact.
What happens when a user is deleted in Clerk?
Turn on user.deleted and choose whether Loops unsubscribes or deletes the matching contact. The event can also start a workflow.
Is there a free plan?
Yes. The free plan includes unlimited contacts and up to 4,000 emails to your first 1,000 contacts in any rolling 30-day window, marketing and transactional combined. Upgrade to send to more subscribed contacts.