Connect Hotjar to Stripe in two minutes.
Real-time triggers from Hotjar, ready-made actions in Stripe. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Hotjar.
- Hotjar New FeedbackWebhook
- Hotjar Survey ResponseWebhook
Workflows do something in Stripe, instantly.
- Cancel SubscriptionAPI
- Create ChargeAPI
- Create Checkout SessionAPI
- Create CouponAPI
- Create CustomerAPI
- Create Payment IntentAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Hotjar, do it in Stripe.
2 Hotjar triggers wired to 31 Stripe actions. Most-used pairing: Hotjar New Feedback → Cancel Subscription.
Or fire it the other way around.
10 Stripe triggers wired to 2 Hotjar actions downstream.
See Stripe → Hotjar →Common Hotjar → Stripe workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a visitor submits the Hotjar Feedback widget. Payload includes rating, text, URL, browser, and the session replay URL. For "frustrated user submitted feedback → create Linear issue with the replay link" workflows.
Fires when a visitor submits the Hotjar Feedback widget. Payload includes rating, text, URL, browser, and the session replay URL. For "frustrated user submitted feedback → create Linear issue with the replay link" workflows.
Fires when a visitor submits the Hotjar Feedback widget. Payload includes rating, text, URL, browser, and the session replay URL. For "frustrated user submitted feedback → create Linear issue with the replay link" workflows.
Fires when a visitor submits the Hotjar Feedback widget. Payload includes rating, text, URL, browser, and the session replay URL. For "frustrated user submitted feedback → create Linear issue with the replay link" workflows.
Fires when someone completes a Hotjar Survey with the answers array. For "NPS detractor submitted → alert CS team" or "feedback by topic → route to right team" workflows.
Fires when someone completes a Hotjar Survey with the answers array. For "NPS detractor submitted → alert CS team" or "feedback by topic → route to right team" workflows.
Fires when someone completes a Hotjar Survey with the answers array. For "NPS detractor submitted → alert CS team" or "feedback by topic → route to right team" workflows.
Fires when someone completes a Hotjar Survey with the answers array. For "NPS detractor submitted → alert CS team" or "feedback by topic → route to right team" workflows.
Connect Hotjar and Stripe in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Hotjar and Stripe
Open Tiny Command, authorize Hotjar and Stripe once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Hotjar trigger
Drop the Hotjar → Hotjar New Feedback trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/hotjar.trigger-new-feedback - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Stripe action
Drop the Stripe → Cancel Subscription action below it. Map fields from the Hotjar payload into the Stripe inputs.
stripe.cancel-subscription - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about Hotjar + Stripe.
How long does it take to connect Hotjar and Stripe on Tiny Command?
Is the Hotjar ↔ Stripe integration real-time?
Can I filter or transform data between Hotjar and Stripe?
What Hotjar events can trigger a Stripe workflow?
Do I need a paid plan to use Hotjar with Stripe?
What if I want Stripe → Hotjar instead?
Other apps that pair well with Hotjar.
Wire Hotjar to Stripe in 2 minutes.
Free tier available. No credit card. No onboarding call.
