Connect Stripe to Control d

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

View example

Provision Network Access After Checkout

Create a Control D device when a Stripe checkout completes, using customer or product details supplied in the event or your instructions.

View example

Provision a Device for Each New Subscriber

When Stripe adds a subscription, have Notis create a Control D device for the subscriber based on supplied account and device details.

View example

Review Control D Devices When a Subscription Ends

When a Stripe subscription is deleted, retrieve the Control D device inventory so Notis can help identify devices that may need cleanup.

View example

Add Network Usage to a Successful Payment Review

After an invoice payment succeeds, retrieve a Control D profile analytics summary to give your review more customer context.

Supported Triggers and Actions

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

Stripe triggers

Control d actions

Recurring trigger

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

TriggerScheduled

Delete Device by ID

Tool to delete a Control-D device. Use when you need to remove a device by its identifier after confirming the device_id.

ActionInstant

Webhook trigger

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

TriggerInstant

Delete Profile by ID

Tool to delete a profile. Use when you need to remove a profile by its ID after ensuring it is not enforced by any device.

ActionInstant

Charge Failed Trigger

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

TriggerInstant

Delete Profile Rule by Hostname

Tool to delete a specific custom rule by hostname from a profile. Use after confirming profile_id and hostname.

ActionInstant

Checkout Session Completed Trigger

Triggered when a checkout session is completed in Stripe

TriggerInstant

Delete Profile Rule by Rule ID

Tool to delete a specific custom rule by its ID within a profile. Use after confirming profile_id and rule_id.

ActionInstant

Invoice Payment Succeeded Trigger

Triggered when an invoice payment is successful in Stripe

TriggerInstant

Delete Profile Rule in Folder

Tool to delete a specific custom rule within a folder. Use after confirming profile_id, rule_id, and folder_id.

ActionInstant

Payment Intent Failed Trigger

Triggered when a payment intent fails in Stripe

TriggerInstant

Delete Profile Schedule

Tool to delete a specific schedule within a profile. Use after confirming profile_id and schedule_id.

ActionInstant

Product Created Trigger

Triggered when a product is created in Stripe

TriggerInstant

List Known Access IPs

Tool to list known IPs associated with the account. Use when you need to retrieve recent access IPs for device resolver queries.

ActionInstant

Subscription Added Trigger

Triggered when a subscription is added in Stripe

TriggerInstant

Get Analytics Endpoints

Tool to list analytics storage regions and their endpoints. Use after authenticating to retrieve available analytics regions.

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.