Keep phone context with subscription cancellations
Give cancellation follow-up a little more context by including the available phone number details in the report.
Trigger
Subscription Deleted Trigger
Triggered when a subscription is deleted in Stripe
Action
Get Phone Number Information
Tool to retrieve detailed information about a specific phone number, including reputation, business and carrier details, and ftc complaints. use when the number is in e.164 format and set hlr=true to include hlr data (adds 1-3 seconds to response).
Why this helps
Cancellation follow-up can get scattered when account and contact details live in separate tools.
- Attach available phone number information to the cancellation event report.
- Keep follow-up context in one place for later review.
- Avoid inventing contact data when the event lacks a usable number.
Setup
Build it in a few focused steps.
- 1Connect Stripe and Callerapi once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel what outcome you want.
- 3In one instruction, ask Notis to look up any available E.164 phone number from the subscription deletion event and summarize the returned details, noting when no usable number exists.
- 4Pick the Stripe Subscription Deleted trigger and choose where run reports should go.
- 5Test with one real deleted subscription event that includes an E.164 phone number.
Questions about this workflow
Does Callerapi tell me why a subscription was deleted?
No. This action retrieves phone number information. Use the Stripe event data for any deletion details it actually includes.
Can this automatically contact the customer?
No. The available Callerapi action retrieves information and does not place calls or send messages.
What if I do not have an E.164 number?
The instruction can tell Notis to skip the lookup and note that a usable phone number was not available.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Callerapi. A trigger fires from one place; an action lands in another.
Stripe triggers
Callerapi actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Phone Number Information
Tool to retrieve detailed information about a specific phone number, including reputation, business and carrier details, and ftc complaints. use when the number is in e.164 format and set hlr=true to include hlr data (adds 1-3 seconds to response).
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get User Information
Tool to retrieve information about the authenticated user, including email and credit usage details. use after authentication to fetch credits spent, monthly allocation, and credits left.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Product Created Trigger
Triggered when a product is created in Stripe
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Connect any two apps with Notis in the middle.
Stripe and Callerapi, 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 Callerapi.