-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trigger start a call from mattermost API #309
Comments
@bayunvnt Nope, unfortunately it's not possible as a call only exists as long as at least one user is connected so to start a call you'd have to create a websocket connection and keep it alive. That said, in the near future we may be able to make this more automatable by relying on the recently introduced Calls bot. By the way, what you are looking to achieve exactly? Getting to understand your use case would be very helpful. |
thankyou for your response, i recently use mattermost for communicating with teams, everyday in the morning we need to do a meeting about taslisks, jobs and etc, i want to automate start a call in the morning with an energic message for the rest of teams so they can join directly without manually start a calls. |
Thanks for the context. I created an internal ticket (MM-49965) to track this as it sounds like a very useful addition. Will give an update here as soon as we get to implement it. |
okay @streamer45, i really appreciate that, thankyou for your cooperation and i'll wait for the update, cheers. |
Hello, i tried to post a "/call start" from API "https://mattermost.domain.id/api/v4/commands/execute", but the calls is not started.
The response code is 200, and this is a full response :
{
"response_type": "",
"text": "",
"username": "",
"channel_id": "",
"icon_url": "",
"type": "",
"props": null,
"goto_location": "",
"trigger_id": "7s7mo33r9bnqirtde22qsjmfmy",
"skip_slack_parsing": false,
"attachments": null,
"extra_responses": null
}
there is any way to trigger call start from an api? thankyou
The text was updated successfully, but these errors were encountered: