AI Agent for Automated Document Signing via Telegram - n8n Workflow

Markdown-formatted:
Business owners or legal teams needing to quickly dispatch documents for signature.
Users looking for advanced examples of building custom AI tools within an n8n workflow.
Developers seeking to integrate document signing APIs (like SignNow) with conversational interfaces (Telegram).
Anyone interested in creating powerful, conversational n8n templates.

This comprehensive n8n workflow streamlines the entire document signing process by embedding it within a Telegram chat interface. Instead of manual steps, users interact with an AI agent who can manage and execute complex API calls to a document signing service.

The power of this solution lies in its ability to abstract complex document signing logistics—such as copying a base template, prefilling necessary data via a prefill_smartfields n8n node, and generating a unique signing URL—all through natural language commands in Telegram. This n8n workflow significantly reduces administrative overhead and accelerates the time-to-signature. Furthermore, the n8n template includes a separate webhook to notify the team automatically once the document signing process is complete.

This n8n workflow operates via two distinct triggers:

1. The Conversational Flow (Telegram Trigger): The process begins with the Main Bot Trigger, which is a Telegram n8n trigger listening for incoming messages. The incoming message is passed through a Context n8n node to format the input before being routed to the Document Signature AI Agent (LangChain Agent).

1. The Completion Flow (Webhook Trigger): The secondary flow starts with the Document Signed n8n webhook node. This n8n trigger receives confirmation from the document signing service upon successful completion of the signature process. It then activates the Notify Document Signed Telegram n8n node, broadcasting a success message to a predefined channel or user, ensuring seamless communication about the contract status.

Markdown-formatted:
To deploy this powerful n8n workflow, follow these steps:

1. Import the n8n template: Copy the provided JSON and paste it directly into your n8n instance via the 'New' menu > 'Import from JSON'.


2. Set up Credentials: This n8n workflow requires several credentials:

1. Activate Webhooks: Save the workflow. For the Main Bot Trigger and Document Signed n8n trigger, ensure the webhooks are active and correctly registered with Telegram and your document signing service, respectively.


2. Customize Tools: Review the parameters within the custom HTTP Request n8n node tools to ensure they match your specific document template IDs and API requirements.

Markdown-formatted:
This advanced n8n workflow uses a combination of core and LangChain nodes to achieve its goal:

Main Bot Trigger (Telegram Trigger):
Function: Serves as the primary conversational n8n trigger, initiating the AI Agent process when a user sends a message to the associated Telegram bot.
Key Configuration: Configured as a Telegram Trigger listening for new messages.

Document Signature AI Agent (Langchain Agent):
Function: The core decision-making n8n node. It processes natural language, retrieves context from aimemory, uses aichat for processing, and decides which custom HTTP tool to call to fulfill the user's request.

aichat & aimemory (Langchain Nodes):
Function: Provides the large language model backend and maintains conversational context for the AI Agent, making the n8n workflow responsive and effective.

copytemplate (HTTP Request Tool):
Function: A custom tool utilized by the Agent to duplicate an existing document template, ensuring each new signature request starts from a clean copy.
Key Configuration: Contains specific API endpoints for copying templates in the document signing service.

getsigningurl (HTTP Request Tool):
Function: This critical n8n node is called by the Agent to generate and retrieve the unique, secure URL that the signer must use to access and sign the document.

sendsign_url (Telegram Tool):
Function: The action tool that the AI Agent uses to send the final generated signing URL back to the user via Telegram, completing the primary task of the n8n workflow.

Document Signed (Webhook Trigger):
Function: A passive n8n trigger that waits for an external event (a signed document) to initiate a secondary flow for notification.