Overview
Connect RingCentral with Flows360
Cloud business communications: send SMS, place calls, manage messages, and post to Team Messaging.
Use the RingCentral connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 8 actions and 3 triggers.
Available actions
- Send SMS
- Make Call (RingOut)
- Send Team Messaging Post
- Get Call Log
- Get Extension Info
- Get Message
- Download Message Attachment
- Custom API Call
Available triggers
- New Inbound SMS or MMS
- New Voicemail
- New Team Messaging Post
The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.
Technical guide
Technical reference
Package identity
- Connector: RingCentral
- Package:
@activepieces/piece-ringcentral@0.1.0 - Exact artifact digest:
sha256:a8899713be87d20a4bc05b60d22341fcb58b448debed08a209f8f301a03d9192 - Runtime: Activepieces-compatible deterministic worker
- Source: the exact reviewed Activepieces source
Authentication
OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.
Action contracts
- Send SMS (
send_sms), Send an SMS text message from one of your RingCentral numbers. Classification: read. - Make Call (RingOut) (
make_call), Start a two-legged RingOut call: RingCentral calls the "from" number first, then connects it to the "to" number. Classification: read. - Send Team Messaging Post (
send_team_message), Post a message to a RingCentral Team Messaging chat, group, or team. Classification: read. - Get Call Log (
get_call_log), Retrieve call log records for the authenticated user's extension. Classification: read. - Get Extension Info (
get_extension_info), Get profile information for the authenticated user's extension. Classification: read. - Get Message (
get_message), Retrieve a single SMS, MMS or voicemail message, including the list of attachments it carries. Classification: read. - Download Message Attachment (
download_message_attachment), Download the content of a message attachment, such as an MMS photo or a voicemail recording, and return it as a file. Classification: read. - Custom API Call (
custom_api_call), Make a custom API call to a specific endpoint Classification: read.
Trigger contracts
- New Inbound SMS or MMS, webhook.
- New Voicemail, webhook.
- New Team Messaging Post, webhook.
Verification
Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.
Capability summary
Authentication
Authentication method: custom
Authentication profiles
connection · custom
- Access token Required · protected credential
- Environment Required
Triggers
New Inbound SMS or MMS · Webhook
Triggers when a new inbound text message is received, with or without media attached.
New Voicemail · Webhook
Triggers when a new voicemail message is received.
New Team Messaging Post · Webhook
Triggers when a new post is added in RingCentral Team Messaging.
Setup
Setup
- Add the RingCentral connector to the workflow in the target Flows360 Studio instance.
- Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
- Provide the connection fields declared by the pinned package:
- Environment (
environment), required.
- Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
- Test the workflow in the appropriate environment before enabling production scheduling or event delivery.
Limitations
Limitations and operational notes
- This content describes
@activepieces/piece-ringcentral@0.1.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes. - Only the 8 actions and 3 triggers declared by this pinned package are represented here.
- Tenant credentials and connection values are not stored in the public connector record.
- Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
- Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.
Troubleshooting
Why canu2019t the connector authenticate?
Check the tenant connection in Studio and confirm every required RingCentral connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.
Why is an action or trigger unavailable?
Confirm that the workflow is using @activepieces/piece-ringcentral@0.1.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.
What should I check after a provider-side change?
Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.