Keep signer details current for new subscriptions
Use subscription data to update a confirmed recipient record when your process calls for it.
Trigger
Subscription Added Trigger
Triggered when a subscription is added in Stripe
Action
Update Document Recipient
Tool to update a recipient's details (name, email, role) on a document. Use after confirming document and recipient IDs. Provide at least one field to update.
Why this helps
Signer details can be stale by the time a subscription is added, creating avoidable manual corrections.
- Update recipient details when a subscription is added
- Reduce repetitive signer record edits
- Use explicit identifiers before changing a recipient
Setup
Build it in a few focused steps.
- 1Connect Stripe and Docnify once in the Notis portal.
- 2Create an automation for subscription signer detail refresh.
- 3Tell Notis which Docnify document and recipient to update and which available Stripe details to use; supply IDs or a matching rule.
- 4Pick Stripe's Subscription Added trigger and choose where run reports should go.
- 5Test with one real subscription and verify the intended recipient was updated.
Questions about this workflow
Can this update any signer field automatically?
The action requires at least one field to update. Specify the desired details and ensure they are available from the Stripe event or supplied context.
What if multiple documents match?
Give Notis a rule that identifies the intended document and recipient. The workflow should not update an ambiguous match.
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.