RocketChat / RocketChat/Rocket.Chat
chatbot not able to answer to livechat
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
I have a RASA bot and configured following the documentation.
It works on the #general channel
If I try to use it in the omnichannel-livechat it is not invoked.
It seems that the outer webhook do not listen to queues created with livechat.
I've tryed to configure to listen to all public channel, to all DM with no luck.
Any hints on what to configure because in the rasa logs it is not called once.
Queues comes as "guest-X" and we obviously need also to be able to answer to guests.
Steps to reproduce:
- register a rasa bot following doc
- activate omnichannel-livechat
- use livechat and try to talk to bot, bot ignores even if correctly assigned to chat
Expected behavior:
Bot invoked
Actual behavior:
The bot is not invoked and stays idle, probably due to integration hook not used
Server Setup Information:
- Version of Rocket.Chat Server: 3.7.1
- Operating System:
- Deployment Method: docker
- Number of Running Instances:
- DB Replicaset Oplog:
- NodeJS Version:
- MongoDB Version:
Client Setup Information
- Desktop App or Browser Version: chrome
- Operating System:
Additional context
RASA running in container
Relevant logs:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the RASA integration documentation and the omnichannel-livechat webhook and queue configuration described in the report. Reproduce the issue with a guest livechat queue, then trace whether the integration receives the message; done means the RASA bot is invoked and can answer guest conversations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100