I've got Dialogflow bot integrated with Telegram. I decided to change bot in Telegram. Created a new one, deleted the previous one in Telegram. But haven't stopped it in Dialogflow before these operations. Now whenever I try to stop it, Dialogflow reports error and doesn't stop it.
The error says:
com.google.apps.framework.request.BadRequestException: {"ok":false,"error_code":401,"description":"Unauthorized"}
Also it's not possible to create a new agent, bcs Dialogflow doesn't allow to use the same GCP project. And I cannot delete existing one.
How can I stop it to change API Token now? Or delete the existing agent?
Related
Let's assume a user chats with another user in a 1:1 chat. (Might also be a group chat.) The user adds a bot and continues to chat while the bot now adds value to the conversation.
We are searching for a way to make adding the bot to a chat as seamless as possible through a simple button click. It seems the closest we can get to a button is using a messaging extension action command.
When the user invokes the messaging extension our backend service runs and can respond e.g. with a card. Now instead of a card is it possible to generate a response to add a bot? There are special responses e.g. for authentication. Is there a response telling the Teams client to add a bot?
Any hints are appreciated.
JIT installation of bot is an option here. You will be able to add bot to user conversation. Check following sample application which helps to add bot instantly: https://github.com/SubbaReddi/89.teams-just-in-time-installation
I created a bot in SAP CAI and integrated the bot with Microsoft Azure. Testing the bot in Azure's webchat was successful. I want the bot to be voice-activated, so I connected the bot with Cortana.
I was able to call the bot and give permission for use on my phone's Cortana app. However, when I invocate the bot afterwards, the bot times out.
Cortana Conversation
Text version of conversation:
Me: Tell Work Order Notification (Work Order Notification = Invocation Name)
Cortana: I'm getting you connected to my-awesome-vaam-bot...
C: Working on it.
C: Working on it.
C: Sorry, but my-awesome-vaam-bot isn't responding right now. Try again later.
In the Azure portal, under the Channels tab, I received two errors after each invocation:
There was an error sending this message to your bot: HTTP status code GatewayTimeout
There was an error sending this message to your bot: HTTP status code BadRequest
How can I solve this problem?
I'm trying to get Slack to prompt the user to sign in with their Google account (account link) before they can use my Dialogflow chatbot in Slack. The reason being, is that I need access to their calendar in order to create and modify the events, among other things.
Simply following the Slack integration instructions on the 'Integrations' page in the Dialogflow console didn't work. It immediately installed the app.
I've been trying to implement the preview version of Microsoft's BotFramework for NodeJS SDK v4 on Teams as mentioned here. I've set up the messaging endpoint in the Azure portal and I'm able to receive the message events just fine.
I've tried out other bots in the Teams Store such as Hipmunk and they seem to be able to proactively message the users as soon as they get added on to the work space.
I've been through the documentation already and I know that I would need to work upon a ConversationUpdate event that fires in the event of a bot user being added to a team, but unfortunately I haven't received any such events. I've wired it up to be able to receive it because the handlers do work when I test the bot in web chat on the Azure portal. Is this some sort of bug in the Teams client itself or is there any alternative documentation that I've been missing. Please let me know if any code samples or further links are required to aid you in helping me as this is a pretty critical integration for me and my company.
I created a web app bot using the LUIS template on Azure. The bot reaches the default intents created (Greeting, Help, Cancel and None), but gives a "Sorry, my bot code is having an issue" error message when I invoke newly created intents in LUIS.
The newly created intents are reached successfully using the LUIS Test platform and when I query the LUIS endpoint, so it seems the issue is from the bot.
I can't figure out what's causing this issue.
Turns out I have to manually define the handlers for the newly created intents under the BasicLuisDialog.cs, thought the publish takes care of this.