capabilities.work

Team Messaging Incoming Webhook Lifecycle

A 5-step recipe with RingCentral. We can help you get access.

Recipe · 5 steps

Team Messaging Incoming Webhook Lifecycle

with RingCentral

Create, inspect, suspend, reactivate, and delete a Team Messaging incoming webhook.

  1. 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. Read the webhook back to confirm it is active and to capture the posting URI that gets handed to the external system.
  3. 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. Reactivate the suspended webhook so the original URI resumes delivering into the chat.
  5. Permanently delete the webhook when the integration is retired. The URI stops working immediately and cannot be recovered.
What you'll need to have ready
  • groupId: Internal identifier of the group or team the webhook posts into. This is the same id returned when a team is created.
For your developer

Arazzo workflow ringcentral:team-messaging-webhook-lifecycle, 5 operations: createGlipGroupWebhookNew → readGlipWebhookNew → suspendGlipWebhookNew → activateGlipWebhookNew → deleteGlipWebhookNew. Specs on APIs.io.

More recipes with RingCentral

Send an A2P SMS Batch and Reconcile StatusesSync the Call Log and Retrieve RecordingsTranscribe and Summarize a Call RecordingProvision a User Extension and Send the Welcome EmailExport the Message Store for ComplianceRead and Update User PresenceRingOut Click-to-Call with Status TrackingSend a Fax and Retrieve the Sent DocumentSend an SMS and Track Its DeliveryCreate a Team, Add Members, and Post a Message