Customer Created
Emit an event when Stripe delivers customer.created.
→
Ready-made Workflow
Send new Stripe customers to a Discord channel
Post a Discord notification when a customer is created in Stripe. Connect Stripe and Discord, wait for the Stripe source to show Connected, then choose a Discord text channel. The instant trigger listens only for customer.created events from the connected Stripe account; existing customers and later updates are not imported. Each message contains the customer name, email, Stripe customer ID and live-mode flag. New customers do not necessarily represent a payment or subscription. No payment details, addresses, tax IDs, descriptions or metadata are forwarded. User, role and everyone mentions are disabled, so customer text cannot trigger Discord notifications accidentally. Test with a fictional customer in Stripe sandbox first and choose a channel whose members may see customer names and email addresses. Name and email may be empty when Stripe does not provide them. Includes its own fictional German customer example with no real customer data.
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.
Notify the customer channel
Send rich content, files, a poll, or a reply to a channel.
Before activation
Connect your accounts in the Draft
Stripe
Connect your own Stripe account and review the provider settings used by this Workflow.
Discord
Connect your own Discord 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 Stripe, Discord 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.