Give matchday billing requests a faster customer check
A support request starts one workflow that checks the supplied match context and retrieves the referenced Stripe customer for a concise report.
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
Support requests that mix a live match issue and a billing question can force founders to switch between tools and lose context.
- Retrieve the specified Stripe customer during support triage.
- Add relevant match context from API Sports.
- Give the next person a concise report with references.
Setup
Build it in a few focused steps.
- 1Connect API Sports and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for matchday billing support.
- 3In one instruction, specify how to use the supplied match and Stripe customer references and what details to include in the report.
- 4Pick a webhook trigger and choose where run reports should go.
- 5Test with one real support request and valid references.
Questions about this workflow
Does this charge or refund the customer?
No. It retrieves the customer record and reports relevant context.
What information should a support request contain?
Include a Stripe customer ID and enough match details for API Sports to identify the relevant fixture.
Will the report include all customer data?
Specify which details are relevant to the support task, and follow your organization's access practices.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Api sports to Stripe. A trigger fires from one place; an action lands in another.
Api sports 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.
Api sports 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.