Home

Error when sending messages using our connector

%3CLINGO-SUB%20id%3D%22lingo-sub-290337%22%20slang%3D%22en-US%22%3EError%20when%20sending%20messages%20using%20our%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-290337%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20planning%20to%20integrate%20Microsoft%20Teams%20with%20our%20web%20app%20so%20our%20users%20can%20receive%20notifications%20related%20to%20their%20account%20in%20a%20Microsoft%20Teams%20channel.%3C%2FP%3E%3CP%3EWe've%20managed%20to%20create%20the%20connector%20and%20to%20obtain%20the%20webhook%20URL.%20But%20when%20we%20send%20the%20message%20to%20that%20URL%20we%20get%20a%20403%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%3Ecurl%20-H%20%22Content-Type%3A%20application%2Fjson%22%20-d%20%22%7B%5C%22text%5C%22%3A%20%5C%22Hello%20World%5C%22%7D%22%20%3CWEBHOOK%20url%3D%22%22%3E%3CBR%20%2F%3E%3CBR%20%2F%3EWebhook%20message%20delivery%20failed%20with%20error%3A%20Microsoft%20Teams%20endpoint%20returned%20HTTP%20error%20403%20with%20ContextId%20tcid%3D3461410331366056765%20%3CBR%20%2F%3E%2Cserver%3DBL2PEPF000001DC%2Ccv%3DyQTNDnd5pE%2BVYk%2FDxoEV%2BA.0..%3C%2FWEBHOOK%3E%3C%2FPRE%3E%3CP%3EEverything%20works%20fine%20when%20we%20use%20the%26nbsp%3Bbuilt-in%20Incoming%20Webhook%20Connector.%3C%2FP%3E%3CP%3EWhat%20are%20we%20doing%20wrong%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CH4%20id%3D%22toc-hId-1259868812%22%20id%3D%22toc-hId-1309834056%22%3E2nd%26nbsp%3Bday%20updates%3C%2FH4%3E%3CP%3EDifferent%20error%20today.%3C%2FP%3E%3CPRE%3EUnknown%20Connector%20provider%20%7Bconnector_id%7D%3C%2FPRE%3E%3CP%3EWe%20use%20the%20%22upload%20app%22%20feature%20to%20test%20our%20connector.%20That%20is%20the%20connector%20id%20in%20the%20manifest.json%20file.%3C%2FP%3E%3CP%3EThe%20connector%20appears%20in%20our%20team's%20app%20list.%20And%20also%20in%20the%20channel's%20configured%20apps%20list.%3C%2FP%3E%3CP%3EStill%2C%20when%20the%20request%20is%20made%20to%20that%20webhook%20url%20received%20during%20the%20configuration%2C%20that%20error%20comes%20up.%3C%2FP%3E%3CP%3EHelp.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-290337%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-301945%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20sending%20messages%20using%20our%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-301945%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20finally%20%3CSTRONG%3Eworked%3C%2FSTRONG%3E%20but%20only%20when%20the%20user%20that%20created%20the%20team%20uploaded%20the%20app.%20If%20I%20upload%20the%20app%20and%20then%20configure%20it%20to%20a%20certain%20channel%2C%20I%20receive%20a%20403%20status%20when%20I%20send%20the%20message%20to%20that%20webhook%20url.%3C%2FP%3E%3CPRE%3EWebhook%20message%20delivery%20failed%20with%20error%3A%20Microsoft%20Teams%20endpoint%20returned%20HTTP%20error%20403%20with%20ContextId...%3C%2FPRE%3E%3CP%3EThanks%20for%20everything.%20Together%20we%20are%20stronger%20%3A))%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-301261%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20sending%20messages%20using%20our%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-301261%22%20slang%3D%22en-US%22%3E%3CP%3EWorked%20for%20me%20today%2C%20try%20now!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fstackoverflow.com%2Fquestions%2F53561357%2Funable-to-post-to-a-test-connectors-webhook-url%2F53757960%2353757960%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fstackoverflow.com%2Fquestions%2F53561357%2Funable-to-post-to-a-test-connectors-webhook-url%2F53757960%2353757960%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298668%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20sending%20messages%20using%20our%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298668%22%20slang%3D%22en-US%22%3EThat%20is%20good%20news.%20Thanks!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-298608%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20sending%20messages%20using%20our%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-298608%22%20slang%3D%22en-US%22%3E%3CP%3ELooks%20like%20a%20fix%20is%20being%20deployed%20on%20Thursday%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmsteams-docs%2Fissues%2F344%23issuecomment-446050671%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmsteams-docs%2Fissues%2F344%23issuecomment-446050671%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-293484%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20sending%20messages%20using%20our%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-293484%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fstackoverflow.com%2Fquestions%2F53561357%2Funable-to-post-to-a-test-connectors-webhook-url%22%20target%3D%22_self%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3EI've%20also%20posted%20on%20StackOverflow%20regarding%20this%20issue.%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-292760%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20sending%20messages%20using%20our%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-292760%22%20slang%3D%22en-US%22%3E%3CP%3EI%20don't%20know%20if%20it%20matters.%20I'm%20thinking%20that%20would%20be%20a%20reason%20why%20the%20Connector%20provider%20is%20unknown%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20able%20to%20save%20the%20configuration%20settings%2C%20after%20side-loading%20the%20app%20-%20but%20I'm%20not%20able%20to%20submit%20to%20any%20webhooks%20that%20were%20generated%20in%20the%20configuration%20screen.%20They%20just%20return%20that%20%22Unknown%20Connector%20provider%2058f...%22%20error%20message%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20created%20this%20issue%20for%20it%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmsteams-docs%2Fissues%2F344%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmsteams-docs%2Fissues%2F344%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%26nbsp%3Bfor%20more%20information%20there%20seems%20to%20be%20a%20guide%20in%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FOfficeDev%2FTrainingContent%2Fblob%2Fmaster%2FTeams%2F02%2520Tabs%2520and%2520Connectors%2FLab.md%23exercise2%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FOfficeDev%2FTrainingContent%2Fblob%2Fmaster%2FTeams%2F02%2520Tabs%2520and%2520Connectors%2FLab.md%23exercise2%3C%2FA%3E%26nbsp%3Band%20a%20video%20%3CA%20href%3D%22https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DwE_w1TA_qjQ%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DwE_w1TA_qjQ%3C%2FA%3E%20that%20I%20was%20able%20to%20find%20only%20due%20to%20the%20author%20commenting%20in%20another%20-%20unrelated%20issue%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmsteams-docs%2Fissues%2F338%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmsteams-docs%2Fissues%2F338%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20try%20and%20look%20through%20it.%20But%20so%20far%20I%20haven't%20seen%20any%20differences%20in%20terms%20of%20setup.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20also%20created%20an%20issue%20regarding%20the%20tutorial%2C%20as%20it%20doesn't%20show%20a%20successful%20webhook%20request.%20The%20screenshot%20is%20pinging%20an%20%22incoming%20webhook%22%20connector%2C%20not%20the%20test%20connector's%20webhook%26nbsp%3Bitself.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2FOfficeDev%2FTrainingContent%2Fissues%2F559%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2FOfficeDev%2FTrainingContent%2Fissues%2F559%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-292659%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20sending%20messages%20using%20our%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-292659%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20issue%20is%20not%20solved.%20Unfortunately.%3C%2FP%3E%3CP%3EYeah%2C%20it%20says%20pending%20approval%2C%20but%20we%20use%20an%20uploaded%20app%20for%20testing.%20So%20that%20shouldn't%20matter%2C%20right%3F%3C%2FP%3E%3CP%3EAlso%20the%20server%20we're%20testing%20the%20integration%20on%20is%20not%20visible%20from%20the%20internet.%3C%2FP%3E%3CP%3EAnyway%2C%20it's%20so%20hard%20to%20find%20any%20working%20example%20in%20one%20place%20so%20if%20you%20have%20any%20info%20to%20share%2C%20it%20would%20be%20awesome.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-292571%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20sending%20messages%20using%20our%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-292571%22%20slang%3D%22en-US%22%3EJust%20a%20side-question%20here.%20When%20you%20view%20your%20connector%20in%20the%20%22Connectors%20Developer%20Dashboard%22%20-%20do%20you%20by%20any%20chance%20have%20a%20%22Pending%20Approval%22%20status%20next%20to%20it%3F%20Trying%20to%20figure%20out%20if%20this%20is%20related.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-292569%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20sending%20messages%20using%20our%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-292569%22%20slang%3D%22en-US%22%3EAlso%20running%20currently%20into%20%22Unknown%20Connector%20provider%20%7Bconnector_id%7D%22%20when%20trying%20to%20ping%20the%20webhook%20url%20we%20received%20in%20the%20configuration.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20is%20for%20a%20side-loaded%20connector%20inside%20Microsoft%20Teams.%20Did%20you%20resolve%20this%20issue%20by%20now%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-291021%22%20slang%3D%22en-US%22%3ERe%3A%20Error%20when%20sending%20messages%20using%20our%20connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-291021%22%20slang%3D%22en-US%22%3E%3CH4%20id%3D%22toc-hId-1259868812%22%20id%3D%22toc-hId--1242322905%22%3E3rd%20Day%20Updates%20-%20New%20day%2C%20new%20Error%3C%2FH4%3E%3CP%3EAt%20the%20end%20of%20the%20configuration%2C%20when%20the%20Save%20button%20is%20clicked%2C%20this%20error%20appears%20in%20the%20page.%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSPAN%3EUnable%20to%20save%20%22Connector%20-%20Staging%22%20connector%20configuration.%20Please%20try%20again.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3EThis%20time%20the%20connector%20doesn't%20appear%20in%20the%20configured%20apps%20list.%20But%20the%20webhook%20URL%20is%20there%20and%20when%20a%20message%20is%20sent%20to%20that%20URL%2C%20this%20NEW%20error%20appears%3A%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3EConnector%20configuration%20not%20found%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3EAnd%20this%20sounds%20accurate%20since%20the%20app%20doesn't%20appear%20in%20the%26nbsp%3B%3CSPAN%3Econfigured%20apps%20list.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStill%20don't%20know%20what's%20causing%20this%20and%20how%20to%20fix%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E
R4ZVAN
Occasional Contributor

