Create a Stripe customer from a Cdr platform request
Keep customer setup moving when a carbon removal request arrives, without switching tools to create the Stripe record.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Customer
Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
Why this helps
A new customer request can stall while someone copies contact details into Stripe.
- Creates a Stripe customer record from an incoming request.
- Reduces repeated entry of customer details.
- Reports missing details for a person to resolve.
Setup
Build it in a few focused steps.
- 1Connect Cdr platform and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis: When a Cdr platform customer registration request arrives, create a Stripe customer from the supplied details and report anything required that is missing.
- 4Choose notis_webhook as the trigger and choose where run reports should go.
- 5Test with one real registration request and review the created customer.
Questions about this workflow
Does the request need to include an email?
An email is highly recommended for Stripe customer communications. The run report can call out when it is missing.
Will this create a subscription too?
No. This workflow creates a customer record only.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cdr platform to Stripe. A trigger fires from one place; an action lands in another.
Cdr platform triggers
Stripe actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel subscription
Cancels a customer's active stripe subscription at the end of the current billing period, with options to invoice immediately for metered usage and prorate charges for unused time.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Confirm payment intent
Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.
Create Customer
Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
Create an invoice
Creates a new draft stripe invoice for a customer; use to revise an existing invoice, bill for a specific subscription (which must belong to the customer), or apply detailed customizations.
Create payment intent
Creates a stripe paymentintent to initiate and process a customer's payment; using `application fee amount` for a connected account requires the `stripe-account` header.
Create a price
Creates a new stripe price for a product, defining its charges (one-time or recurring) and billing scheme; requires either an existing `product` id or `product data`.
Create product
Creates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.
Create Refund
Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.
Connect any two apps with Notis in the middle.
Cdr platform and Stripe, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Stripe.