Customer Created
Receive customer.created events after activation. Existing customers and later edits are not imported or synchronized; creation is not payment or subscription confirmation.
Workflow template
Create an empty Google Drive document folder for each new Stripe customer. Name it with the customer ID and supplied name, inside your selected parent or My Drive.
How it works
Receive customer.created events after activation. Existing customers and later edits are not imported or synchronized; creation is not payment or subscription confirmation.
Create an empty folder named Stripe {customer ID} - {customer name}. Keep the ID even when the name is blank, using the optional parent folder or My Drive when no parent is chosen.
The result
Stripe cus_example_drive - Lukas Weiß
Type: Empty folder Location: Selected parent folder, or My Drive when no parent is selected Name source: Stripe customer ID and supplied customer name
Fictional sandbox customer. No documents, invoices, payment details or email addresses are copied. The folder is not attached back to Stripe and no sharing-permission change is included.
Before activation
Choose Stripe sandbox first and retain Customer Created. Use a new fictional customer record for testing rather than expecting existing customers to be imported.
Connect Google Drive and optionally select a writable parent folder. Leaving it empty saves to My Drive. Review destination access because the name can contain a customer’s name and Stripe identifier.
Activate, wait for Connected and create a fictional sandbox customer. Check the empty folder’s name and location. The customer ID remains in the name even if the source customer name is absent.
The folder records a customer creation only. It does not prove payment or a subscription. Existing customers and later profile edits are not imported, and subsequent name changes do not rename the folder.
The result is an empty folder. Invoices, payment details, email addresses, tax IDs and metadata are not copied, and no folder link is attached to Stripe. Access follows the destination folder without a sharing-permission action.
Matching names are not reused. There is no existing-folder lookup. A manual rerun can create another folder with the same name; the customer ID provides a source reference rather than a deduplication guarantee.
In My Drive. Choose a writable parent folder if you need another location and review its access. The workflow changes no sharing permissions.
The folder name still includes the Stripe Customer ID. The supplied name is appended when present, without inventing a replacement name.
No. It is empty and triggered by customer.created only. No payment or subscription is confirmed, no invoices or payment details are copied, and the folder is not attached to Stripe.
No. Later changes are not synchronized and there is no existing-folder lookup. A manual rerun can create another folder with the same name.