Setup Guides

Written setup guides for getting stream-ready.

Use these step-by-step guides in place of recordings. They are faster to scan, easier to update, and work well on mobile while keeping the same Quick Start flow.

Setup progress

0 of 45 steps complete

Twitch

Twitch setup

Connect Twitch so Tink Bot can read activity and power alerts.0/5 complete

Purpose

Use Twitch setup when the creator streams on Twitch and wants chat, follows, subs, raids, or channel activity to reach Tink Bot.

Steps

Open Connections from the dashboard.
Choose Twitch and sign in with the streamer account.
Accept the requested permissions without changing Twitch OAuth scopes.
Return to Tink Bot and confirm the Twitch card shows connected or healthy.
Send a test alert or wait for a real Twitch event to confirm activity appears.

Expected Result

The Twitch connection appears in the platform card, reconnect only appears for confirmed saved-token or scope failures, and Twitch events can reach alerts/activity.

Troubleshooting

If Twitch shows a temporary connection issue, use Check again first. Reconnect only when the saved token is expired, revoked, missing scopes, or Twitch returns 401/403 for the saved token.

YouTube

YouTube setup

Connect YouTube live chat and event signals.0/5 complete

Purpose

Use YouTube setup when the creator streams or premieres on YouTube and wants live chat or channel activity in Tink Bot.

Steps

Open Connections.
Choose YouTube and sign in with the channel owner account.
Approve the requested YouTube access.
Confirm the YouTube card returns to Tink Bot with connected status.
Start or schedule a live event and check that recent activity is detected.

Expected Result

YouTube appears connected, live chat checks can run, and missing recent activity is treated as no recent signal instead of a broken connection.

Troubleshooting

If there is no live stream, wait until a stream exists before expecting chat activity. If the API is unavailable, check again instead of reconnecting immediately.

Kick

Kick setup

Connect Kick where available and verify event health.0/5 complete

Purpose

Use Kick setup for creators who want Tink Bot to monitor Kick activity and alerts through the supported adapter path.

Steps

Open the platform connections area.
Select Kick.
Complete the available connection or setup instructions shown by Tink Bot.
Check the Kick health card after setup finishes.
Run a test or wait for a Kick event and review activity.

Expected Result

Kick appears in platform health with a clear connected, unavailable, or setup-needed status.

Troubleshooting

If Kick health is unavailable, treat it as a platform/API availability issue unless Tink Bot specifically reports an account authorization problem.

Rumble

Rumble setup

Prepare Rumble monitoring where the adapter is enabled.0/5 complete

Purpose

Use Rumble setup when the creator needs Rumble activity checked alongside their other stream platforms.

Steps

Open Connections from the dashboard.
Choose Rumble if it is available for the workspace.
Follow the setup fields or adapter instructions shown on the card.
Save the platform setup.
Check platform health and recent activity after a stream signal exists.

Expected Result

Rumble setup is saved, platform health explains whether the adapter can check upstream status, and lack of recent activity stays calm.

Troubleshooting

If the adapter reports missing configuration, review the setup fields or admin environment configuration. Do not treat no recent signal as a hard failure.

Discord

Discord setup

Connect Discord community tools and clip delivery.0/5 complete

Purpose

Use Discord setup when the creator wants moderation, community personality, clips, or notifications in a Discord server.

Steps

Open the Discord or community setup area from the dashboard.
Invite or authorize the Tink Bot Discord bot where prompted.
Choose the server and channels for clips or community updates.
Save the Discord settings.
Send a safe test message or clip test if available.

Expected Result

Discord settings save, selected channels stay visible, and any missing bot permissions are reported clearly.

Troubleshooting

If messages fail, check that the bot is in the server and has permission to view and send messages in the selected channel.

Alerts

Alert Studio setup

Pick an alert look, upload custom media if available, preview it, and save it.0/8 complete

Purpose

Use Alert Studio setup to make alerts match the creator brand, including saved custom images, GIFs, videos, or sounds when the workspace tier allows uploads.

Steps

Open Alert Studio.
Choose a preset pack or allowed alert style.
If using custom media, open Media Uploads and choose the alert type: follow, sub, raid, or tip.
Choose the image, GIF, video, or sound file, then press the matching Upload asset button.
Wait for the upload status to say the asset uploaded and saved. Large files may take longer.
Select My custom uploaded files and press Save Upload Settings so saved uploads control the alert.
Refresh Saved Uploads or reload Alert Studio and confirm the uploaded file still appears in the saved media list or preview.
Run Test Alert or Test Uploaded Alert before going live.

Expected Result

The selected preset or custom upload saves, the uploaded file remains visible after refresh, and the preview/test alert uses the same saved alert art and sound that overlays use.

Troubleshooting

If a custom upload option is locked, confirm the workspace tier or billing status instead of changing billing gates. If an upload fails, try a smaller supported file, check the daily upload/storage limit message, and do not go live until Refresh Saved Uploads still shows the asset after saving.

OBS

OBS overlay setup

Add the private overlay URL to OBS and test it.0/5 complete

Purpose

Use OBS overlay setup to get alerts visible on stream with the private browser source URL.

Steps

Open Quick Start.
Copy the private OBS alert overlay URL.
In OBS, add a Browser Source to the stream scene.
Paste the URL, set the size, and keep the source visible.
Press Test Alert and confirm animation and sound.

Expected Result

OBS displays the alert overlay and the test alert appears without exposing private workspace data beyond the intended overlay token.

Troubleshooting

If nothing appears, check the URL, source visibility, OBS browser cache, and audio monitoring. Copy the URL again if it was pasted incorrectly.

Engagement

Engagement Studio setup

Prepare interactive stream moments and viewer prompts.0/5 complete

Purpose

Use Engagement Studio setup when the creator wants stream prompts, moments, or community interactions ready before the first stream.

Steps

Open the dashboard section for engagement or stream activity tools.
Choose the engagement feature the creator wants to test first.
Review the viewer-facing text for clear, friendly wording.
Save the engagement settings.
Run a test interaction or review the activity panel after a signal arrives.

Expected Result

The creator has one engagement flow configured and knows where to check activity or moderation results.

Troubleshooting

If there is no activity yet, confirm the platform connection and wait for a real signal. No recent signal should not be treated as a broken setup.

Launch

First stream checklist

Final pre-stream check before going live.0/5 complete

Purpose

Use the first stream checklist to make sure the creator can go live with alerts, platforms, and support paths ready.

Steps

Confirm at least one stream platform is connected or intentionally skipped.
Confirm Alert Studio settings are saved.
Confirm OBS shows a successful Test Alert.
Confirm moderation or Discord settings are ready if the creator will use them.
Know where to report a bug or feedback from Support.

Expected Result

The creator can start the first stream with working alerts, clear support steps, and no dependence on a recorded walkthrough.

Troubleshooting

If a check fails, fix the earliest failed setup item first: platform connection, alert save, OBS URL, then test alert.