Review Stripe customer context for Cardly follow-ups
See the billing context you need alongside outreach follow-up, without repeatedly searching across tools.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Action
Retrieve customer
Retrieves detailed information for an existing stripe customer using their unique customer id.
Why this helps
A founder preparing a customer follow-up may have to switch tools just to confirm the relevant Stripe record.
- Bring customer details into a scheduled follow-up summary.
- Reduce repetitive account lookups before outreach.
- Flag contacts that lack a usable Stripe customer id.
Setup
Build it in a few focused steps.
- 1Connect Cardly and Stripe once in the Notis portal.
- 2Create an automation and give it a clear name.
- 3Tell Notis to review Cardly outreach contacts on the schedule, retrieve Stripe customer details for contacts with a supplied customer id, and summarize missing ids separately.
- 4Choose a recurring schedule and select where run reports should go.
- 5Test with one real contact and confirm the summary uses the intended Stripe customer.
Questions about this workflow
Can this find a customer from a name alone?
The retrieve-customer action needs a unique Stripe customer id. Supply that id or have Notis report that it is missing.
Does this change any Stripe data?
No. This workflow retrieves customer details for follow-up context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Cardly to Stripe. A trigger fires from one place; an action lands in another.
Cardly 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.
Cardly 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.