Automate rental agreements with BoldSign, Google Sheets & Gemini AI
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
Nodes used (11)
- Webhook
n8n-nodes-base.webhook - If
n8n-nodes-base.if - Edit Fields (Set)
n8n-nodes-base.set - Google Sheets
n8n-nodes-base.googleSheets - HTTP Request
n8n-nodes-base.httpRequest - n8n Form Trigger
n8n-nodes-base.formTrigger - Telegram Trigger
n8n-nodes-base.telegramTrigger - AI Agent
@n8n/n8n-nodes-langchain.agent - Google Gemini Chat Model
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - Google Sheets Tool
n8n-nodes-base.googleSheetsTool - Telegram
n8n-nodes-base.telegram
What it does
Complete Video Documentation: https://youtu.be/O-bKlX3G74 Explanation WITH clean Video timestamps: Prerequisites: You need a rental agreement document, a BoldSign account (which has a free tier for testing) 00:44, a Google Sheet, and an n8n instance. BoldSign Setup: How to upload your agreement as a template, drag-and-drop the signature and text fields 01:13, get your API key 01:57, and set up a webhook to notify n8n when the agreement is signed or completed 02:13. Workflow Logic: The video walks through the two main flows: 1. Form Submission: A tenant fills out a form, which triggers n8n to save the details to Google Sheets and then call the BoldSign API to send the agreement to both the owner and tenant 03:01. 2. Completion: When both parties sign, BoldSign sends an event to the n8n webhook, which then filters for the "Completed" event and updates the Google Sheet 09:12. Bonus: It also covers the Telegram bot setup, which lets an owner ask an AI about the status of agreements 11:52. ----- Prerequisites Before you build this, you'll need a few things: An n8n Instance: This can be on n8n.cloud or self-hosted. A Google Sheet: Create a new sheet with columns like Tenant Name, Tenant Email, Property, Estimated Rent per month, contract expiry, and agreement status. A BoldSign Account: An API Key. 01:57 A prepared rental agreement document (like a PDF or .docx). A BoldSign Template created from that document. You'll need to drag and drop the required fields (like signatures, dates, text boxes) onto the template. 01:13 A Telegram Bot (Optional): If you want the AI status checker, you'll need to create a bot with Telegram's BotFather to get an API token. A Google Gemini API Key (Optional): For the AI agent. ----- In BoldSign, you would replace the {{...}} and Date parts with draggable form fields. ----- Understanding the BoldSign API Node The key to sending the agreement is the Send aggrement to Tenant's Email node. This is a standard HTTP Request node, not a special BoldSign node. Method: POST URL: https://api.boldsign.com/v1/template/send?templateId=enter-your-template-id This is the official BoldSign API endpoint for sending a document based on a template. You must replace enter-your-template-id with the actual ID of the template you created in BoldSign 07:04. Authentication: Header Auth BoldSign uses an API key in the header. You would create a credential in n8n where the Name is X-API-KEY and the Value is the secret API key you got from your BoldSign account 07:16. Body: The jsonBody is the most important part 08:02. It's a JSON object that tells BoldSign who to send the agreement to and what data to pre-fill. title: Sets the document title, like "Rental Agreement - 123 Main St". roles: This array defines the signers. One role is for the "Owner", dynamically filling their name and email from the form data. The second role is for the "Tenent" (Tenant), also filling their name and email. existingFormFields & mergeFields: This is where you dynamically insert data into the document. You map the data from your n8n form (like {{ $('Retrive Data from submitted form').item.json.address }}) to the id of the fields you created in your BoldSign template 08:16. ----- Workflow Explanation (From Scratch) This workflow is actually three separate flows that work together. Flow 1: New Tenant Onboarding (Form to Agreement) This is the main flow that kicks everything off when a new tenant is interested. 1. Node: Tenant Form (Form Trigger) What it is: This node creates a public web form 03:10. This is the starting point. From Scratch: You'd drag in a Form Trigger node. You add fields for "Your Name" (tenant's name) and "Your Email" (tenant's email). This Workflow: It also cleverly uses hidden fields 03:18 to store the owner's details, the property address, and the rent. This is a simple way to manage a single property. For multiple properties, you might use a database or a Google Sheet lookup. 2. Node: Retrive Data from submitted form (Set) What it