Get the Stripe refund details needed for follow-up
When someone asks about a refund, include its refund ID in the handoff and get the record details summarized before replying.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Retrieve a refund
Retrieves details for an existing stripe refund using its unique `refund id`.
Why this helps
Responding to refund questions takes longer when the team has to search for the exact transaction before they can answer.
- Ground refund follow-up in the exact Stripe refund record.
- Reduce manual searching during customer support work.
- Highlight cases where the refund ID or customer context is missing.
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 which refund details to summarize and how to frame the follow-up context.
- 4Pick the Notis webhook trigger and choose where run reports should go.
- 5Test with one real refund ID and verify the report matches the Stripe record.
Questions about this workflow
What identifier is required?
Provide the Stripe refund ID in the webhook handoff.
Does this create a refund?
No. It retrieves an existing refund's details.
Can it draft a customer reply?
It can summarize the retrieved details for a report. Any customer-facing response should use the channel and workflow you specify separately.
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.