Keep corrected signer details aligned
Edits happen. Use the clarified Telegram message as the prompt for an accurate update to the recipient on the identified Docnify document.
Trigger
Message Edited
Triggered when a message in a chat your bot can see is edited by its sender.
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
A corrected email or name can be missed when the earlier message has already been read and acted on.
- Notice when a Telegram correction replaces earlier information.
- Keep recipient details consistent with the latest instruction.
- Reduce confusion from outdated contact information.
Setup
Build it in a few focused steps.
- 1Connect Telegram and Docnify to Notis once in the portal.
- 2Create an automation from Automations or ask Notis to create it conversationally.
- 3Write one plain-language instruction to use an edited message as the correction and update a verified Docnify recipient only when document and recipient IDs are clear.
- 4Choose Telegram Message Edited as the trigger and set a channel for run reports.
- 5Test by editing a real test message with a specific, verifiable recipient correction.
Questions about this workflow
Does this act on the original or edited message?
The instruction should tell Notis to use the latest edited message as the correction request.
What must be verified before updating?
The document and recipient IDs, plus the intended detail to change.
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.