Customer Created
Receive customer.created events from the connected Stripe account after activation. Existing customers and later updates are not imported, and creating a customer record does not establish payment.
Workflow template
Announce newly created Stripe customers in Discord. Include name, email, customer ID and live mode, with mentions and automatic embeds disabled; customer creation alone does not confirm a payment or subscription.
How it works
Receive customer.created events from the connected Stripe account after activation. Existing customers and later updates are not imported, and creating a customer record does not establish payment.
Post name, email, customer ID and event livemode to your chosen text channel. Disable user, role and everyone mentions and suppress embeds; name and email can be blank when absent in Stripe.
The result
New Stripe customer Name: Mara Hoffmann Email: mara.hoffmann@example.com Customer ID: cus_example_hoffmann Live mode: false
Fictional sandbox customer. The message is not a payment receipt or subscription confirmation. Name and email are copied when supplied; no Stripe record URL is added.
Before activation
Select Stripe sandbox for the first test and retain Customer Created. Activate when ready and wait for the source to show Connected before creating the fictional customer.
Connect the destination text channel through its webhook; no bot installation is required. Select a channel whose members may see customer names and email addresses, and retain disabled mentions and suppressed embeds.
Create a new sandbox customer after the source is Connected and compare name, email, ID and Live mode=false in Discord. Do not treat that notice as evidence of payment or a subscription.
A customer record is not a paid conversion. The source watches customer.created only. Existing customers and later profile changes are not imported; payment and subscription events are separate.
Name and email are optional source fields. They can be blank when Stripe does not provide them. No payment details, addresses, tax IDs, descriptions or metadata are copied. Destination readers still receive any supplied name and email.
Discord notification controls stay enabled. The prepared allowed-mentions setting disables user, role and everyone mentions, and embeds are suppressed. There is no existing-message update step; a manual rerun can send another notice.
No. Connect the destination text channel through its webhook. Select it in the action and keep mentions disabled and embeds suppressed.
No. customer.created means a customer record was created. It does not confirm a payment or subscription, and later updates are not imported.
Those fields can be absent in Stripe. The template copies them as supplied without inventing values. Payment details, addresses, tax IDs, descriptions and metadata are not forwarded.
The prepared settings disable user, role and everyone mentions and suppress automatic embeds. Keep them when editing the message; choose a channel appropriate for the name and email data.