Connect your tools to Hark

Connect a Telegram group to one workshop. Mentions become sparks, /v adds a note to a project, and the updates you choose post back into the group.

Connect the group

1. Open your Hark profile and link your own Telegram account (a 6-character code, sent to the bot in a private chat). Do this first — the bot checks your Hark role.
2. Add the Hark bot to the group chat.
3. In the group, send /link <workshop-handle>. Your Hark account needs to be an owner or admin of that workshop. The handle is shown in workshop settings.
4. The bot confirms in the group. One group maps to one workshop; a workshop can have several groups.
5. Send /unlink in the group to disconnect it, or use Disconnect in workshop settings → Notifications.

Capture from the chat

• @mention the bot with an idea — it becomes a spark in the linked workshop.
• /spark <idea> — the same thing, without the mention.
• Reply to one of the bot's messages — the reply is captured too.
• /v V-012 <note> — adds a note to that project's journal.
• The bot replies in-thread with a link to what it saved. Everything else in the chat is ignored.

Who gets credit

If the person who wrote the message has linked their own Telegram account to Hark and belongs to the workshop, the capture is theirs. Otherwise it's filed under the admin who connected the group, with "captured from Telegram (First name)" in the note. Phone numbers and Telegram usernames are never stored.

Post updates into the group

In workshop settings → Notifications, each connected group has its own event picker — stage moves, ship entries, accepted decisions, proposals awaiting review (with a Review link) and weekly review reminders. Same choices as Slack.

Privacy mode stays on for the bot, so it only ever sees commands, mentions of itself and replies to its own messages. A bot in a group that isn't connected replies once with the /link instruction, then stays silent. Captures are rate-limited per group.

Verify it works

Ask your client: "List my Hark workspaces." Expected: your workspace names.

Then: "Create a project called Connection test in <workspace>." Expected: a new V-### appears in the app and the activity log shows the source ("via Claude Code", "via Codex", etc.). Delete the test venture afterward.

Troubleshooting

• "Unauthorized request origin" — the client origin isn't allowlisted; retry from the latest app version, or email hello@harkstudio.io.
• Consent screen loops / stale token — remove the connector in the client, sign out of Hark, sign back in, re-add the connector.
• Tools list is empty — the connector isn't enabled for this chat (Claude and ChatGPT require enabling it per conversation).
• Plan cap error — you've hit the monthly agent-call cap for this workspace; see billing.
• Old endpoint — anything pointing at a lovable.app URL must be updated to harkstudio.io/mcp.