Provision network access after a Stripe checkout
A completed checkout can kick off device provisioning while the customer context is fresh.
Trigger
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Action
Create Device
Tool to create a new device. Use when you need to provision devices and retrieve their DNS resolvers.
Why this helps
New customers can be left waiting while you manually turn a completed checkout into network access.
- Start device provisioning as soon as checkout completes.
- Reduce manual handoffs between payment and network setup.
- Use event details or supplied instructions to identify the intended device configuration.
Setup
Build it in a few focused steps.
- 1Connect Stripe and Control D once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis to create it from any channel.
- 3Describe how a completed checkout should result in a Control D device, including how to identify the customer and required device details.
- 4Pick the Stripe Checkout Session Completed trigger and choose where run reports should go.
- 5Test with one real checkout and confirm the created device is correct.
Questions about this workflow
What details does Notis need to create a device?
Provide the customer identifier and device details in the Stripe event or your instruction. If the event does not contain the required details, Notis needs you to supply them.
Will this create a device for every completed checkout?
It runs for each checkout completion. Describe any eligibility rules in the instruction and test with a real example.
When this happens · Trigger
Do this · Action
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.
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.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
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.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Delete Profile Rule by Hostname
Tool to delete a specific custom rule by hostname from a profile. Use after confirming profile_id and hostname.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
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.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
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.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Delete Profile Schedule
Tool to delete a specific schedule within a profile. Use after confirming profile_id and schedule_id.
Product Created Trigger
Triggered when a product is created in Stripe
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.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Get Analytics Endpoints
Tool to list analytics storage regions and their endpoints. Use after authenticating to retrieve available analytics regions.
Connect any two apps with Notis in the middle.
Stripe and Control d, 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 Control d.