What you will be able to doYou know which integration path exists, what must be paired and what remains outside iTok’s current scope.
Before you start
- A supported paired local companion and access to the receiving app or device.
- A specific action to verify, such as changing an OBS scene.
Use the supported target types
iTok has action types for supported OBS scene changes, OBS source visibility and configured light or webhook targets through the local companion. The receiving application, target credentials and pairing must be set up on that computer.
This is not a promise that any arbitrary webhook, keyboard command or game plugin can run. iTok does not currently expose a public general-purpose local Event API equivalent to TikFinity’s, or its broader Minecraft, GTA and Voicemod ecosystem.
Connect one external action
- Prepare and verify the receiving app or device using its supported setup.
- Pair the local companion and configure the allowed target. Keep credentials in its configuration, not in an alert’s public text.
- Create the event rule and select that configured target.
- Check the companion’s status and the action’s conditions. Live event processing has its own connection, active-window and pause requirements.
- Run a deliberate test when appropriate and confirm the result in the receiving app. An accepted or queued command is not proof of execution.
Posting into TikTok chat has a separate dependency
iTok can process supported commands and show overlay replies. Posting as a TikTok account currently uses the optional Streamer.bot plus TikFinity bridge on the computer. The account signed into that posting path is the sender; basic profile sign-in is not a chat-posting permission.
Confirm the first visible message and intended sender in the actual chat before depending on it. Do not remove a working TikFinity bridge because a local overlay reply appeared.
Do not replay a backlog blindly
A stale event should not change a scene or device long after the moment has passed. Check the connection and current action state before retrying. Never treat repeated manual tests as a harmless way to clear an external queue.
If your show depends on an unsupported integration, keep that requirement in the migration checklist. A missing integration is a reason to retain the existing tool, not to claim parity from a similarly named button.