We are planning to integrate Microsoft Teams with our web app so our users can receive notifications related to their account in a Microsoft Teams channel.

We've managed to create the connector and to obtain the webhook URL. But when we send the message to that URL we get a 403 error.

 

curl -H "Content-Type: application/json" -d "{\"text\": \"Hello World\"}" <WEBHOOK URL>

Webhook message delivery failed with error: Microsoft Teams endpoint returned HTTP error 403 with ContextId tcid=3461410331366056765
,server=BL2PEPF000001DC,cv=yQTNDnd5pE+VYk/DxoEV+A.0..

Everything works fine when we use the built-in Incoming Webhook Connector.

What are we doing wrong?

 

2nd day updates

Different error today.

Unknown Connector provider {connector_id}

We use the "upload app" feature to test our connector. That is the connector id in the manifest.json file.

The connector appears in our team's app list. And also in the channel's configured apps list.

Still, when the request is made to that webhook url received during the configuration, that error comes up.

Help.

 

 

 

10 Replies

3rd Day Updates - New day, new Error

At the end of the configuration, when the Save button is clicked, this error appears in the page.

Unable to save "Connector - Staging" connector configuration. Please try again.

This time the connector doesn't appear in the configured apps list. But the webhook URL is there and when a message is sent to that URL, this NEW error appears:

