RingCentral · Arazzo Workflow
RingCentral Team Messaging Incoming Webhook Lifecycle
Version 1.0.0
Create an incoming webhook for a team, read its address, suspend and reactivate it, and delete it when retired.
Provider
Workflows
team-messaging-webhook-lifecycle
Create, inspect, suspend, reactivate, and delete a Team Messaging incoming webhook.
Creates an incoming webhook against a group/team, reads it back to capture the generated posting URI and status, suspends it to mute delivery, reactivates it, and finally deletes it.
1
createWebhook
Create the incoming webhook for the group. This operation takes no request body — RingCentral generates the webhook and returns its resource, including the URI external systems will post to.
2
readWebhook
Read the webhook back to confirm it is active and to capture the posting URI that gets handed to the external system.
3
suspendWebhook
Suspend the webhook to stop delivery without destroying it. Posts to the URI are rejected while suspended, but the URI survives so the external system does not have to be reconfigured to resume.
4
activateWebhook
Reactivate the suspended webhook so the original URI resumes delivering into the chat.
5
deleteWebhook
Permanently delete the webhook when the integration is retired. The URI stops working immediately and cannot be recovered.
Source API Descriptions
Arazzo Workflow Specification
Work with this as data
Every workflow here is available over the APIs.io API and to AI agents over MCP.