Summary
The Microsoft Teams channel in HolderChat does not post a notification into a Teams channel, and it does not use a standard Teams Incoming Webhook or a default Teams Workflows webhook.
Instead, when a visitor asks for a person, HolderChat sends an HTTP POST to a URL you configure. That URL must create a Microsoft Teams meeting and return the join link. HolderChat then shows the visitor a “Join Microsoft Teams Meeting” link in the chat.
HolderChat does not send the visitor’s question, language, or conversation id in that request. If your team needs to see the question in Teams, your own endpoint or process must handle that separately — the product does not do it today.
Prerequisites
- A HolderChat chatbot. You will configure the channel on the Support tab.
- An HTTPS endpoint that you control (for example a Power Automate HTTP trigger, Azure Function, or similar service) and that can create a Teams meeting for your organization.
- The endpoint must accept the request body below and return the exact JSON shape HolderChat expects.
What the dashboard fields mean
| Field | What to enter | Example |
|---|---|---|
| URL | The HTTPS endpoint that creates the meeting. This is not a meeting join link such as https://teams.microsoft.com/l/meetup-join/.... Pasting a join link here will not work. |
https://example.com/holderchat/create-teams-meeting |
| Subject | Title sent to your endpoint as the meeting subject. | Website support request |
| Thema | Topic name the chatbot uses to select this channel. Several topics can be separated with a semicolon. | Technical Support or Sales; Onboarding |
| Duration (minutes) | Meeting length sent to your endpoint, as a positive integer. | 30 |
Required endpoint contract
When a handoff happens, HolderChat sends:
POST https://example.com/holderchat/create-teams-meeting
Content-Type: application/json
{
"subject": "Website support request",
"startTime": "2026-11-21T15:04:05.123456",
"duration": 30
}
startTime is the current time on the HolderChat server, in ISO 8601 format. duration is the number of minutes from the dashboard. The request is sent without an authentication header or signature.
Your endpoint must respond with HTTP status 200 and JSON in this shape:
{
"result": "OK",
"meetingUrl": "https://teams.microsoft.com/l/meetup-join/EXAMPLE-MEETING-ID"
}
If the status is not 200, or result is not exactly OK, the visitor sees an error instead of a join link.
outlook.office.com/webhook URLs, retired in 2026) are not used. A default “Post to a channel when a webhook request is received” Workflow also does not match this contract, because HolderChat posts subject, startTime, and duration, and then looks for result and meetingUrl in the response.
If you want to use Power Automate or a similar tool, you must build a custom flow or function that: receives this JSON, creates a meeting in your Microsoft 365 tenant, and returns the JSON above. That flow is configured on your side, not inside HolderChat.
Step-by-step: Add the channel in HolderChat
- Build and test your meeting-creation endpoint so that a sample POST with the body above returns
result: "OK"and a realmeetingUrl. - In the HolderChat dashboard, open the chatbot and go to the Support tab.
- Under Add Support Channel, select Microsoft Teams and click Add.
- Paste the endpoint URL into URL (not a
meetup-joinlink). - Enter a Subject, a Thema, and a Duration in minutes, for example
30. - Save the chatbot settings. You do not need to click Rebuild Bot.
Step-by-step: See the first meeting link
- Open Test Chatbot.
- Ask to speak with a person and, if needed, name the Thema you configured.
- If the endpoint returns a meeting URL, the chatbot shows an invitation such as: “I’ve created a Microsoft Teams meeting for you. Please join the meeting to speak with our support team,” followed by a Join Microsoft Teams Meeting link.
- Open the link and confirm that the meeting is valid for your team.
What triggers a rebuild
| Action | Rebuild needed? |
|---|---|
| Add, edit, or remove a Teams channel | No |
Limitations
- This is a meeting-link handoff, not a two-way Teams chat with the website widget.
- The visitor’s question is not included in the POST body, so a Teams channel will not see the chat text unless you add that yourself outside HolderChat.
- HolderChat waits up to 10 seconds for your endpoint. There is no automatic retry if the request fails.
- The request is not signed. Protect your endpoint as you would any public HTTP trigger (a secret in the URL path, IP allowlisting, or a similar control on your side).
- Do not paste a personal meeting join link into the URL field. HolderChat must be able to POST JSON to that address.
Troubleshooting
Symptom: The visitor sees “Failed to create meeting in Teams” or a generic support error
Cause: The URL is a join link rather than an endpoint, the endpoint did not return HTTP 200, or the JSON did not contain "result": "OK" and meetingUrl.
Fix: Call the endpoint with the sample body above. Confirm a 200 response and the required JSON keys. Then paste that same endpoint URL into the Support tab.
Symptom: Nothing appears in a Teams channel
Cause: This integration does not post messages to a channel.
Fix: Check whether a meeting was created and whether the visitor received a join link. To notify a channel, extend your own endpoint; HolderChat does not offer that today.