Add a signer to a Docnify document from a request
When a signer is confirmed, a request can start the focused step of adding them to the right document.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
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.
Why this helps
Recipient details arrive in one place and the document lives in another, creating a handoff that is easy to postpone.
- Adds a recipient to a specific confirmed document.
- Can include signing order or authentication options when needed.
- Keeps signer details and document identity explicit.
Setup
Build it in a few focused steps.
- 1Connect Docnify once in the Notis portal.
- 2Create an automation and give it a clear name.
- 3In one instruction, provide the confirmed document ID and recipient details, including signing order or authentication options if needed, and ask Notis to add the recipient when a webhook starts.
- 4Pick the webhook trigger and choose where run reports go.
- 5Test with one real document and recipient example.
Questions about this workflow
Does the webhook supply signer details automatically?
The listed trigger only starts on an HTTP request. Make sure the instruction or supported request context supplies the recipient details.
Can the recipient be added before confirming the document?
No. Confirm the document ID and intended recipient before the action runs.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Airtable to Docnify. A trigger fires from one place; an action lands in another.
Airtable 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.
Base Metadata Changed
Triggers when an existing Airtable base changes its name or permission level.
Delete Document
Tool to delete a specific document by its ID. Use when you have confirmed the document should be permanently removed.
Base Schema Changed
Triggers when tables, fields, or views change in an Airtable base.
Delete Document Field
Tool to delete a field from a document. Use when you need to remove a specific field from an existing document.
User Profile Changed
Triggers when the connected Airtable user's profile information changes.
Delete document recipient
Tool to remove a recipient from a document. Use after verifying document and recipient IDs to revoke access.
View Created
Triggers when a new view is created in an Airtable base.
Get Document
Tool to fetch a specific document by its ID. Use when you need to view a document's current state and metadata.
View Deleted
Triggers when a previously known Airtable view is deleted.
Get Template
Tool to fetch a specific template by its ID. Use to view a template's details and metadata.
View Metadata Changed
Triggers when an Airtable view changes its name or type.
List Documents
Tool to list documents in the Docnify account.
Connect any two apps with Notis in the middle.
Airtable 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.