- Integrations
- /
- Help Scout
- /
- with Stripe
Connect Help Scout to Stripe in two minutes.
Real-time triggers from Help Scout, ready-made actions in Stripe. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Help Scout.
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 Help Scout, do it in Stripe.
5 Help Scout triggers wired to 31 Stripe actions. Most-used pairing: Help Scout Conversation Assigned → Cancel Subscription.
Or fire it the other way around.
10 Stripe triggers wired to 4 Help Scout actions downstream.
See Stripe → Help Scout →Common Help Scout → Stripe workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a conversation is assigned (or reassigned) to a user. Useful for "new assignment → ping the user in Slack with context" workflows.
Fires when a conversation is assigned (or reassigned) to a user. Useful for "new assignment → ping the user in Slack with context" workflows.
Fires when a conversation is assigned (or reassigned) to a user. Useful for "new assignment → ping the user in Slack with context" workflows.
Fires when a conversation is assigned (or reassigned) to a user. Useful for "new assignment → ping the user in Slack with context" workflows.
Fires when a new conversation lands in a mailbox. Payload includes customer, subject, message body, channel (email, chat, social). The base hook for "new inbound → route to right team" workflows.
Fires when a new conversation lands in a mailbox. Payload includes customer, subject, message body, channel (email, chat, social). The base hook for "new inbound → route to right team" workflows.
Fires when a new conversation lands in a mailbox. Payload includes customer, subject, message body, channel (email, chat, social). The base hook for "new inbound → route to right team" workflows.
Fires when a new conversation lands in a mailbox. Payload includes customer, subject, message body, channel (email, chat, social). The base hook for "new inbound → route to right team" workflows.
Fires when a conversation moves between mailboxes (e.g., Support → Billing). Useful for cross-team handoff workflows that need to notify the new owning team.
Connect Help Scout and Stripe in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Help Scout and Stripe
Open Tiny Command, authorize Help Scout and Stripe once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Help Scout trigger
Drop the Help Scout → Help Scout Conversation Assigned trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/helpscout.trigger-conversation-assigned - 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 Help Scout 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 Help Scout + Stripe.
How long does it take to connect Help Scout and Stripe on Tiny Command?
Is the Help Scout ↔ Stripe integration real-time?
Can I filter or transform data between Help Scout and Stripe?
What Help Scout events can trigger a Stripe workflow?
Do I need a paid plan to use Help Scout with Stripe?
What if I want Stripe → Help Scout instead?
Other apps that pair well with Help Scout.
Wire Help Scout to Stripe in 2 minutes.
Free tier available. No credit card. No onboarding call.