Keep Stripe customer details aligned with Algolia
Send Notis a customer identifier. It can search Algolia for the corresponding record and update the Stripe customer when the record includes a reliable Stripe customer id.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Update Customer
Updates an existing stripe customer, identified by customer id, with only the provided details; unspecified fields remain unchanged.
Why this helps
Customer details can become stale when updates are recorded in one system and not carried over to Stripe.
- Use Algolia customer records as the lookup source for updates.
- Update only customer details present in the source record.
- Report when a matching Stripe customer id is unavailable.
Setup
Build it in a few focused steps.
- 1Connect Algolia and Stripe once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for customer record updates.
- 3Tell Notis to search the chosen Algolia index for the customer identified by the webhook, use the Stripe customer id in the record to update available details, and report missing or ambiguous matches.
- 4Choose a webhook trigger and report channel.
- 5Test with one real customer record and inspect the Stripe customer update.
Questions about this workflow
What links an Algolia record to a Stripe customer?
The record should include a reliable Stripe customer id. If it does not, the automation should report that it cannot safely identify the customer.
Will absent fields clear existing Stripe values?
The Stripe update action changes only provided details. The prompt should tell Notis to use only values present in the matching Algolia record.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Algolia to Stripe. A trigger fires from one place; an action lands in another.
Algolia 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.
Algolia 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.