Toky
Voice & TelephonyManage agents, calls, SMS, and numbers on the Toky cloud phone and call center system. Agents keep call activity attached to the record it belongs to.
What This Integration Enables
Toky is a call center you assemble country by country. You search its inventory by region and by city, take a local number where your customers actually are, hang an IVR on it, and route it into an agent group. That is a different proposition from a corporate PBX. It is built for teams whose customers are spread across markets and whose support and sales lines need to look local in each one, without standing up infrastructure in any of them.
FlowRunner agents work the resulting call center as a live system rather than a monthly export. Toky delivers real-time events for new calls, new voicemails and new SMS, and FlowRunner registers and removes the webhook for you. From there an agent resolves the caller against the directory, pulls the recording as a hosted URL, transcribes and summarizes it, writes the outcome to the CRM, and sends the SMS follow-up from a number that is actually SMS-enabled. Two details are worth knowing before you build. Toky's delivered webhook body carries no event-type field, so each trigger registers its own callback URL and matches on that. And the meaning of the two numbers inverts by direction, so on an inbound call the from number is the caller while on an outbound call it is yours.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Inbound call logged against the right record, automatically
On Toky Event fires with New Call. The agent takes the from number, runs Get Contact By Number against the Toky directory, and gets a name and email back. It then updates the matching record in HubSpot with the call duration, the handling agent, the disposition code and the IVR option the caller pressed. That last field is often the most useful one in the payload, because it tells you what the customer thought they were calling about before anyone spoke. Calls from numbers with no directory match are queued for enrichment rather than silently dropped.
Voicemail that reaches a person before it goes cold
On Toky Event fires with New Voicemail. Get Voicemail Recording returns the audio as a hosted URL, which means the agent can hand it directly to Speechmatics without downloading anything. The transcript is classified by urgency and posted to the owning channel in Slack with the caller's name resolved and a link to the audio. A message left at 6pm is triaged and assigned before the team opens the next morning, and the ones that are genuinely urgent are escalated rather than sitting in a queue.
Local presence, checked before it is bought
A team wants a local number in a new city. The agent walks List Regions and List Cities to see where Toky actually has coverage, then runs List Available Numbers filtered by number type and area code to confirm inventory before anyone commits. The connector deliberately does not buy the number, so the agent brings the availability, the coverage and the existing inventory from List Numbers to whoever owns the budget, and a person completes the purchase in Toky. On the way out, Remove Number handles decommissioning, and because a released number stops receiving calls and messages and may not be recoverable, the agent proposes rather than executes.
Human-in-Loop Highlight
Delete Call Recording is the operation that stops the agent, and the reason is evidence rather than cost. A recording is often the only account of what was actually said on a call that later turns into a dispute, a refund argument, or a complaint. It is also the thing a retention policy says you may not keep forever. Those two facts pull in opposite directions, and an agent should not resolve that tension on its own. So the retention flow does the work and holds the trigger: it walks List Calls for the policy window, matches each recording against open tickets and any call tagged for dispute, and posts to the compliance owner: "62 recordings from March are past the 90 day retention policy. 4 are attached to open tickets and 1 is tagged disputed, so they are excluded. Confirm permanent deletion of the remaining 57?" The owner approves the batch, or pulls individual calls out of it. Only then does the agent run Delete Call Recording. The same shape covers Delete Voicemail and Remove Number, all three of which Toky treats as one-way. This is human-in-the-loop applied where it is genuinely load-bearing: the agent handles the reconciliation, and a person owns the irreversible half.
Agent Capabilities
22 actionsAgents and Groups
3- List Agents Returns the agents on the account with email, name, admin flag, phone number, timezone, last connection time and any custom extra data. Filterable by email, group, account status or role, which makes it the basis of an access audit.
- List Agent Groups Returns the agent groups configured on the account. Groups are Toky's team unit and scope both call routing and agent filtering.
- Delete Agent Group Permanently removes an agent group. The agents in it are not deleted, but any routing that depended on the group stops applying, so flows check routing before running this automatically.
Calls and Recordings
3- List Calls Returns call detail records with both parties, the caller ID used, direction, duration, handling agent, disposition code and any IVR option pressed. Searchable by number to find every call involving it. All timestamps come back in GMT and need converting locally.
- Get Call Recording Returns a publicly accessible URL for a call's recording. Because Toky serves a hosted link rather than binary, the audio can be handed straight to a transcription or storage step.
- Delete Call Recording Permanently deletes a call's recording. Used to enforce a retention policy once the audio has been archived elsewhere. This cannot be undone, which is why it belongs behind an approval.
Voicemails
3- List Voicemails Returns voicemails left on the account, newest first. Paired with Get Voicemail Recording to fetch the audio for transcription or triage.
- Get Voicemail Recording Returns the audio for one voicemail as a hosted URL, ready to pass to a transcription or storage step.
- Delete Voicemail Permanently deletes a voicemail and its audio. Used to clear handled messages or enforce retention. This cannot be undone.
Messaging
3- Send SMS Sends a real, billable text message from one of the account's SMS-enabled numbers. The sending number must appear in List SMS Numbers, so flows resolve the sender before attempting to send.
- List SMS Returns the SMS history for the account, both sent and received. Used to reconcile a conversation or build a messaging volume view.
- List SMS Numbers Returns the account numbers enabled for SMS. Only these can be used as the sender, so this is the check that runs before Send SMS.
Contacts
2- List Contacts Returns contacts from the Toky directory. Supports Toky's filter expression syntax, so contacts can be narrowed by creation date for a nightly sync of everything added in a window.
- Get Contact By Number Looks up a directory contact by phone number. Used to resolve an unknown caller to a name and email the moment a call event arrives.
Numbers
5- List Numbers Returns the numbers provisioned on the account, optionally narrowed to one country or number type. Used to audit inventory or pick a caller ID.
- List Available Numbers Searches Toky's inventory for numbers available to buy in a country and region, narrowable by city, number type or area code. Used to check availability before a purchase decision.
- Remove Number Removes a number from the account. It stops receiving calls and messages and billing for it ends, but it may not be recoverable, so flows confirm before running this automatically.
- List Regions Returns the regions of a country where Toky has numbers, so a flow can present valid choices before searching availability.
- List Cities Returns the cities within a country and region where Toky has numbers. Used to narrow a search to a specific local presence.
IVR
2- List IVRs Returns the IVR menus configured on the account. Used to discover menu identifiers or to audit how inbound calls are being routed.
- Get IVR Returns one IVR menu by ID with its configured options. Paired with the IVR option recorded on a call to work out which path the caller took.
Webhooks
1- List Webhooks Returns the webhooks registered on the account with callback URL and subscribed event. Triggers in this service create and remove their own webhooks, so those appear here alongside any configured manually.
Triggers
1 triggersEvent Triggers
1- On Toky Event Fires when a call, voicemail or SMS event occurs in Toky, with the event selected from New Call, New Voicemail or New SMS. Call events deliver the call ID, direction, handling agent, duration, state, both numbers, recording URLs, caller and contact details, the IVR option pressed, queue and answer times, and tags. FlowRunner registers and removes the Toky webhook for you. Because Toky's delivered body carries no event-type field, each trigger registers its own callback URL and events are matched on that.
Frequently Asked Questions
What can FlowRunner do with Toky?
FlowRunner agents can run List Agents, List Agent Groups, and Delete Agent Group in Toky, plus 19 more actions.
Does connecting Toky to FlowRunner require OAuth?
No. Toky connects to FlowRunner with an API key, no OAuth flow required.
Can Toky trigger a FlowRunner workflow automatically?
Yes. Toky supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with Toky
$100 in credits. No card required. Connect in minutes.