telegram-bot | Telegram Bot using AWS API Gateway and AWS Lambda | Bot library

Update is a class and the property Update.effective_chat can only be properly evaluated for instances of that class. If you want to make simple calls to the Bot API, you should instantiate an instance of the telegram.Bot class and call its methods - in your case Bot.ban_chat_member. Please see the Introduction to the API for a more detailed explanation of how to use the API methods.

Handler callbacks must have exactly two positional arguments - that's just how python-telegram-bot is designed. That's why your first approach doesn't work.

Moreover, Chat.ban_member is a bounded method, not a class/static method. Chat is a class, not an instance of that class, so Chat.ban_member(user_id) can't work either. You need an instance of the Chat class to call that method. In your case probably update.chat_member.chat or update.effective_chat (the latter being a shortcut for the former).

Disclaimer: I'm currently the maintainer of python-telegram-bot.

I never tested it before but it seems you have it in documentation as deep linking.

start=something should run command /start something

Link can use only start or startgroup

You can do this:

Firstly, the error you get is clear. The Session of your userbot has not yet met the group and cannot identify it based on its ID. You will have to receive any kind of update from that entity first.
See this FAQ entry: https://docs.pyrogram.org/faq/peer-id-invalid-error

Secondly, the group you are trying to forward from may have forwards restricted in its group settings. Since you can forward via an official client, this is likely not the case.

Not sure if this is the intended way, but you can pass the bot the the function by passing it to run_async:

You can de-activate buttons like "Save As..." or "Share to..." by adding a protect_content parameter. It is available for many methods, including sendMessage, sendPhoto, sendDocument.

Of course anything that can be viewed can also be copied in some way or another. Nonetheless it provides some protection.

TBF, I'm not familiar with Google Cloud Run, but if I understand correctly the point is that you code will only be invoked when a request is made to the app, i.e. it's one of those "serverless" setups - is that correct?

If so: What updater.start_polling() does is start a long running background thread that fetches updates continuously. To have your bot responsive 24/7 with this method, your script needs to run 24/7. Now the point of serverless setups is that your code only runs on demand, so for this hosting method a more reasonable approach would be to only invoke your code when your bot receives an update. This can achieved using a webhook instead of long polling. There is a section on this in the PTB wiki. See also this thread about AWS Lambda, which is similar AFAIK.

However one should note that stateful logic like ConversationHandler is hard to realize in such setups: By default ConversationHandler keeps track of the current state in memory, so the information is lost on shutdown of the process. You can use persistence to store the data, but I'm not sure how well this works with serverless setups - there might be race conditions if multiple updates come in at the same time. So another idea would be to switch to a different hosting service that allows to run your process 24/7.

Disclaimer: I'm currently the maintainer of python-telegram-bot.

python-telegram-bot is a library that provides a wrapper for the Telegram Bot API. As such, it provides all the methods from the API as well as auxiliary functionality to build chat bots in general, including downloading files sent by users. Extracting contents from a received PDF file after download is however far beyond the scope of this library.

Of course there are other libraries that provide such functionality and that can be used in combinantion with python-telgram-bot. See e.g. camelot.

Disclaimer: I'm currently the maintainer of python-telegram-bot.