Skip to content
Notis

Keep completed checkout context close to your Cults work

A completed checkout can be the cue to update Cults with the purchase context you need, without switching apps to do it by hand.

Trigger

Checkout Session Completed Trigger

Triggered when a checkout session is completed in Stripe

Action

Cults GraphQL POST

Tool to execute a GraphQL operation against the Cults API. Use when you need to fetch or mutate data via the Cults GraphQL endpoint.

Why this helps

Purchase follow-up gets lost when checkout details live in Stripe and the next step lives in Cults.

  • Reduce manual app switching after a checkout completes.
  • Use Notis to interpret the event and issue a supported Cults GraphQL operation.
  • Keep the next action tied to a real Stripe checkout event.

Setup

Build it in a few focused steps.

  • 1Connect Stripe and Cults once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and give it a name.
  • 3In one instruction, tell Notis what supported Cults GraphQL operation to perform using the completed checkout context.
  • 4Pick Checkout Session Completed as the trigger and choose where run reports go.
  • 5Test with one real example and confirm the intended Cults result.

Questions about this workflow

Does this automatically create a Cults collection?

Only if Cults exposes a supported GraphQL operation for that change. Describe the intended operation and confirm it with a real example.

Can Notis infer the fields Cults needs?

Notis can analyze returned event data, but any required field or context not supplied by Stripe or Cults must be provided in your instruction.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Stripe to Cults. A trigger fires from one place; an action lands in another.

Stripe triggers

Cults actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

Get Approved Origins

Tool to retrieve approved sharing origins from Cults. Use when you need to infer the allowed domains for the Share on Create action. Use after authenticating with Cults.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Cults GraphQL POST

Tool to execute a GraphQL operation against the Cults API. Use when you need to fetch or mutate data via the Cults GraphQL endpoint.

ActionInstant

Charge Failed Trigger

Triggered when a direct charge fails in Stripe's legacy Charges API

TriggerInstant

Share on Create (FR)

Tool to prefill a new creation on Cults (French locale). Use when you need to generate a one-click share link for a 3D file. Use after your site is approved by Cults.

ActionInstant

Checkout Session Completed Trigger

Triggered when a checkout session is completed in Stripe

TriggerInstant

Invoice Payment Succeeded Trigger

Triggered when an invoice payment is successful in Stripe

TriggerInstant

Payment Intent Failed Trigger

Triggered when a payment intent fails in Stripe

TriggerInstant

Product Created Trigger

Triggered when a product is created in Stripe

TriggerInstant

Subscription Added Trigger

Triggered when a subscription is added in Stripe

TriggerInstant

Connect any two apps with Notis in the middle.

Stripe and Cults, 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 Cults.