TEASEDocs
ProductsClubHow-to

Connect Tribute (Private)

Bring Telegram subscription, donation, and digital-product revenue into Club by connecting your own Tribute account.

Tribute (shown in the panel as Private) is a paid-Telegram platform — subscriptions, donations, and digital products sold through the @tribute bot. Connecting it to Club is self-serve: each creator pastes their own Tribute API key, and Club mints a private webhook URL that routes only that creator's events back to their own workspace. Find it at Dashboard → Telegram → Private.

Only the workspace owner can connect or disconnect

Managing the Tribute connection is a workspace-owner action — a team member does not see the connect/disconnect controls, even with full Telegram tab access.

Connect

Generate an API key in Tribute

In your Tribute author account, go to Settings → API Keys and generate a key.

Paste it into Club

Paste the key into the Private panel's connection card and confirm. Club stores the key (it is never echoed back to you) and mints a stable webhook token for your account if one doesn't exist yet.

Paste the webhook URL into Tribute

Club gives you back a webhook URL, unique to your account. Copy it and paste it into Tribute → bot @tribute → Settings → Webhook URL. This is the wiring that makes events start flowing — the API key alone only lets Club record who owns the key, not receive events yet.

Once both halves are in place, revenue from new subscriptions, renewals, donations, and digital product sales appears on the Private panel as real events land — net revenue, an active-subscriber count, and a recent-events list.

Disconnect and reconnect

Disconnecting clears the stored API key and turns the connection off, but keeps your webhook token — if you reconnect later with a (possibly new) key, you get back the exact same webhook URL, so you never have to paste a new one into @tribute.

Why revenue can read zero after "connecting"

The REST API is not the source of truth — the webhook is

Storing your API key alone does not backfill revenue. Tribute publishes no stable schema for polling subscribers or revenue, so Club deliberately does not try — every number you see comes only from webhook events Tribute has actually delivered. If the connection card shows connected: true but revenue/subscribers stay at zero, double-check that the webhook URL was pasted correctly into @tribute → Settings → Webhook URL — nothing is missing on Club's side until an event arrives.

What's next

Set up a traffer payout

Create, edit, or deactivate a flat or percent-of-revenue payout arrangement for the contractor who supplies one traffic source.

Check the revenue forecast

See a next-30-day run-rate projection by revenue stream, plus which subscriptions are at risk or expiring soon.

On this page

ConnectGenerate an API key in TributePaste it into ClubPaste the webhook URL into TributeDisconnect and reconnectWhy revenue can read zero after "connecting"What's next