Start free
RPer-pair page

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.

Connect RingCentral to Slack — start free See reverse direction
R
Trigger app
RingCentral as the trigger

Workflows fire when something happens in RingCentral.

Action app
Slack as the action

Workflows do something in Slack, instantly.

See all 45 actions →
Connect RingCentral to Slack — start free
Both directions

Pick the way that fits your stack.

Pair pages are mirrored. Each direction gets its own dedicated page.

RRingCentral → Slack

When something happens in RingCentral, do it in Slack.

3 RingCentral triggers wired to 45 Slack actions. Most-used pairing: RingCentral Call Completed → Add Reaction.

RSlack → RingCentral

Or fire it the other way around.

13 Slack triggers wired to 6 RingCentral actions downstream.

See Slack → RingCentral →
Popular pairings

Common RingCentral → Slack workflows.

Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.

Showing 9 of 135 combinations
R
When ringcentral call completed in RingCentral, add reaction in Slack.

Fires when a phone call completes. Payload includes duration, parties, recording URL if recording was on. For "log call to CRM after completion" workflows.

R
When ringcentral call completed in RingCentral, raw api request in Slack.

Fires when a phone call completes. Payload includes duration, parties, recording URL if recording was on. For "log call to CRM after completion" workflows.

R
When ringcentral call completed in RingCentral, archive channel in Slack.

Fires when a phone call completes. Payload includes duration, parties, recording URL if recording was on. For "log call to CRM after completion" workflows.

R
When ringcentral call completed in RingCentral, cancel scheduled message in Slack.

Fires when a phone call completes. Payload includes duration, parties, recording URL if recording was on. For "log call to CRM after completion" workflows.

R
When ringcentral sms received in RingCentral, add reaction in Slack.

Fires on incoming SMS. For business-SMS workflows that need to route inbound customer texts to the right team.

R
When ringcentral sms received in RingCentral, raw api request in Slack.

Fires on incoming SMS. For business-SMS workflows that need to route inbound customer texts to the right team.

R
When ringcentral sms received in RingCentral, archive channel in Slack.

Fires on incoming SMS. For business-SMS workflows that need to route inbound customer texts to the right team.

R
When ringcentral sms received in RingCentral, cancel scheduled message in Slack.

Fires on incoming SMS. For business-SMS workflows that need to route inbound customer texts to the right team.

R
When ringcentral voicemail received in RingCentral, add reaction in Slack.

Fires when a voicemail lands. Useful for "auto-transcribe via AssemblyAI → ping the recipient with the text" or "VIP caller voicemail → priority alert" workflows.

How it works

Connect RingCentral and Slack in five steps.

No code, no glue, no half-day setup. Each step is one click.

  1. 1
    Connect
    Authorize RingCentral and Slack

    Open TinyCommand, authorize RingCentral and Slack once each. Both connections are available to every workflow on your account.

  2. 2
    Trigger
    Pick a RingCentral trigger

    Drop the RingCentral → RingCentral Call Completed trigger onto the canvas. TinyCommand auto-registers the webhook.

    POST /v1/webhooks/ringcentral.trigger-call-completed
  3. 3
    Transform
    Add a filter or AI step

    Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.

  4. 4
    Action
    Add the Slack action

    Drop the Slack → Add Reaction action below it. Map fields from the RingCentral payload into the Slack inputs.

    slack.add-reaction
  5. 5
    Publish
    Publish and forget

    Hit Publish. TinyCommand runs it in production from second one. Watch the run-log fill up.

FAQ

Questions about RingCentral + Slack.

How long does it take to connect RingCentral and Slack on TinyCommand?
Under two minutes. Authorize RingCentral and Slack once each, drop the RingCentral trigger and Slack action onto a workflow canvas, map a couple of fields, and publish. No code, no glue.
Is the RingCentral ↔ Slack integration real-time?
Yes. Both RingCentral and Slack expose webhooks, so events from one fire workflows in the other within seconds rather than on a polling interval.
Can I filter or transform data between RingCentral and Slack?
Yes. Add a Filter node to only pass through matching events, a Switch node to branch by value, or an AI / Code node to transform payloads before they hit Slack.
What RingCentral events can trigger a Slack workflow?
Any of the 3 RingCentral triggers, including "RingCentral Call Completed". Each fires in real time when the matching event happens in RingCentral.
Do I need a paid plan to use RingCentral with Slack?
No. There's a free tier that covers most RingCentral+Slack use cases without a credit card. Paid plans unlock higher run volumes and team features when you outgrow it.
What if I want Slack → RingCentral instead?
Build it the same way, in reverse. There's a dedicated /integrations/slack/with/ringcentral page with the reverse-direction triggers and actions.
Related

Other apps that pair well with RingCentral.

R+
RingCentral + Gmail
Email
R+
RingCentral + Google Sheets
Spreadsheets & Databases
R+
RingCentral + HubSpot
CRM & Sales
R+
RingCentral + Stripe
Payments
R+
RingCentral + Notion
Productivity
R+
RingCentral + Airtable
Spreadsheets & Databases
Connect RingCentral to Slack — start free