Connect Coassemble to Stripe

When something happens in Coassemble, Notis takes the next step in Stripe. Describe what you want in plain English, or start from one of the examples below.

When this happens · Trigger

Do this · Action

Build an automation Browse examples

Examples

Ways Notis can move work from Coassemble to Stripe

View example

Invoice for completed training

Create a Stripe draft invoice when a trusted webhook reports billable course completion.

View example

Create a Stripe customer for a learner

Create a Stripe customer from a trusted Coassemble enrollment request when billing setup is needed.

View example

Prepare payment for approved training

Create a Stripe PaymentIntent when a trusted request includes an approved amount and payment context.

View example

Issue an approved training refund

Create a full or partial Stripe refund from a trusted request that identifies the payment and refund amount.

View example

Cancel a training subscription at period end

Schedule an approved Stripe subscription cancellation for period end from a trusted request.

View example

Review subscriptions alongside training progress

On a schedule, retrieve Stripe subscriptions for a supplied customer or filter set to support training billing reviews.

View example

Review training invoices on a schedule

Retrieve Stripe invoices on a recurring schedule and summarize those matching supplied review criteria.

View example

Review training charges against billing records

Retrieve Stripe charges on a schedule for a focused training billing reconciliation.

View example

Review training refund activity

Retrieve recent Stripe refunds on a schedule and summarize matching records for billing follow-up.

Supported Triggers and Actions

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

Coassemble triggers

Stripe actions

Recurring trigger

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

TriggerScheduled

Cancel subscription

Schedule a customer’s active subscription to end when the current billing period finishes.

ActionInstant

Webhook trigger

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

TriggerInstant

Accept quote

Accepts a quote, creating an invoice, subscription, or subscription schedule as configured.

ActionInstant

Confirm payment intent

Confirm a customer’s intent to pay and start a payment attempt.

ActionInstant

Activate billing alert

Reactivates a billing alert so it can trigger and send notifications again.

ActionInstant

Create Customer

Create a new customer record.

ActionInstant

Add lines to invoice

Adds charges, services, or credits to an existing draft invoice.

ActionInstant

Create an invoice

Create a draft invoice for a customer.

ActionInstant

Advance test clock

ActionInstant

Trigger Types

Four ways to start an automation.

A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.

Integration triggers

Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.

New Notion pageStripe chargeCalendar event

Webhook triggers

A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.

Any HTTP POSTCustom backendIoT event

Works with

ZapierPipedream

Most used

Recurring triggers

Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.

Daily · 8:00HourlyWeekdays only

Coming soon

Database triggers

Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.

Row insertedValue > limitQuery match

Why AI automation

Classic automation breaks. AI adapts.

Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.

Classic automationAI automation

Cost

$ · pay per run

$$ · AI models per run

Reliability

Breaks on schema change

Adapts to format changes

Setup

Click 8 dropdowns

Describe it in English

Handles fuzzy

Hard-coded fields only

Reads intent, summarises

Human in loop

Bolted on

Built in · approval inbox

Maintenance

You own every break

Self-heals · we own it

Ease of use

Describe it. Notis builds it.

Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.

You · in the Notis Builder

NEW

“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”

Notis built this automation:

TriggerRow added to "Q4 OKRs"

Condition✦Status = "Blocked"

AI step✦Summarise the blocker in plain English

ActionDM the row owner with summary

Timeout✦No reply in 24h → ping you

Observability

Watch every run.

Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.