Skip to content
Novo O Dailybot 3 chegou. Leia o lançamento
Explicação Admin team-manager

Native integrations overview

Native integrations overview

Dailybot connects to work tools your team already uses so check-ins, automations, and reports can reference real activity (pull requests, issues, calendar events, and more). Integrations are managed by Org Admins (and sometimes Team Managers) from the web app under Integrations or from within Automations when you add an action that requires an external system.

What integrations are for

  • Richer context in standups and summaries (for example open PRs or blocked issues).
  • Automation triggers and actions that react to events in GitHub, Jira, Linear, ClickUp, Bitbucket, Trello, Shortcut, or Google Calendar.
  • Fewer manual copy-paste steps between chat and your delivery tools.

Integrations are not a replacement for your chat platform connection (Slack, Discord, Microsoft Teams, or Google Chat). You need both: chat for day-to-day bot interaction, integrations for external systems.

How to connect (general flow)

  1. Sign in as an Org Admin on the Dailybot web app.
  2. Open Integrations (or start an automation that prompts for a connection).
  3. Choose the system (GitHub, Jira, Linear, etc.).
  4. Complete the OAuth or API token flow shown on screen.
  5. Select repositories, projects, or workspaces when asked.
  6. Save and run a test automation or check-in feature that uses the integration.

Exact screens differ per provider; use the dedicated article for each tool below.

Dedicated setup guides

Other native connectors (ClickUp, Bitbucket, Trello, Shortcut, Google Calendar) follow the same pattern in the Integrations area. If you do not see a tile, your plan or feature flags may limit that connector — contact support with your organization name.

Troubleshooting

  • Re-authorize if tokens expired (common after password resets or org SSO changes).
  • Confirm the Dailybot app has access to the repository or project you expect.
  • For automations, open the automation run history and read the error message before changing triggers.

Want to go deeper? See the Dailybot Academy for workflow design patterns.