I'm using Microsoft's botframework to create a Slack bot, however I'm running into 2 problems.
When I do "Test connection to your bot" I'm getting
InternalServerError
no_text
When I type in the test chat console on the botframework page, the messages are received in my slack general channel. However, when I as a user in my slack and type in the general channel, whatever I type the bot also generate the same message. i.e.
me: Hello
bot: Hello
I think it's how I set up my configuration for the slack bot app and/or the messaging endpoint of my botframework bot.
Thanks.
Related
Scenario:-
User A -> Types a message in Teams App (bot)
Now Bot has to reply to the same thread that user A has started in Teams App (bot)
I am able to send a new message in the Teams App (bot) - Not expected
The bot needs to reply to the same thread the user started - Expected
Did not find any reply method in the below documentation.. continueConversation creates a new message.
https://learn.microsoft.com/en-us/javascript/api/botbuilder-core/turncontext?view=botbuilder-ts-latest#botbuilder-core-turncontext-getmentions&preserve-view=true
https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/conversations/conversation-basics
The bot cannot give the reply to the same thread that user started. This is by design behaviour.
Bot can reply to an existing message but it looks new message not like reply, call ReplyToActivity in .NET or session.send in Node.js. The Bot Builder SDK handles all the details.
If you choose to use the REST API, you can also call the /v3/conversations/{conversationId}/activities/{activityId} endpoint.
Ref Doc: https://learn.microsoft.com/en-us/microsoftteams/platform/resources/bot-v3/bot-conversations/bots-co...
If you wish you can suggest this feature on - Microsoft Teams ยท Community
Up until this Friday, MS Teams would always send a conversationUpdate event payload to our bot messaging endpoint whenever a user installed our app in Teams.
This stopped happening suddenly and now we only get a message when an app is added to a Team scope and not just personal scope.
Given that: how do we know to send a Welcome message via our bot to a user that installed our app if we receive no message, no payload. Nothing hits our bot messaging endpoint.
I have been working on azure chat bot using the bot framework SDK v4 and I have ran into an issue. My bot needs to initiate a conversation first. I have seen some examples with proactive bot but that requires us to save the user credentials as a cookie. What I need is a chat bot that sends the first message to user via SMS to initiate the conversation. The bots needs to be able to set the recipient phone number dynamically. I have looked at integrating the Twillio channel to my bot, but the problem is that the user has to initiate the conversation to the Twillio phone number which then forwards the text to Azure chat bot. I was wondering if there is anything out there which will allow the chat bot to initiate the conversation first via SMS and the phone number of the recipient should be set dynamically. Is there anything out there currently on Microsoft stack? Our company has been a long partner with Microsoft so I would like to have the chat bot using the Microsoft Azure Bot Service. Can you please guide me or forward some documentation? Any help would be appreciated.
I'm working on an integration between Microsoft Teams and Slack.
I'm building a Microsoft Teams application which is connected to a Microsoft Bot.
Additionally, I created a server for:
Listening to messages which were sent by users in Slack (via Slack webhooks)
Posting them in Microsoft Teams conversation as a user message to the bot (outgoing message)
I receive messages from Slack (which were sent by a Slack user) to my server and I wish to post them in Microsoft Teams as messages from the user to the bot and I'm not able to do so.
I'm able to send messages from Bot to user in Microsoft Teams app via Microsoft Bot's "botbuilder" Node.js SDK:
session.send(message);
How can I send the message on the other direction (from user to bot)?
You can't. See this question for more info, but the short version is:
The BotFramework has no direct way to do this.
Even the Teams Graph API doesn't currently support this. They're working on it, but don't have an ETA.
The closest thing to a workaround would be:
User writes message in Slack to Bot
Bot receives message and posts a proactive message in Teams, something like:
User #louis1600 said: "blah blah blah"
Resources:
Proactive Messages in Teams
#mention-ing users in Teams with a Bot
The many other Teams Bot related questions I've answered
I am using Microsoft Botframework to publish a bot (Channel Registration). When I try enabling the channels , I see the bot to be working in Slack , Skype, MS Teams & Web chat . However (despite following the steps to enable bot in SFB) I could not get the bot working in Skype for Business. I keep getting the error.
"Sorry, we ran into a problem at our end."
Neither do I see any log to debug.
Waited more than 24 hrs to ensure it is not the sync issue. But issue still remains. Any help appreciated !!
I am not clear with the error as to from which end it is being thrown.
I need you to follow the below steps:
Publish Bot in azure as an app service, through VS if you are coding through c#.
Create a "Bot channel registration" in azure and connect the above app service and Bot channel registration(simple use the URL of the app service append it with /api/messages and insert the same as messaging endpoint in Bot channel registration).
use the app id and app secret in bot solution and republish the app service.
Inside Bot channel registration click on channel and enable it for Skype for business(you will find your BOT in SFB using the credentials you have used to create the bot channel registration).
Finally got it working. What i noticed is the following
I faced the issue when I used the SIP URI as somebot#mydomain.com to register the bot in my tenant.
And i got it working when I used the SIP URI as somebot#mydomain.onmicrosoft.com.
Unsure on the reasoning though :)
And btw thanks #Tanmoy for your answer aswell !!