Connect RingCentral to Slack in two minutes.
Real-time triggers from RingCentral, ready-made actions in Slack. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in RingCentral.
- RingCentral Call CompletedWebhook
- RingCentral SMS ReceivedWebhook
- RingCentral Voicemail ReceivedWebhook
Workflows do something in Slack, instantly.
- Raw API RequestAPI
- Add ReactionAPI
- Archive ChannelAPI
- Cancel Scheduled MessageAPI
- Create CanvasAPI
- Create ChannelAPI
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in RingCentral, do it in Slack.
3 RingCentral triggers wired to 45 Slack actions. Most-used pairing: RingCentral Call Completed → Raw API Request.
Or fire it the other way around.
13 Slack triggers wired to 6 RingCentral actions downstream.
See Slack → RingCentral →Common RingCentral → Slack workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a phone call completes. Payload includes duration, parties, recording URL if recording was on. For "log call to CRM after completion" workflows.
Fires when a phone call completes. Payload includes duration, parties, recording URL if recording was on. For "log call to CRM after completion" workflows.
Fires when a phone call completes. Payload includes duration, parties, recording URL if recording was on. For "log call to CRM after completion" workflows.
Fires when a phone call completes. Payload includes duration, parties, recording URL if recording was on. For "log call to CRM after completion" workflows.
Fires on incoming SMS. For business-SMS workflows that need to route inbound customer texts to the right team.
Fires on incoming SMS. For business-SMS workflows that need to route inbound customer texts to the right team.
Fires on incoming SMS. For business-SMS workflows that need to route inbound customer texts to the right team.
Fires on incoming SMS. For business-SMS workflows that need to route inbound customer texts to the right team.
Fires when a voicemail lands. Useful for "auto-transcribe via AssemblyAI → ping the recipient with the text" or "VIP caller voicemail → priority alert" workflows.
Connect RingCentral and Slack in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize RingCentral and Slack
Open Tiny Command, authorize RingCentral and Slack once each. Both connections are available to every workflow on your account.
- 2TriggerPick a RingCentral trigger
Drop the RingCentral → RingCentral Call Completed trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/ringcentral.trigger-call-completed - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Slack action
Drop the Slack → Raw API Request action below it. Map fields from the RingCentral payload into the Slack inputs.
slack.api-request - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about RingCentral + Slack.
How long does it take to connect RingCentral and Slack on Tiny Command?
Is the RingCentral ↔ Slack integration real-time?
Can I filter or transform data between RingCentral and Slack?
What RingCentral events can trigger a Slack workflow?
Do I need a paid plan to use RingCentral with Slack?
What if I want Slack → RingCentral instead?
Other apps that pair well with RingCentral.
Wire RingCentral to Slack in 2 minutes.
Free tier available. No credit card. No onboarding call.
