Collect delivery proof in Telegram and store it in Google tools. Drivers share a shipment number, GPS location, and a photo. Operations teams receive an email and a clean record in a sheet, so handoffs are quick and clear.

A Telegram message starts the flow and a command switch guides the chat. The workflow keeps a state per chat, so it asks for the right next step and only accepts the expected input. GPS coordinates are read from the message and saved. Photos are pulled from Telegram, uploaded to Google Drive, and shared with a link. Shipment details, location, and the file link are written to Google Sheets. Gmail sends a confirmation to the team, and a confirmation message goes back to the driver.

You will need a Telegram bot plus Google Drive, Google Sheets, and Gmail. Run the one time init step to create the state store, then activate the workflow. Expect faster proof collection, fewer errors, and simple tracking from start to finish. It fits last mile delivery, field drops, vendor pickups, and any team that needs reliable proof with location, photo, and a traceable record.

• Telegram message trigger starts the conversation on every driver message.
• Command switch routes slash commands like add shipment, send photo, and confirmation.
• Per chat state engine stores waiting flags so inputs are collected step by step.
• GPS capture reads location from the Telegram message and confirms back to the driver.
• Photo handling downloads from Telegram, uploads to Google Drive, and creates a shareable link.
• Google Sheets records shipment number, GPS, and photo link for easy tracking.
• Gmail sends proof of delivery to the operations team and confirms completion.
• One time init and clear state steps keep sessions clean across many drivers.

• Reduce manual tracking work from 20 minutes to 3 minutes per stop
• Automate driver prompts so the right data arrives in the right order
• Eliminate copy paste errors for shipment numbers and GPS
• Handle many drivers at the same time without extra staff
• Connect Telegram, Google Drive, Google Sheets, and Gmail in one flow

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Telegram, Google Drive, Gmail and Google Sheets. See the Tools Required section above for links to create accounts with these services.
3. Create a Telegram bot using BotFather and copy the bot token. In n8n, open the Telegram Trigger node, choose Credential to connect with, click Create new credential, and paste the bot token. Save and test that the node shows a successful connection.
4. Set up Google Drive credentials: open any Google Drive node, choose Credential to connect with, click Create new credential, then follow the on screen steps to sign in with your Google account and approve access.
5. Set up Google Sheets credentials the same way. Use the same Google account so Drive and Sheets can work together.
6. Set up Gmail credentials: open the Gmail node, create a new credential, and follow the on screen sign in flow. In the node, set the To address for your operations team and adjust the subject and body text.
7. Open the Upload Picture node and pick the destination folder in Google Drive. Make sure the Share or link step is configured to produce a public or team share link as needed.
8. Open the Google Sheets node and select the target spreadsheet and worksheet. Map fields for shipment number, GPS latitude, GPS longitude, file name, and file link.
9. Run the Initiate Workflow Data node once. This creates the global state store used to track each chat session. You only need to do this a single time.
10. Activate the workflow. In Telegram, send a message to your bot and try the commands to add shipment number, share location, and send a photo. Confirm that the sheet updates, the Drive file appears, and the email is delivered.
11. If the bot does not reply, check that the workflow is active and the Telegram credential is valid. If photos are not saved, verify Drive folder permissions. If data seems stuck, use the clear state path to reset the chat session and test again.