Why connected apps matter
Connected apps let VDF AI work with the tools where your team already stores work, knowledge, files, and meeting context.
This makes it easier to:
- answer questions using your real company information
- create or update work in connected systems
- reduce manual copy/paste between tools
- keep prompts shorter because the relevant context is already available
The apps covered in this guide
| App | Best for | How it connects |
|---|---|---|
| Drive files, calendars, and Gmail drafting | Google sign-in, covering Drive, Calendar, and Gmail | |
| Microsoft | OneDrive, Microsoft 365, Outlook, Planner, SharePoint, Azure DevOps, and Dynamics 365 | Microsoft sign-in, covering all seven apps |
| Jira | Backlog work, issue creation, and delivery metrics | Sign-in, or a form with your site details |
| Confluence | Company knowledge and internal documentation | Sign-in, or a form with your site details |
| Trello | Board-based planning, cards, lists, and labels | Sign-in |
| Asana | Tasks, projects, assignees, and due dates | Sign-in |
| GitHub | Repository context, pull requests, and code-related summaries | Form with a personal access token |
| Bitbucket | Bitbucket Cloud repositories and pull requests | Sign-in |
| Team Foundation Server | On-premises TFS or Azure DevOps Server work items | Form with a server URL and personal access token |
| Slack | Channel conversation history and collaboration context | Form with a bot token |
| Notion | Pages and databases you choose to share | Sign-in, then page-by-page selection |
| GitBook | Product docs and searchable knowledge bases | Form with a personal access token |
| Fireflies.ai | Meeting transcripts, summaries, and action items | Form with an API key |
Apps your administrator registers first
Trello, Asana, Notion, and Bitbucket need credentials registered at the platform level before the Connect button can start their sign-in flow. If a card reports that the integration is not configured on the server, that registration is what is missing — ask your administrator rather than retrying.
Google Workspace and Microsoft 365 tenants may separately require an administrator to consent on the organisation’s behalf.
Before you connect an app
- Use the account that already has the files, boards, spaces, or channels you need.
- Only approve the access your team actually plans to use.
- If your company restricts third-party access, ask your workspace owner or IT team to confirm approval first.
Good habits after connecting
- Test one small workflow right away so you know the connection is working.
- Reconnect the app if you change passwords, revoke access, or switch accounts.
- Disconnect apps you no longer need so the workspace stays clean.
If the system you need is not here
Two paths, depending on the shape of the need: attach exports from it manually in Chat, or build the access into an agent’s tool set as a custom connector so it runs under the same permission model and audit trail as everything else.