Clerk logo

Ready-made Workflow

Tag a new Clerk user for onboarding

Start from the native Clerk user.created event and merge a public onboarding tag into that user's metadata. Connect the same Clerk instance to the Trigger and Actions. In Connected accounts, copy its webhook endpoint URL into Clerk Configure → Developers → Webhooks, select user.created, and save that endpoint's Signing Secret in FastHook. Review the public metadata field and value before activation. The example sets fasthook_onboarding to new and grants no permissions. Existing users are not imported. Repeated delivery merges the same value; subsequent user.updated events do not retrigger this template. Pause stops local delivery; disable the dedicated remote endpoint manually when finished. No account IDs, real resource IDs, secrets or private webhook URLs are included.

Use this templateCreates a new Draft · no credentials copied

What gets copied

The working graph, not another user's secrets

FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.

Step 1 · Clerk · Trigger

Clerk user created

Native Clerk event. Requires a Clerk Dashboard endpoint and its per-endpoint Svix Signing Secret in the connected account. Remote endpoints are configured and disabled in Clerk.

Step 2 · Clerk

Merge onboarding tag

Update a user's metadata attributes by merging existing values with the provided parameters. This endpoint behaves differently than the *Update a user* endpoint. Metadata values will not be replaced entirely. Instead, a deep merge will be performed. Deep means that any nested JSON objects will be merged as well. You can remove metadata keys at any level by setting their value to `null`.

Step 3 · Clerk

Read the updated user

Retrieve the details of a user

Before activation

Connect your accounts in the Draft

1

Clerk

Connect your own Clerk account and review the provider settings used by this Workflow.

Explore connected apps

Questions

Template FAQ

Does the template copy someone else's credentials?

No. FastHook creates a disconnected Draft. Connect your own Clerk accounts before activation.

Can I change the Steps and mappings?

Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.

What is copied into my workspace?

FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.

When does the Workflow start running?

Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.