Check parsed agreement records when a subscription ends
A cancellation can leave paperwork to review. Have Notis bring relevant parsed agreement results into the run report.
Trigger
Subscription Deleted Trigger
Triggered when a subscription is deleted in Stripe
Action
Get Multiple Document Results
Tool to retrieve parsed data from multiple documents processed by a specific parser. Use when you need to fetch results for multiple documents at once. Returns up to 100 results by default, with a maximum of 10000.
Why this helps
Subscription cancellations can get separated from agreement and renewal paperwork, leaving follow-up easy to miss.
- Bring related parsed agreement results into the cancellation review.
- Keep the review tied to the subscription deletion event.
- Make unclear or unmatched records visible for follow-up.
Setup
Build it in a few focused steps.
- 1Connect Stripe and Docparser once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it.
- 3Tell Notis to retrieve results from your agreement parser and summarize records that may relate to the deleted subscription; provide the parser ID and document clues available for matching.
- 4Pick the Stripe Subscription Deleted trigger and choose where run reports should go.
- 5Test with one real subscription deletion and check how the report handles records it cannot confidently match.
Questions about this workflow
Can this cancel or amend an agreement in Docparser?
No. The available action retrieves parser results only. The workflow prepares a review report and does not change agreements or parsed records.
Will every subscription match an agreement automatically?
Only if the event and parsed results contain usable matching clues. Tell Notis which clues to use, and have it flag uncertain matches rather than assume a match.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Stripe to Docparser. A trigger fires from one place; an action lands in another.
Stripe triggers
Docparser actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Get Multiple Document Results
Tool to retrieve parsed data from multiple documents processed by a specific parser. Use when you need to fetch results for multiple documents at once. Returns up to 100 results by default, with a maximum of 10000.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Get Parser Models
Tool to retrieve all model layouts for a specific parser. Use when you need to list different layout configurations within a parser that help handle document variations.
Charge Failed Trigger
Triggered when a direct charge fails in Stripe's legacy Charges API
List Parsers
Tool to retrieve all Document Parsers linked to your account. Use when you need to view available parsers or obtain parser IDs for subsequent operations.
Checkout Session Completed Trigger
Triggered when a checkout session is completed in Stripe
Ping API
Tool to test API authentication and connection health check for Docparser API. Use when you need to verify that API credentials are valid and the connection is working.
Invoice Payment Succeeded Trigger
Triggered when an invoice payment is successful in Stripe
Payment Intent Failed Trigger
Triggered when a payment intent fails in Stripe
Product Created Trigger
Triggered when a product is created in Stripe
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Connect any two apps with Notis in the middle.
Stripe and Docparser, 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 Docparser.