Skip to content
Notis

Check refund history before responding to an Apilio support request

Give Notis the payment or customer context from a request and quickly see whether Stripe already has a related refund.

Trigger

Webhook received

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

Action

List Refunds

Lists stripe refunds, sorted by creation date descending (newest first), with optional filtering by charge or payment intent and pagination support.

Why this helps

A second refund or an unnecessary customer follow-up can happen when prior refund history is hard to find.

  • Check for existing refund records before responding.
  • Reduce duplicate investigation during support handoffs.
  • Summarize matching refund history for the next action.

Setup

Build it in a few focused steps.

  • 1Connect Apilio and Stripe once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it.
  • 3Tell Notis to use the supplied charge or payment intent context to list related refunds and summarize the results.
  • 4Choose the webhook trigger and select where run reports should go.
  • 5Test with one real support case.

Questions about this workflow

What information makes the refund search useful?

Provide a charge ID or payment intent ID when available, along with relevant Apilio support context.

Will this issue a refund?

No. This workflow only lists refund records.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Apilio to Stripe. A trigger fires from one place; an action lands in another.

Apilio triggers

Stripe actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Confirm payment intent

Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.

ActionInstant

Create Customer

Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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`.

ActionInstant

Create product

Creates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.

ActionInstant

Create Refund

Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.

ActionInstant

Connect any two apps with Notis in the middle.

Apilio 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.