Keep Apollo contacts current when a payment fails
Give your team a clear starting point for a billing conversation by updating the matching Apollo contact when Stripe reports a failed payment.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
Update Apollo contact
Updates specified attributes of an existing apollo.io contact, identified by `contact id`; requires at least one other attribute to be provided for modification.
Why this helps
A failed payment can disappear into Stripe while the account owner stays unaware and misses the chance to follow up.
- Make payment issues visible in the contact record.
- Help the account owner follow up with relevant billing context.
- Reduce manual checks across Stripe and Apollo.
Setup
Build it in a few focused steps.
- 1Connect Stripe and Apollo once in the Notis portal.
- 2Create an automation in the portal or tell Notis the outcome you want in plain language.
- 3Ask Notis to find the matching Apollo contact and record the payment failure context; pick the Stripe Payment Intent Failed trigger.
- 4Choose where run reports go, then test with one real failed payment.
Questions about this workflow
What if the failed payment does not identify an Apollo contact?
Notis can only update a contact it can match from the event data. Ask it to report unmatched payments for review.
Does this retry the Stripe payment?
No. This workflow updates Apollo only; it does not retry or change the payment.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Apollo. A trigger fires from one place; an action lands in another.
Stripe triggers
Apollo actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Contacts to Sequence
Adds contacts to a specified apollo email sequence by initiating an asynchronous background job and returning its details.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Bulk organization enrichment
Enriches data for up to 10 organizations simultaneously by providing a list of their base company domains (e.g., 'apollo.io', not 'www.apollo.io').
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Bulk people enrichment
Use to enrich multiple person profiles simultaneously with comprehensive data from apollo's database.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Bulk update account stage
Bulk updates the stage for specified existing apollo.io accounts, moving them to a valid new account stage.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Create an Apollo account
Creates a new account in apollo.io; a new record is created even if a similar account exists, and provided `owner id` or `account stage id` must be valid existing ids.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Create Apollo contact
Creates a new contact in apollo.io; use `account id` to link to an organization and `contact stage id` for sales stage, noting that apollo does not perform automatic deduplication.
Product Created Trigger
Triggered when a product is created in Stripe
Create Apollo deal
Creates a new sales opportunity (deal) in apollo.io; all provided ids (`owner id`, `account id`, `opportunity stage id`) must be valid existing apollo identifiers.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Create Apollo Task
Creates a distinct apollo.io task for each contact id in contact ids, assigning them to user id; this action is not for free plan users and repeated calls create duplicate tasks.
Connect any two apps with Notis in the middle.
Stripe and Apollo, 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 Apollo.