Keep Amplitude user context current after checkout
A completed checkout can be a useful customer milestone. Have Notis update available Amplitude user properties so teams can understand product behavior with that context in view.
Trigger
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Action
Update User Properties in Amplitude
Update user properties using amplitude's identify api. this action allows you to: - set or update the user id for a device id - update user properties without sending an event - perform operations on user properties (set, append, etc.) - update user attributes like device info and location
Why this helps
Teams may need to reconcile completed purchases with user context by hand before reviewing product behavior.
- Refresh user context from completed checkout activity
- Reduce manual reconciliation between payment and analytics tools
- Support more informed product analysis
Setup
Build it in a few focused steps.
- 1Connect Stripe and Amplitude once in the Notis portal.
- 2Create an automation in Automations, then choose New Automation and enter a name and prompt.
- 3Tell Notis which available user properties to update in Amplitude when a Stripe checkout completes.
- 4Choose the Stripe Checkout Session Completed trigger and select where run reports should go.
- 5Test the automation with one real completed checkout.
Questions about this workflow
Does this create an Amplitude event?
This workflow uses Amplitude's user properties action to update user attributes. Use a separate event action if you also need to record an event.
What if the checkout does not include a matching Amplitude user identifier?
Notis can only update user properties with identifiers available from the event or supplied by you. Confirm the required identifier is present in your Stripe data.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Amplitude. A trigger fires from one place; an action lands in another.
Stripe triggers
Amplitude actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Check Amplitude Cohort Status
Check the status of a cohort export request. this action allows you to: - poll the status of an in-progress cohort download request - determine if a cohort is ready for download
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Amplitude Event Category
Create a new event category in amplitude. this action allows you to: - create a new event category to organize event types - validate category name before creation key features: - creates event categories for organizing events - returns success/failure status
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Create Amplitude Event Type
Create a new event type in amplitude. this action allows you to: - define a new event type with various properties - associate the event with a category - add metadata like description, tags, and owner key features: - creates trackable events in your amplitude project - supports full event type configuration
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Delete Amplitude Event Category
Delete an event category from amplitude. this action allows you to: - delete an existing event category - remove category organization from events key features: - permanently removes event categories - returns success/failure status
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Delete Amplitude Event Type
Delete an event type from amplitude. this action allows you to: - remove an event type from your project - mark live events as deleted - remove planned events from the tracking plan key features: - different behavior based on event status (live, planned, etc.) - returns success/failure status
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Request Amplitude Cohort
Get a single cohort by id and initiate download. this action allows you to: - request a specific cohort from amplitude - optionally include user properties in the response - start the asynchronous download process key features: - supports filtering by specific user properties - returns a request id used for polling status and downloading - supports eu data residency
Product Created Trigger
Triggered when a product is created in Stripe
Get Amplitude Event Categories
Get event categories from amplitude. this action allows you to: - get all event categories in your project - get a specific category by name
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Get Amplitude Event Type
Get a specific event type from amplitude by name. this action allows you to: - retrieve detailed information about a single event type - get all properties and metadata for the event key features: - retrieves comprehensive event type details - returns metadata like category, description, and settings - supports lookup by exact event name
Connect any two apps with Notis in the middle.
Stripe and Amplitude, 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 Amplitude.