Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
Docusign
Telegram Bot

Connect Docusign and Telegram Bot

Explore ready-made Docusign and Telegram Bot templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate Docusign with Telegram Bot and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

Docusign
Trigger: [Deprecated] Watch Events
Telegram Bot
Action: Select an action
1. Select a trigger

  • Triggers when an envelope or recipient status is changed.

  • Sent after a recipient accepts an elastic template.

  • Sent after a recipient declines an elastic template.

  • Triggers when one of the selected events are fired in Docusign

  • Triggers when an envelope has been completed.

  • The envelope has been completed by all the recipients.

  • Sent when the envelope is correctedcorrected, opens in new window within the UI or via any of the Envelopes/EnvelopesRecipients API calls.

  • This event is sent when an envelope is created through the DocuSign eSignature UI or when an envelope's status is set to "created" after an Envelopes:create API call.

  • The envelope has been declined by one of the recipients.

  • This event is sent after an already-sent envelope is deleted, opens in new window.

  • This event is sent when all recipients have opened the envelope through the DocuSign signing website. This does not signify an email delivery of an envelope.

  • Sent when an envelope in created or draft state is deleted or discarded within the tagging UI.

  • Sent when the envelope is queued to be purged, opens in new window or via the Envelopes:update API call.

  • Sent when the envelope is resent, opens in new window within the UI or via the Envelopes:update API call.

  • This event is sent when the email notification, with a link to the envelope, is sent to at least one recipient or when it is a recipient's turn to sign during embedded signing. The envelope remains in this state until all recipients have viewed the envelope.

  • The envelope has been voided by the sender or has expired. The void reason indicates whether the envelope was manually voided or expired.

  • Triggers when a new Agreement Manager agreement is created. Only available for Docusign IAM plans.

  • Triggers when a new document is added to a specific workspace. Only available for Docusign IAM Plans.

  • Triggers when a new user is added to a specific workspace. Only available for Docusign IAM Plans.

  • Triggers when a new workspace is created. Only available for Docusign IAM Plans.

  • Sent when DocuSign gets notification that an email delivery has failed. The delivery failure could be for a number of reasons, such as a bad email address or that the recipient’s email system auto-responds to the email from DocuSign.

  • Sent when the recipient has completed their actions for the envelope, typically (but not always) by signing.

  • Sent when the recipient declines to sign the document(s) in the envelope.

  • Sent after a Delegation rule is in place and when a delegated signer is sent an envelope within the UI or the API.

  • Sent when the recipient has viewed the document(s) in an envelope through the DocuSign signing web site. This does not signify an email delivery of an envelope.

  • Sent when the recipient selects Finish Later on an envelope.

  • Sent when the envelope is reassigned by a recipient within the UI.

  • Triggered when an envelope is resent to a recipient within the web application or using the EnvelopeRecipients : update API call.

  • This event is sent when an email notification is sent to the recipient signifying that it is their turn to sign an envelope.

  • Sent when a template is createdtemplate is created, opens in new window within the UI or via the Templates:create API call.

  • Sent when a template is deleted within the UI or via the recycle bin API call recycle bin API call, opens in new window.

  • Sent when a template is modified within the UI or via the Templates:update API call.

  • Triggers when an existing Agreement Manager agreement is updated. Only available for Docusign IAM plans.

  • Triggers when a Workflow Builder workflow completes. Only available for Docusign IAM Plans.

  • Triggers when a Worflow Builder workflow fails. Only available for Docusign IAM Plans.

  • Triggers when a Workflow Builder workflow started. Only available for Docusign IAM Plans.

2. Select an action

  • Sends answer to an inline query.

  • Creates an additional invite link for a chat.

  • Deletes a message. A message can only be deleted if it was sent less than 48 hours ago.

  • Downloads a file from the Telegram server.

  • Edits a non-primary invite link created by the bot.

  • Edits photo or video messages.

  • Edits a caption of a message.

  • Edits text or game messages.

  • Forwards messages of any kind. This module can be used to forward messages only within Telegram.

  • Use this module to get the number of members in a chat. Returns Int on success.

  • Use this method to kick a user from a group, a supergroup or a channel. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights.

  • Performs an arbitrary authorized API call.

  • Pins a message.

  • Use this method to promote or demote a user in a supergroup or a channel. The bot must be an administrator in the chat for this to work and must have the appropriate admin rights.

  • Use this method to restrict a user in a supergroup.

  • Revokes an invite link created by the bot.

  • Sends a document or an image to your Telegram Desktop application.

  • Sends a photo to your Telegram Desktop application.

  • Sends a .webp sticker to your Telegram Desktop application.

  • Sends a text message or a reply to your Telegram Desktop application.

  • Sends a video file to your Telegram Desktop application.

  • As of v.4.0, Telegram clients support rounded square mp4 videos of up to 1 minute long. Use this method to send video messages.

  • Sends a voice message

  • Sends a group of photos or videos as an album.

  • Sends an audio file to your Telegram Desktop application.

  • Sends an invoice.

  • Sends a file (document, photo, video, audio, ...) by HTTP URL or by ID that exists on the Telegram servers.

  • Unpins a message.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between Docusign and Telegram Bot.

[Deprecated] Watch Events
Triggers when an envelope or recipient status is changed.
Trigger
Add document to Workspace (for IAM Plans)
Adds a new document to a workspace. Only available for Docusign IAM Plans.
Action
Add to Bulk Send List
Adds a recipient to the bulk send list
Action
Add User to Workspace (for IAM Plans)
Adds a user to a workspace. Only available for Docusign IAM Plans.
Action
Answer an Inline Query
Sends answer to an inline query.
Action
Bulk Send Envelope from Template
Sends envelopes based on a template to multiple recipients using a bulk send list.
Action
Cancel Workflow Instance (for IAM Plans)
Cancels a running Workflow Builder workflow instance. Only available for Docusign IAM Plans.
Action
Create a Chat Invite Link
Creates an additional invite link for a chat.
Action
Create Bulk Send List
Creates a bulk send list
Action
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.