Dash now connects to the tools your team already uses. Connect to an external service, and Dash will pull files, draft emails, and catch up on your messages, all from within GovDash.
Until now, Dash lived within GovDash. It couldn’t touch your work that lives elsewhere: a document in SharePoint, a thread in Teams, a note from your last capture call, or an email from the contracting officer. Connectors unleash Dash’s full potential to operate across your entire workflow.
Every Connector below is live in your account today:
- Microsoft 365: SharePoint, Teams, Outlook, Microsoft Word, Microsoft Calendar
- Google Workspace: Gmail, Google Calendar, Google Drive
- Slack, HubSpot, Gong, Granola, GitHub, Linear, Document360, Intercom, Airtable, Confluence, and Jira
- Custom Connectors for the tools specific to your team
What is a Connector?
A Connector lets Dash interact with an external service.
Connectors leverage Model Context Protocol (MCP), the industry standard for connecting AI to external tools and data. Think of it as a universal plug. Instead of a custom integration for each application, MCP gives Dash a simple way to connect to all of them.
Two types of Connectors
Native connectors are built-in providers like Slack, Google Drive, GitHub, Linear, HubSpot, and the Microsoft services. An admin enables a provider for the team, then each user connects their own account through that provider's sign-in.
Custom connectors are MCP endpoints your team manages, configured with a URL and headers. They are team-owned, so users do not sign in individually.
Why we built this
Government contractors need a stack of tools to deliver top-quality results. To craft a proposal, a proposal manager pulls past performance from SharePoint, pricing from a workbook, a technical approach drafted in Word, a kickoff thread in Teams, and a dozen emails with teammates and the contracting officer. They spend hours moving between systems, and up to now, AI solutions can’t access any of them.
GovDash is infrastructure that allows your team to fully leverage AI for GovCon workflows. Connectors extend that infrastructure to the tools you already use, on one verified data layer, so context compounds across every pursuit. We built one secure way to connect external systems, so we can add new tools without starting from scratch each time.
What you can do with it
Capture and BD: Dash pulls the latest past performance write-up from SharePoint into a capture summary, drafts an intro email to the contracting officer named in a solicitation, catches you up on the capture channel in Slack or Teams, and logs the outcome to HubSpot. Dash brings the context; you make the call.
Proposal: Dash pulls approved boilerplate or a prior technical volume into a new draft, summarizes a long PWS so the team can scope, and drafts a compliant reply to a clarification email for your approval before it sends. Turn a Granola recording of the color review into a clean action-item list.
Contracts and post-award: Dash drafts the MSR from your notes, searches your inbox to confirm a teaming agreement went out, and pulls the modification thread when a question comes up.
Connectors and agents
Connectors get more powerful when you enable them in an Agent. A Dash Agent with Connectors can reach across your outside tools on its own.
Here are some of our favorite Agents:
- When a proposal is created in GovDash, an Agent builds a kickoff deck and emails it to the team.
- Every Monday at 9 am, an Agent can post a pipeline summary to your Slack channel.
- After each capture call, an Agent can turn the Granola note into next steps and logs them to HubSpot.
Agents put repetitive work on autopilot. You set the goal, the trigger, the tools an Agent can use, and who has access. Nothing runs without human approval on writes, and every run is auditable.
You stay in control
Connectors are designed exclusively for unclassified environments and are never enabled in classified deployments. Dash never exceeds the permissions you already have, every action is logged for auditing, and your organization remains in complete control over connected systems. You can enable or disconnect Connectors for your team.
Getting started
Connectors are enabled once by an admin, then each person connects their own account.
To make a provider available to your team:
- Log in to GovDash.
- Go to Settings > Dash > Connectors.
- Under Native Connectors, find the provider you want to make available.
- Click Enable.
The provider is now available to everyone on your team. Each person will see it in their Connectors menu in Dash, where they connect their own account and toggle it on. For the full walkthrough, see the Dash Connectors setup guide.
With Connectors, Dash becomes the place where your work comes together, reading across your tools and running repetitive work through Agents on one compliant data layer, with your team in control. Book a demo to see what agentic infrastructure looks like for government contractors.
FAQs
How is a Connector different from an API integration?
An API integration is custom code for one system that breaks when that system changes. A Connector uses MCP, one standard interface many tools already speak, so Dash connects in a few clicks and picks the right tool in the moment. Use an API for a deep system of record like an ERP. Use Connectors for the tools your team touches all day.
Can a Connector integrate our ERP or accounting system?
Not the way a deep ERP integration would. Connectors read and act at the application level. They are not a bidirectional sync or a system-of-record integration. What a Connector can do today is work with ERP outputs once they land in a tool Dash connects to, like a cost report saved to SharePoint or a funding summary posted in Teams, and pull them into a pursuit.
What can I get done that I couldn't before?
Ask one question and get an answer that spans your files, your CRM, and your team's threads. Dash pulls a past performance write-up from SharePoint, checks the latest from the contracting officer in your inbox, and drafts the next step, without you switching tools.