-
Notifications
You must be signed in to change notification settings - Fork 1
Feature: Added messenger integration (Telegram) #147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
- Add fi_messenger.py with unified forwarding logic for both platforms - rick_bot uses Telegram integration to forward messages via GraphQL to v1_backend
humbertoyusta
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't we need captured threads logic like slack and discord? Are they in another pr? Or will these messengers work differently? I guess we want to communicate in kinda real time with user after it wrote right? Feels like capture logic
- generate_telegram_invite tool - generate_guest_url tool - fi_telegram.py integration managed fully by bots
| "platform": handle_result["platform"], | ||
| } | ||
|
|
||
| async def should_restart_thread(self, thread) -> tuple[bool, str]: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if has passed more than 10 minutes since last message, also should be triggered
Relies on PR https://github.com/smallcloudai/flexus/pull/1228