Add Stripe customer context to a deployment handoff
Include customer IDs in a release or support handoff and get the relevant Stripe customer details back in one report, without searching customer records manually.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Retrieve customer
Retrieves detailed information for an existing stripe customer using their unique customer id.
Why this helps
Release and support teams lose time switching into Stripe to understand which customer a deployment handoff concerns.
- Add Stripe customer context to a release handoff.
- Reduce manual searching when a customer issue is tied to a deployment.
- Flag IDs that are missing or do not return a customer record.
Setup
Build it in a few focused steps.
- 1Connect CircleCI and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Describe how to summarize customer records supplied in the deployment handoff and what details are relevant.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real customer ID and confirm the returned context is appropriate.
Questions about this workflow
Does this find customers from an email address?
This workflow uses the Stripe retrieve customer action, which requires a customer ID. If the handoff only has an email, include a separate lookup step or supply the ID.
Does the automation change customer data?
No. It retrieves customer details for a report and does not update the Stripe record.
What should the webhook send?
Send the customer ID and a short description of the deployment or issue context. Notis cannot derive the affected customer from a CircleCI build because no CircleCI trigger events are available here.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Circleci to Stripe. A trigger fires from one place; an action lands in another.
Circleci 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.
Circleci 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.