Fix a Docnify recipient detail from chat
Capture a correction where it is noticed, then let Notis update the specified recipient details after checking the document and recipient IDs.
Trigger
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.
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
Small recipient corrections can get buried in chat while the signing task waits for someone to return to Docnify.
- Act on a correction without losing the conversation context.
- Update only the named recipient on the identified document.
- Reduce back-and-forth for routine contact fixes.
Setup
Build it in a few focused steps.
- 1Connect Telegram and Docnify to Notis once in the portal.
- 2Create an automation in Automations or by asking Notis in plain language.
- 3In one instruction, ask Notis to update a recipient only when a Telegram correction clearly identifies the Docnify document, recipient, and intended detail.
- 4Select Telegram New Message Received and choose a run-report channel.
- 5Test with an authorized correction on a document and recipient you can verify.
Questions about this workflow
What does the request need to identify?
The Docnify document and recipient must be verified, and the requested correction must specify at least one detail to update.
Can the workflow change a recipient's email?
Yes. The action supports updating recipient details such as name, email, and role.
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.