自定义 Microsoft Teams 连接器根本不与外部服务通信

问题描述

通用说明

首先，我的目标是使用内部 API 将来自我的服务的通知发送到 MT 通道，并且可以选择将通知发送到内部 API.

我发现连接器具有这样的功能.我尝试使用

1. 从 [github 连接器示例][3] 运行 nodejs 代码(它没有意义，因为完全没有请求)

我的预期:

外部服务中的任何活动，我无法监控的其他集成节点.我将这个失败的结果与 StackOverflowConnector 和我的机器人体验进行了比较，两者都可以根据需要工作.

问题:

如何设置连接器工作，发送网络请求?至少要有回声逻辑.

更新:

我注意到一个关于删除连接器的 MT 应用程序的奇怪报告.

解决方案

我相信您可能对 Bot 和 连接器.根据您的帖子描述，您应该创建一个Bot 而不是连接器.如果您有进一步的疑问，请告诉我们.

更新:

您能否尝试一下 C# 示例 代码?以下是您理解的基本流程:

1. 当用户点击访问站点以安装时，设置 端点被命中.
2. 当用户点击连接到 Office 365 时，注册端点被网络钩子信息命中.
3. 在系统中创建新任务后，您可以使用 网络钩子网址.

Common description

First, my goal is sending notifications from my service using an internal API to a MT channel and having an option to answer it transmitting one to internal API.

I've found a Connector has such functionality. Good example which i've tried to use StackOverflowConnector. It was a good point to start that is exactly what i need(Bot has inappropriate UI behaviour) , but i've decided to do it by small steps from creating a Bot just to understand things better. In short i had success, the bot and a mt channel communicted well both directions. Next point was Connector. I explored all information here:

1. https://docs.microsoft.com/en-us/microsoftteams/platform/index
2. https://docs.microsoft.com/en-us/azure/bot-service/?view=azure-bot-service-3.0
3. https://docs.microsoft.com/en-us/outlook/

What i have taken to create a Connector

1. registered a Connector in the Connectors Developer Dashboard with followed fields:

   • Connector name: connector

   • Logo: contoso96x96.png

   • Short description of your app (10 words or less): sd

   • Detailed description of what your Connector does (3-5 sentences): dd

   • Company website: https://external.service

   • List the events supported by your Connector: all

   • Do you want to enable actions on your Connector cards?: Yes

   • Actions URL: https://external.service/api/messages

   • Does your service support login using subdomain?: No

   • Landing page for your users for Inbox: https://external.service

   • Landing page for your users for Groups or Teams: https://external.service

   • Redirect URLs: https://external.service/api/messages

2. Ran the external service to communicate with a Connector. Checked service works

3. took a manifest.json file is generated by Connectors Developer Dashboard and uploaded it to a Microsoft Team(MT) team. Uploading was successful. There was no network requests(monitored nginx logs) to the external service

4. selected a channel in MT and clicked the Connectors dialog option. Found the created connector in the list Sideloaded group and clicked Configure. Got such window and clicked Done. Nothing happened

1. ran nodejs code from the [github connector example][3](it didn't have meaning because of total lack of the requests)

What i expected:

Any activity in the external service, other nodes of integration i can't monitor. I compare this failed result with ones of StackOverflowConnector and my bot experience, both works as needed.

Question:

How to set up the connector to work, to send network requests? At least to have echo logic.

Upd:

I have noticed a weird report of deleting a MT app of the connector.

解决方案

I believe you might have some confusion between a Bot and a Connector. Based on your post description you should be looking to create a Bot and not a Connector. Please let us know if you have further queries.

Update:

Could you please give a try with C# sample code? Here is the basic flow for your understanding:

1. When user clicks on Visit Site to install the Setup endpoint is hit.
2. When user clicks on Connecto to Office 365 the Register endpoint is hit with webhook information.
3. When new task is created in your system you can post the message to registered channels using webhook url.

这篇关于自定义 Microsoft Teams 连接器根本不与外部服务通信的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！