From cc5adc750870435697e36eae1c8d90b8532696a3 Mon Sep 17 00:00:00 2001
From: Lorenzo Perlo <68781644+TIT8@users.noreply.github.com>
Date: Thu, 2 May 2024 16:53:59 +0200
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 10e94cf..5e50773 100644
--- a/README.md
+++ b/README.md
@@ -29,7 +29,7 @@ HTTP API that handles, under the hood, the [_e-mail us_](https://triennale-elett
 
    But it's important to remember that Telegram is just an API endpoint, and it's entirely possible to send messages to chats from the browser as well (see [here](https://stackoverflow.com/questions/73084236/send-message-to-telegram-through-html-form-using-javascript) for an example). The same applies to the verification API of friendly captcha, which you can find [here](https://docs.friendlycaptcha.com/#/verification_api).
 
-2. This API can be extended with additional features, such as the ability to directly receive files and create pull requests to the GitHub repository, something that cannot be achieved in the browser.
+2. This API can be extended with additional features, such as the ability to directly receive files and create pull requests to the GitHub repository, something that cannot be achieved in the browser. Indeed it handles also [POST requests]() sent from Google Form when someone send files to maintainers. 
 
 ## Testing