node-ms-teams-webhook
node-ms-teams-webhook copied to clipboard
waigel
Microsoft Teams webhook
* Fix typo in code (`Incomming` -> `Incoming`) * Add response body to error object in case of an API failure
The JSON schema of the incoming webhook request payload is quite elaborate, and obscure at the same time. The Microsoft Teams API isn't making it too easy to troubleshoot deviations....
How can I mock this in my tests? Do you have a simple example, please?
According to [this article](https://devblogs.microsoft.com/microsoft365dev/retirement-of-office-365-connectors-within-microsoft-teams/), MS are retiring webhook connectors in 2024. Specifically, new integrations won't be possible after August 15th, ~~and existing webhooks will stop working after October 1st~~. EDIT:...
Bumps the dependencies group with 17 updates in the / directory: | Package | From | To | | --- | --- | --- | | [chalk](https://github.com/chalk/chalk) | `5.3.0` |...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Bumps the dev-dependencies group with 15 updates in the / directory: | Package | From | To | | --- | --- | --- | | [pkg-pr-new](https://github.com/stackblitz-labs/pkg.pr.new/tree/HEAD/packages/cli) | `0.0.35` |...
Bumps the npm_and_yarn group with 1 update: [next](https://github.com/vercel/next.js). Updates `next` from 15.1.0 to 15.1.2 Release notes Sourced from next's releases. v15.1.2 [!NOTE] This release is backporting bug fixes. It does...
Bumps the npm_and_yarn group with 1 update in the /apps/convert-website directory: [next](https://github.com/vercel/next.js). Updates `next` from 15.1.0 to 15.1.2 Release notes Sourced from next's releases. v15.1.2 [!NOTE] This release is backporting...