Bring Basin intake context into completed checkout follow-up
A completed checkout can cue Notis to retrieve the related Basin submissions and summarize the context your team needs next.
Trigger
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Action
Get Submissions
Tool to retrieve all submissions for a specific form. use when you need to list entries after obtaining the form id.
Why this helps
Payment and form responses are separated, leaving someone to search both systems before following up.
- Retrieve form responses after a checkout completes
- Summarize available intake context for follow-up
- Cut down on switching between payment and form records
Setup
Build it in a few focused steps.
- 1Connect Stripe and Basin once in the Notis portal.
- 2Create a new automation from Automations, New Automation, or tell Notis what to do from a connected channel.
- 3In one instruction, ask Notis to retrieve submissions for the specified Basin form after checkout and summarize the useful context available.
- 4Pick the Stripe Checkout Session Completed trigger and choose where run reports go.
- 5Test with one checkout and a real Basin form containing submissions.
Questions about this workflow
Can Notis find the matching submission automatically?
Only if the event and Basin submission data provide a usable link or identifier. Supply any matching rule or identifier that is missing.
Does this create a notification in Basin?
No. It retrieves Basin submissions for Notis to analyze. The workflow does not create or send a notification.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Basin. A trigger fires from one place; an action lands in another.
Stripe triggers
Basin actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Form
Tool to create a new form in basin. use when you need to automate form setup with name, timezone, and project association; optionally configure redirect, notifications, or spam protection.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Form Webhook
Tool to create a new webhook for a specific form. use when you need to programmatically add a webhook once you have the form id and callback url confirmed.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Create Notification
Tool to create a new notification webhook. use when you need to forward form submissions to an external service.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Create Project
Tool to create a new basin project. use when you need a new organizational container for forms. example: "create a project named marketing leads."
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Delete Form
Tool to delete a form. use when permanently removing a form after it's no longer needed. ensure the form id is correct; this operation is irreversible.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Delete Integration
Tool to delete a form webhook integration. use when removing an obsolete integration by id.
Product Created Trigger
Triggered when a product is created in Stripe
Delete Project
Tool to delete a project. use when you need to remove a project after confirming its id. returns the deleted project's details.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Delete Webhook
Tool to delete a specific webhook. use when you need to remove a webhook from a form after confirming its id.
Connect any two apps with Notis in the middle.
Stripe and Basin, 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 Basin.