See Stripe customer context alongside Canny feedback
Give feedback triage more useful context by retrieving the Stripe customer record named in a Canny event and including available details in the run 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
A feature request may lack the billing context needed to prioritize follow-up, forcing founders to search Stripe manually.
- Bring available Stripe customer details into the feedback run report.
- Reduce manual customer lookups during feature triage.
Setup
Build it in a few focused steps.
- 1Connect Canny and Stripe once in the Notis portal.
- 2Create an automation in the portal under Automations, New Automation, and name it.
- 3Tell Notis: When a Canny feedback request includes a Stripe customer ID, retrieve that Stripe customer and summarize the available details in the run report.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real Canny request that contains a valid Stripe customer ID.
Questions about this workflow
Does this workflow change the Stripe customer?
No. It retrieves customer details and can summarize the available response in the run report.
What if Canny does not include a Stripe customer ID?
The retrieve action requires a customer ID. Supply it in the incoming event or have your instruction report that the identifier is missing.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Canny to Stripe. A trigger fires from one place; an action lands in another.
Canny 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.
Canny 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.