Keep document requirements in sync with corrections
When field instructions change, let the edited Telegram message guide a targeted update to existing fields on the verified Docnify document.
Trigger
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Action
Update Document Fields
Tool to update metadata of document fields. Use when you need to change labels or requirements of existing fields before sending.
Why this helps
An outdated field label or requirement can survive after the team has already corrected the instruction in chat.
- Use the clarified version of a field instruction.
- Keep existing Docnify fields aligned with the team's latest decision.
- Reduce rework caused by acting on stale details.
Setup
Build it in a few focused steps.
- 1Connect Telegram and Docnify to Notis once in the portal.
- 2Create an automation in Automations or ask Notis to set it up conversationally.
- 3In one plain-language instruction, tell Notis to use the edited message as the latest field request and update only verified fields on the identified document.
- 4Choose Telegram Message Edited as the trigger and select a channel for run reports.
- 5Test with a real edited request on an identified test document.
Questions about this workflow
Does this create new fields?
No. This workflow updates metadata for existing fields. Creating fields is a separate action.
What should the instruction include?
A verified document, which existing fields to change, and the clarified label or requirement.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Telegram to Docnify. A trigger fires from one place; an action lands in another.
Telegram 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.
New Message Received
Triggered when your bot receives a new message in a private chat, group, or supergroup. To receive every message in a group, Privacy Mode must be disabled for the bot in BotFather.
Delete Document
Tool to delete a specific document by its ID. Use when you have confirmed the document should be permanently removed.
New Channel Post
Triggered when a new post is published to a channel where your bot is an administrator.
Delete Document Field
Tool to delete a field from a document. Use when you need to remove a specific field from an existing document.
Callback Query Received
Triggered when a user taps an inline keyboard button attached to one of your bot's messages.
Delete document recipient
Tool to remove a recipient from a document. Use after verifying document and recipient IDs to revoke access.
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
Get Document
Tool to fetch a specific document by its ID. Use when you need to view a document's current state and metadata.
New Chat Member
Triggered when a new member joins a group or supergroup the bot belongs to, including when the bot itself is added.
Get Template
Tool to fetch a specific template by its ID. Use to view a template's details and metadata.
List Documents
Tool to list documents in the Docnify account.
Connect any two apps with Notis in the middle.
Telegram 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.