Bring customer records into entity research
When a specific entity is under review, keep its supplied Stripe customer record close to the Bigdata.com intelligence.
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
Entity research can be harder to use when customer context sits elsewhere and has to be found manually.
- Begin entity research from an HTTP request.
- Retrieve a customer record using its supplied Stripe customer ID.
- Keep entity intelligence and customer context in one run report.
Setup
Build it in a few focused steps.
- 1Connect Bigdata.com MCP and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and set a name and prompt.
- 3In one instruction, ask Notis to research the entity with Bigdata.com MCP and retrieve the Stripe customer record for the customer ID included in the request.
- 4Choose a Notis webhook trigger and a report channel.
- 5Test with one real entity and valid customer ID.
Questions about this workflow
Can it find the right Stripe customer from an entity name alone?
This workflow uses Retrieve customer, which requires the unique Stripe customer ID. Provide that ID; entity names alone may not uniquely identify a customer.
Does the customer record confirm an entity relationship?
No. Bigdata.com research and Stripe customer details are distinct sources. Review them together without assuming one proves the other.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bigdata.com MCP to Stripe. A trigger fires from one place; an action lands in another.
Bigdata.com MCP 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.
Bigdata.com MCP 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.