Forum Discussion
HttpPost in Notifications via Webhook Connector on teams is failing with InternalServerError
bharath_yarlagadda - Thanks for reporting your issue.
Could you please verify below checkpoints?
-
Check the webhook.site URL permissions: Ensure that the webhook.site URL is added as an Action URL in the connector developer dashboard and as a valid domain in the connector manifest.json.
-
Check the format of your JSON payload: Ensure that the JSON payload you're sending is correctly formatted. Incorrectly formatted JSON can often lead to errors.
-
Check the status of the webhook.site: If the issue persists, try using a different webhook.site. There might be an issue with the current webhook.site you're using.
-
Check the API called Execute Action: If you're receiving a 403 forbidden error, it might be due to the API called Execute Action. Ensure that this API has the correct permissions to execute.
- bharath_yarlagaddaOct 11, 2023Copper Contributor
1. I tried with a different webhook site link. I m able to make this call and see the call pop on the webhook site.
curl -X POST https://webhook.site/86b6a1c9-cca2-4739-bcfa-89728b0edf4f -d '{}'
- bharath_yarlagaddaOct 11, 2023Copper Contributor
step 2:
I even tried an empty json payload to /executeAction
{ "inputParameters": [ { "id": "mc_status_update_action", "value": "investigating" } ], "actionId": "55451c61-97b4-4da0-81b1-743d4efcad91", "potentialAction": "{\"@type\":\"HttpPOST\",\"@id\":\"55451c61-97b4-4da0-81b1-743d4efcad91\",\"name\":\"Submit\",\"target\":\"https://webhook.site/86b6a1c9-cca2-4739-bcfa-89728b0edf4f\",\"headers\":[],\"body\":\"{}\",\"bodyContentType\":\"\"}", "name": "action/connector", "integrationId": "lk2mssdku5", "meta": "{\"connectorSenderGuid\":\"203a1e2c-26cc-47ca-83ae-be98f960b6b2\",\"providerAccountUniqueId\":\"\",\"connectorConfigurationAlternateId\":\"3207cad15c4e4115a83b4b247ea63d5f\"}", "clientInfo": { "locale": "en-us", "country": "us", "platform": "Web", "clientVersion": "1415/1.0.0.2023092925" } }
It still failed with following error
- bharath_yarlagaddaOct 11, 2023Copper Contributorfor step 3:
I tried different endpoints which are reachable using curl but failing on ms teams.
For step 4:
As you can see in the pictures above executeAction returns status as 200 but fails with ExchangeServerException.