Add company context to failed payment follow-up
A failed payment is easier to resolve when you can quickly see who the customer is and where they work. Let Notis enrich available customer details in Datagma as soon as Stripe reports a failed payment intent.
Trigger
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Action
Enrich Person or Company
Enrich person or company data using LinkedIn URLs, emails, domains, or names. Returns enriched data including: contact information, LinkedIn profiles, company details, work experience, education, phone numbers (with phoneFull), and company metrics. Input types: LinkedIn profile URL (~100% success), email (~60% success), name+company (~90% success), company domain/name, or SIREN number (French companies).
Why this helps
Payment failures interrupt work, and looking up customer context separately makes timely follow-up easy to forget.
- See enriched person or company details alongside a payment failure.
- Reduce manual research before contacting a customer.
- Keep payment recovery follow-up moving with less context switching.
Setup
Build it in a few focused steps.
- 1Connect Stripe and Datagma once in the Notis portal.
- 2Create a new automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis to enrich the customer or company associated with a failed payment intent in one plain-language instruction.
- 4Choose the Stripe Payment Intent Failed trigger and select where run reports should go.
- 5Test the automation with one real failed payment example.
Questions about this workflow
What information does Datagma need to enrich a customer?
Datagma can enrich people or companies using supported inputs such as email, company domain, name, or LinkedIn URL. The Stripe event must provide a usable identifier for the lookup.
Does this recover or retry the failed payment?
No. This workflow adds context through Datagma enrichment. It does not retry charges or contact the customer.
What if Stripe does not provide enough identifying information?
Notis can only pass along available details. Provide a usable email, company domain, name, or LinkedIn URL in the event data for the best chance of a useful result.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Datagma. A trigger fires from one place; an action lands in another.
Stripe triggers
Datagma actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Detect Job Change
Tool to detect if a contact changed jobs. Use when verifying a contact’s current employment details by email.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Enrich Person or Company
Enrich person or company data using LinkedIn URLs, emails, domains, or names. Returns enriched data including: contact information, LinkedIn profiles, company details, work experience, education, phone numbers (with phoneFull), and company metrics. Input types: LinkedIn profile URL (~100% success), email (~60% success), name+company (~90% success), company domain/name, or SIREN number (French companies).
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Find Work Email
Find verified work email address for a person using their name and company. Returns a professionally verified email address with validation metadata including SMTP checks and MX records. Requires either fullName or firstName+lastName, plus company domain or LinkedIn company slug.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Get Credits
Get the current credit balance for the authenticated Datagma API account. Use this to check how many API credits remain before making enrichment calls.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Get Twitter Profile By Email
Retrieve Twitter account information associated with an email address. This action looks up Twitter username and display name for a given email address using Datagma's enrichment database. Returns Twitter username, display name, and the queried email if a match is found, or status 'NOT_FOUND' if no Twitter account is associated with the email. Use this when you need to: - Find someone's Twitter handle from their email address - Verify if an email has an associated Twitter account - Enrich contact data with social media information
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Get Twitter Profile by Username
Enrich Twitter profile data using Datagma's database. Returns contact information (email), social media profiles (LinkedIn, Facebook, GitHub), and professional details (skills, interests, industry) associated with a Twitter username. Note: Not all usernames are in Datagma's database. A 'not found' response (code 5) indicates the username hasn't been indexed yet.
Product Created Trigger
Triggered when a product is created in Stripe
Reverse Phone Lookup
Tool to reverse-lookup information associated with a phone number. Use when you have a phone number and need associated details (e.g., carrier, location).
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Search Phone Numbers
Find mobile phone numbers using email address and/or LinkedIn profile URL. Returns list of phone numbers with confidence scores and optional WhatsApp verification. Best results when both email and LinkedIn URL are provided.
Connect any two apps with Notis in the middle.
Stripe and Datagma, 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 Datagma.