Bring Stripe customer context into a Callingly lead follow-up
Give your next lead conversation a clearer starting point with the customer details already in Stripe.
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 returning lead can force you to search Stripe and Callingly separately before you know what to say next.
- Reduces app switching before a follow-up
- Surfaces existing customer information for context
- Helps avoid treating a returning customer like a brand new contact
Setup
Build it in a few focused steps.
- 1Connect Callingly and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, or describe it to Notis from any channel.
- 3In one instruction, ask Notis to retrieve the Stripe customer using an available customer ID and summarize relevant details for the follow-up.
- 4Choose a webhook trigger and select where run reports should go.
- 5Test with one real lead that has a Stripe customer ID.
Questions about this workflow
Can this find a Stripe customer from a phone number alone?
The selected Stripe action retrieves a customer by unique customer ID. Supply that ID in the request or lead context.
What if the lead has no Stripe customer ID?
Notis needs a usable customer ID to retrieve details. Provide it in the incoming request or handle the lead without a Stripe lookup.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Callingly to Stripe. A trigger fires from one place; an action lands in another.
Callingly 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.
Callingly 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.