Turn a deployment incident impact list into Stripe refunds
When a release causes customer harm, send Notis the affected customer and payment details. It can check each case against your refund policy and create the approved Stripe refunds.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Refund
Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.
Why this helps
Incident follow-up often means tracking down affected customers, payment records, and refund decisions across separate tools.
- Handle customer remediation from one incident handoff.
- Use a documented refund policy to guide each decision.
- Receive a run report that highlights missing payment details or review cases.
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 the incident review and approved refund outcome in one plain-language instruction, including your refund policy.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real, low-risk example and confirm the report and Stripe refund.
Questions about this workflow
Does CircleCI provide the trigger for this workflow?
CircleCI has no trigger events in this package. A Notis webhook starts the automation when it receives an HTTP request.
What information should the webhook include?
Provide the affected customer's Stripe charge or payment intent identifier, the requested refund amount if partial refunds are allowed, and enough incident context to apply your policy. Notis cannot infer which customers were affected.
Can the automation decide refund eligibility on its own?
It can apply a policy you provide, but it should flag cases where impact, eligibility, or payment identifiers are unclear for review.
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.