How to connect your tools to Eodly: a beginner's guide

Eodly reads two things: where your team talks (Slack, Telegram, or Discord) and where the work actually happens (GitHub, Linear). You connect those once, your team checks in with a single message a day, and every evening Eodly writes you one sourced report on what shipped, who is quiet, and what is slipping. This guide walks through connecting each tool from scratch. You only need the ones your team actually uses.

A few things to know before you start:

You connect tools once, as the founder or manager. Your team never logs into Eodly, never creates an account, and never sees a dashboard. Their entire experience is one friendly message a day.
Connect at least one check-in channel (Slack, Telegram, or Discord). That is how your team reports.
Connect GitHub and Linear if your team ships code or tracks issues there. That is how Eodly checks claims against real work.
Everything below lives on your dashboard, in the row of "Connect ..." buttons.

Step 1: connect a check-in channel

Pick the app your team already lives in. You can connect more than one.

Slack

On your dashboard, click Connect Slack.
Choose your workspace and click Allow.
Done. Eodly adds a bot your team can message. When someone tells the bot what they did ("shipped the onboarding flow"), it is captured and attributed automatically.

On your dashboard, click Connect Telegram.
Once connected, click invite next to the Telegram pill to get your team's link.
Share that link with your team. Each person taps it, which opens a private chat with the Eodly bot, and from then on they just DM the bot their daily update.

Discord

On your dashboard, click Connect Discord.
Discord asks how to add the app. Choose Add to Server, not "Add to My Apps." This is the single most common mistake: "Add to My Apps" installs Eodly onto your personal account and nothing will work.
Pick the server your team uses and click Authorize.
Your team checks in by typing /checkin in any channel and filling in the update box. Eodly replies privately to confirm.

One note on the Discord bot: it is intentionally offline. It shows greyed out in your member list and never posts messages, and that is normal. The /checkin command is what matters, and it works whether the bot looks online or not. If /checkin does not appear when you type "/", press Ctrl+R to refresh Discord.

Microsoft Teams

Teams installs a little differently from the others: you add the Eodly app once, then link your workspace with a code.

On your dashboard, click Connect Teams.
Download the Eodly app from the panel, then in Teams go to Apps → Manage your apps → Upload an app → Upload a custom app, and pick the file.
Open the Eodly chat the app creates and send it the connect code shown on your dashboard (it looks like connect AB12...). That links your workspace to Eodly.
From then on, your team DMs the bot their daily update, exactly like Slack or Telegram.

Two things to know up front. Teams needs a work or school account: a personal Microsoft Teams account cannot install custom apps. And if "Upload a custom app" is greyed out, an admin has to allow it once in the Teams admin center (Teams apps → Setup policies → Upload custom apps → On).

Step 2: connect your work sources

This is what lets the report say "claimed done, but no PRs moved in three days" instead of just trusting the self-report. Skip any you do not use.

GitHub

On your dashboard, click Connect GitHub.
Install the Eodly app and choose the repositories you want it to read.
Eodly pulls the last 10 days of commits, pull requests, and issues on connect, so your very first report already has real work in it.

Eodly only reads the repositories you grant it. If a teammate commits in a repo you did not select, that work never reaches Eodly and they will look quiet even while they are shipping. Grant every repo your team actively works in, and when you spin up a new one later, open Connect GitHub again (or the Eodly app's settings on GitHub) and add it.

Linear

On your dashboard, click Connect Linear.
Authorize your workspace.
As with GitHub, Eodly backfills the last 10 days of issues, so day one is not empty.

Step 3: map your team

Eodly matches chat check-ins to people automatically. For GitHub and Linear, open the Team page and set each person's username (their GitHub handle, their Linear user) so their commits and issues attribute to the right name in the report. You only do this once.

Step 4: get your first report

You do not have to wait until the evening.

On your dashboard, click Generate now.
Eodly builds a report from whatever it has so far: your backfilled GitHub and Linear history, plus any check-ins.
To set when the daily report fires automatically, set your report time in settings. The default is 7 PM in your team's timezone.

That is the whole setup. Connect a channel, connect your sources, generate once to see it, and from then on it runs itself every evening.

Common questions

My team does not see anything in Eodly. Correct, and intended. They never log in. Their only touchpoint is the bot: a Slack or Telegram DM, or /checkin in Discord.

The Discord bot looks offline. By design. Use /checkin; it works regardless of whether the bot shows as online.

I connected Discord but /checkin is missing. You probably chose "Add to My Apps" instead of "Add to Server." Reconnect, pick Add to Server, choose your server, then refresh Discord with Ctrl+R.

Can I disconnect a tool? Yes. Each connected tool on the dashboard has a disconnect option. Your history is preserved, and reconnecting later picks up where you left off.

A teammate's GitHub work is not showing up. Two things to check. First, make sure the Eodly app has access to the repository they are committing to: Eodly only reads the repos you granted, so open Connect GitHub (or the app's settings on GitHub) and add any that are missing. Second, on the Team page make sure their GitHub handle is set and unique to them. A GitHub handle can only credit one person, so if two members share one, only the first gets the activity and the other shows silent.