Connect Stripe to Draftable

When something happens in Stripe, Notis takes the next step in Draftable. 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 Stripe to Draftable

View example

Review document comparisons after a failed Stripe charge

Use Draftable comparison history to check document changes when a direct charge fails, so you can spot a related agreement or billing document that needs follow-up.

View example

Check agreement changes after checkout completes

After a Stripe checkout completes, use Draftable comparison history to review available agreement changes and keep document follow-up with the completed purchase.

View example

Review document changes when an invoice is paid

When Stripe confirms an invoice payment, have Notis inspect Draftable comparison history for related document changes to include in your account follow-up.

View example

Triage document changes after a payment intent fails

Pair a Stripe payment intent failure with a Draftable comparison history review to see whether relevant document changes should be considered in payment recovery.

View example

Review product document changes when a Stripe product is created

When a product is created in Stripe, have Notis review Draftable comparison history for product-related document changes that may need a consistency check.

View example

Check document changes when a subscription starts

When Stripe adds a subscription, review Draftable comparison history for changes to subscription terms or related customer documents.

View example

Review document changes when a subscription ends

When Stripe deletes a subscription, check Draftable comparison history for related term changes to include in account closeout and retention review.

Supported Triggers and Actions

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

Stripe triggers

Draftable actions

Recurring trigger

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

TriggerScheduled

List Comparisons

Tool to retrieve a paginated list of document comparisons. use when you need to browse comparisons across pages.

ActionInstant

Webhook trigger

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

TriggerInstant

Charge Failed Trigger

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

TriggerInstant

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

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.