Trigger event-based messaging from Stripe, Clerk, Supabase
Knock data sources enable you to ingest event data from any tool to trigger messaging in a few clicks—no code required. Connect pre-built sources like Stripe, Clerk, Supabase, PostHog, and WorkOS, or map any custom webhook to workflows, audiences, and user updates in a few clicks. Knock handles verification, transformation, and action mapping so you can launch lifecycle and transactional messaging faster.
Over the years, I’ve found that most teams responsible for messaging are most limited by their lack of access to real-time data.
The hard part is not designing the email, push, or in-app message… It’s getting the right event data from the rest of your stack into your messaging system in a way that is reliable, flexible, and fast enough to actually use.
We’re launching data sources today to solve that problem.
With data sources, you can connect events from tools like Stripe, Clerk, Supabase, PostHog, and WorkOS directly into Knock and map them to actions like triggering workflows, updating users, or syncing audiences. You can leverage pre-configured data sources, or map in custom tools, too.
Now, when something important happens anywhere in your stack, it’s easy to turn that into a messaging experience:
Send an ‘update billing info’ alert when a Stripe payment fails.
Trigger an onboarding sequence when a user is created in WorkOS.
Create user segments based on product usage activity in Posthog.
A lot of messaging software still assumes your data arrives in exactly the right format, from a narrow set of supported integrations. That breaks down quickly in the real world. Every company has a different stack, different schemas, and different events.
What makes data sources useful is not just that it connects tools. It removes a lot of the work that usually sits between the event and the action:
no custom middleware just to reshape payloads
no separate verification layer for sensitive events
no waiting on engineering for every new source or mapping
Data sources is a step toward a more flexible model: connect whatever emits events, verify and transform the payload, and map it to the action you want in a few clicks.
Check it out, and tell us what you think. What other tools do you plan to connect?
About Knock data sources on Product Hunt
“Trigger event-based messaging from Stripe, Clerk, Supabase”
Knock data sources launched on Product Hunt on April 10th, 2026 and earned 123 upvotes and 6 comments, placing #11 on the daily leaderboard. Knock data sources enable you to ingest event data from any tool to trigger messaging in a few clicks—no code required. Connect pre-built sources like Stripe, Clerk, Supabase, PostHog, and WorkOS, or map any custom webhook to workflows, audiences, and user updates in a few clicks. Knock handles verification, transformation, and action mapping so you can launch lifecycle and transactional messaging faster.
On the analytics side, Knock data sources competes within Customer Communication, Marketing and Developer Tools — topics that collectively have 986.3k followers on Product Hunt. The dashboard above tracks how Knock data sources performed against the three products that launched closest to it on the same day.
Who hunted Knock data sources?
Knock data sources was hunted by fmerian. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
fmerian
Over the years, I’ve found that most teams responsible for messaging are most limited by their lack of access to real-time data.
The hard part is not designing the email, push, or in-app message… It’s getting the right event data from the rest of your stack into your messaging system in a way that is reliable, flexible, and fast enough to actually use.
We’re launching data sources today to solve that problem.
With data sources, you can connect events from tools like Stripe, Clerk, Supabase, PostHog, and WorkOS directly into Knock and map them to actions like triggering workflows, updating users, or syncing audiences. You can leverage pre-configured data sources, or map in custom tools, too.
Now, when something important happens anywhere in your stack, it’s easy to turn that into a messaging experience:
Send an ‘update billing info’ alert when a Stripe payment fails.
Trigger an onboarding sequence when a user is created in WorkOS.
Create user segments based on product usage activity in Posthog.
A lot of messaging software still assumes your data arrives in exactly the right format, from a narrow set of supported integrations. That breaks down quickly in the real world. Every company has a different stack, different schemas, and different events.
What makes data sources useful is not just that it connects tools. It removes a lot of the work that usually sits between the event and the action:
no custom middleware just to reshape payloads
no separate verification layer for sensitive events
no waiting on engineering for every new source or mapping
Data sources is a step toward a more flexible model: connect whatever emits events, verify and transform the payload, and map it to the action you want in a few clicks.
Check it out, and tell us what you think. What other tools do you plan to connect?