Connector configuration not found

And this sounds accurate since the app doesn't appear in the configured apps list.

 

Still don't know what's causing this and how to fix it.

Also running currently into "Unknown Connector provider {connector_id}" when trying to ping the webhook url we received in the configuration.

This is for a side-loaded connector inside Microsoft Teams. Did you resolve this issue by now?
Just a side-question here. When you view your connector in the "Connectors Developer Dashboard" - do you by any chance have a "Pending Approval" status next to it? Trying to figure out if this is related.

The issue is not solved. Unfortunately.

Yeah, it says pending approval, but we use an uploaded app for testing. So that shouldn't matter, right?

Also the server we're testing the integration on is not visible from the internet.

Anyway, it's so hard to find any working example in one place so if you have any info to share, it would be awesome.

 

I don't know if it matters. I'm thinking that would be a reason why the Connector provider is unknown?

 

I was able to save the configuration settings, after side-loading the app - but I'm not able to submit to any webhooks that were generated in the configuration screen. They just return that "Unknown Connector provider 58f..." error message

 

I created this issue for it https://github.com/MicrosoftDocs/msteams-docs/issues/344

 

As for more information there seems to be a guide in https://github.com/OfficeDev/TrainingContent/blob/master/Teams/02%20Tabs%20and%20Connectors/Lab.md#e... and a video https://www.youtube.com/watch?v=wE_w1TA_qjQ that I was able to find only due to the author commenting in another - unrelated issue https://github.com/MicrosoftDocs/msteams-docs/issues/338

 

You can try and look through it. But so far I haven't seen any differences in terms of setup.

 

I've also created an issue regarding the tutorial, as it doesn't show a successful webhook request. The screenshot is pinging an "incoming webhook" connector, not the test connector's webhook itself. https://github.com/OfficeDev/TrainingContent/issues/559

 

Extending a Microsoft Teams app with Tabs and Connectors.
That is good news. Thanks!

It finally worked but only when the user that created the team uploaded the app. If I upload the app and then configure it to a certain channel, I receive a 403 status when I send the message to that webhook url.

Webhook message delivery failed with error: Microsoft Teams endpoint returned HTTP error 403 with ContextId...

Thanks for everything. Together we are stronger :)) 

Related Conversations