Start Stripe subscriptions from signed BoldSign contracts
Move from signed terms to subscription setup with one clear handoff.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create subscription
Creates a new, highly configurable subscription for an existing stripe customer, supporting multiple items, trials, discounts, and various billing/payment options.
Why this helps
A signed contract can be easy to forget when subscription setup requires a separate Stripe step.
- Reduce delays between signature and billing setup
- Use supplied Stripe customer and price identifiers
- Surface missing subscription inputs for review
Setup
Build it in a few focused steps.
- 1Connect BoldSign and Stripe once in Notis.
- 2Create an automation and describe creating a subscription from supplied signed-contract details.
- 3Pick a Notis webhook trigger and choose where run reports go.
- 4Send the customer and subscription details to the webhook after signature.
- 5Test with one real agreement and valid Stripe identifiers.
Questions about this workflow
Does the agreement automatically provide Stripe price identifiers?
Not necessarily. Include the Stripe customer and price identifiers in the webhook request or have Notis report that they are missing.
Does this workflow decide the subscription terms?
No. The subscription details must be supplied or already determined; the workflow uses them to create the subscription.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Boldsign to Stripe. A trigger fires from one place; an action lands in another.
Boldsign triggers
Stripe actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Cancel subscription
Cancels a customer's active stripe subscription at the end of the current billing period, with options to invoice immediately for metered usage and prorate charges for unused time.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Confirm payment intent
Confirms a stripe paymentintent to finalize a payment; a `return url` is necessary if the payment method requires customer redirection.
Create Customer
Creates a new customer in stripe, required for creating charges or subscriptions; an email is highly recommended for customer communications.
Create an invoice
Creates a new draft stripe invoice for a customer; use to revise an existing invoice, bill for a specific subscription (which must belong to the customer), or apply detailed customizations.
Create payment intent
Creates a stripe paymentintent to initiate and process a customer's payment; using `application fee amount` for a connected account requires the `stripe-account` header.
Create a price
Creates a new stripe price for a product, defining its charges (one-time or recurring) and billing scheme; requires either an existing `product` id or `product data`.
Create product
Creates a new product in stripe, encoding the request as `application/x-www-form-urlencoded` by flattening nested structures.
Create Refund
Creates a full or partial refund in stripe, targeting either a specific charge id or a payment intent id.
Connect any two apps with Notis in the middle.
Boldsign and Stripe, 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 Stripe.