Add signature fields to a Docnify document on request
When a document is ready for signing setup, a request can kick off the field creation step with your specified details.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Create Document Fields
Tool to create one or more fields on a document. Use after fetching a document to add fields before sending.
Why this helps
Getting field placement and requirements ready can become a separate task that stalls the rest of a signing workflow.
- Creates specified fields on a document that has been fetched.
- Moves field setup into a clear step before sending.
- Makes required field details explicit in the instruction.
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, specify the document ID and fields to create, and ask Notis to fetch the document and add those fields when a webhook starts.
- 4Pick the webhook trigger and choose where run reports go.
- 5Test with one real document and field example.
Questions about this workflow
Does this send the document?
No. It creates fields before sending; a send action is a separate step.
What if the document ID is not known?
Provide a confirmed document ID in the instruction. The webhook trigger alone does not identify a Docnify document.
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.