Rinkel connector for Okou
Connect Rinkel to read and manage business phone users, numbers, calls, recordings, voicemails, and webhooks through its official REST API.
Communication · API Key
Use Rinkel in Okou
Rinkel business telephony REST API for users, numbers, call detail records, recordings, voicemails, music on hold, and webhooks.
Once connected, supported Rinkel actions can become steps in a reusable workflow alongside the other services your team uses. Run the workflow once, on a schedule, or when an event starts it.
What you can do with Rinkel
- Read token-gated audio for voicemails, recordings, call recordings, and music-on-hold files. Treat access tokens in URLs as reusable credentials.
- Read call detail records that can include reusable avatar or media access URLs.
- Retrieve a temporary URL for streaming or downloading a call recording; the URL is reusable access for three hours.
- Start an outgoing call through the Rinkel account; this is an external side effect and may incur provider charges.
- Validate a phone number using the Rinkel API.
- Read music-on-hold files and their metadata.
- Cancel a Rinkel phone number.
- Block or unblock numbers for the Rinkel account.
How the Rinkel connector works
A connected service becomes one permissioned step in the work you hand off.
- 1
Connect Rinkel
Choose API Key.
- 2
Choose the work
Use only the supported actions your workflow needs.
- 3
Run it your way
Start it once, schedule it, or attach an event trigger.
Connect Rinkel securely
Use the connection method that fits your account and grant only the access the workflow needs.
- API Key
Connector access is controlled per service and per action, so a workflow does not need broader access than the work you ask it to do.
What Rinkel covers
The topics this connector's published operations touch.
- business telephony
- phone system
- call recordings
- voicemail
- webhooks
- crm
Rinkel connector questions
- What can Okou do with Rinkel?
- Connect Rinkel to read and manage business phone users, numbers, calls, recordings, voicemails, and webhooks through its official REST API. Documented actions include: Read token-gated audio for voicemails, recordings, call recordings, and music-on-hold files. Treat access tokens in URLs as reusable credentials. Read call detail records that can include reusable avatar or media access URLs.
- How do I connect Rinkel to Okou?
- Connect Rinkel using API Key. The connection controls which supported actions a workflow can use.
- Can Rinkel run in an automated workflow?
- Yes. After it is connected, supported Rinkel actions can run in reusable Okou workflows on demand, on a schedule, or from an event trigger.
More communication connectors
Explore other connectors in the same product category.
Rocket.Chat
Connect a Rocket.Chat workspace to inspect channels, direct messages, users, threads, and send messages through the official REST API.
Ringover
Connect your Ringover account to read team communications, contacts, call history, transcriptions, and AI call insights.
Ryver
Connect Ryver to read teams, forums, chat, tasks, members, and organization users, with opt-in administration actions.
