Keep checkout and document signing in sync
A completed checkout can be the cue to check whether its related agreement is signed.
Trigger
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Action
List Documents
Tool to list documents in the Docnify account.
Why this helps
A successful payment can be easy to celebrate while the related agreement is still waiting for signatures.
- See signing status alongside checkout activity
- Spot agreements that still need attention
- Avoid manually checking Docnify after each payment
Setup
Build it in a few focused steps.
- 1Connect Stripe and Docnify once in the Notis portal.
- 2Create an automation and name it for checkout document status.
- 3Tell Notis to find the Docnify document associated with the completed checkout and report its current status; provide the matching rule if needed.
- 4Pick Stripe's Checkout Session Completed trigger and choose where run reports should go.
- 5Test with one real checkout and confirm the correct document is found.
Questions about this workflow
How does Notis know which document belongs to a checkout?
Tell Notis the matching rule, such as a customer email or an identifier present in both systems. If no shared identifier is available, provide the document ID or a reliable lookup instruction.
Does this send a document for signature?
No. This workflow lists documents to locate a match and report status. It does not send a document.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Docnify. A trigger fires from one place; an action lands in another.
Stripe triggers
Docnify actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Document Recipient
Tool to add a recipient to a document. Use after confirming the document's ID. Optionally specify signing order and authentication options.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Document Fields
Tool to create one or more fields on a document. Use after fetching a document to add fields before sending.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
Delete Document
Tool to delete a specific document by its ID. Use when you have confirmed the document should be permanently removed.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Delete Document Field
Tool to delete a field from a document. Use when you need to remove a specific field from an existing document.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Delete document recipient
Tool to remove a recipient from a document. Use after verifying document and recipient IDs to revoke access.
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Get Document
Tool to fetch a specific document by its ID. Use when you need to view a document's current state and metadata.
Product Created Trigger
Triggered when a product is created in Stripe
Get Template
Tool to fetch a specific template by its ID. Use to view a template's details and metadata.
Subscription Added Trigger
Triggered when a subscription is added in Stripe
List Documents
Tool to list documents in the Docnify account.
Connect any two apps with Notis in the middle.
Stripe and Docnify, 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 Docnify.