Connectors
Give d5s governed access to external systems through credentials, activation, and tool policy.
Connectors give agents governed access to external services such as source control, messaging, files, and MCP servers. Four settings control a connector: whether d5s offers it, whether the workspace connected it, whether a project removed it, and which operations may run.
Connector catalog
Matches the connector directory in d5s.
Google Drive files
Connect Google Drive with the Google account whose files the agent should use. The Drive API connection can find, read, download, and export files that account can access. If Google grants write access when you connect, agents can also create, upload, copy, move, edit, trash, restore, or permanently delete files and folders, and change file sharing. The same connection can create and edit Google Docs and Google Sheets, including spreadsheet cell values. All of this also works for files and folders in shared drives that the account can access.
Reads start on Allow. Each file, sharing, document, and spreadsheet change starts on Ask. Use tool permissions to allow the actions an agent needs or set them to Deny. Permanent file deletion has its own permission. The connection cannot empty the whole trash or administer shared-drive membership.
A sharing change or a file delete waits on a card that names the file. A sharing card shows the person, group, or domain and the role. You can change the role before you select Share or Change access. Remove access removes that permission. A delete card shows the file or folder, and for a folder, how many items it holds. A delete and a move to trash show the same card. Delete moves the item to Drive trash, where you can restore it for 30 days. The agent cannot transfer file ownership.
An older read-only connection keeps its Google permissions. If write access is available for your workspace, reconnect it when a write fails for missing Google access. Check the permissions in Google's consent screen before you finish. Reconnecting does not change a tool's Deny setting.
Google Drive has one connection method in the directory. If a workspace still has an older Google Drive MCP connection, connect the Drive API method and activate that new connection in the projects or agents that need it. The older connection does not automatically become a Drive API credential. After moving access to the new connection, an admin can disconnect the retired MCP credential from workspace connectors.
Google Search Console
Connect the Google account that can access the required Search Console property. The agent can read properties and sitemaps, query search performance, and inspect indexed URL status. Queries start on Allow, including queries that Google receives as POST requests.
If Google grants write access when you connect, the agent can add or remove properties from that account and submit or remove sitemaps. Each change starts on Ask and has its own tool permission. Adding a property does not verify ownership. This connection cannot verify domains or submit URLs for indexing. If write access is available for your workspace, reconnect an older read-only connection when a change fails for missing access.
Google Calendar events
Connect Google Calendar with the Google account whose calendars the agent should use. The Calendar API connection can list calendars and events, check availability, and create, edit, or delete events. Event changes start on Ask and can be configured separately with tool permissions. In the same work where Gmail sends wait on a card (see Gmail drafts and sending), a new event the agent creates waits on a card too: it shows the time, guests, location, repeat rule, and description. Before you approve, you can change the title, date and time, location, and description in the card. The calendar, guests, repeat rule, video link, and the dates of an all-day event stay as the agent set them. Book creates the event as the card shows it.
A change to an existing event also waits on a card. The card shows the event and each change from the old value to the new one, such as the time, title, guests, location, or description. Change applies it. d5s refuses a change that the card cannot show, such as a new repeat rule, and a change or cancel of a whole repeating series. A request to delete an event shows the event and its guests, and Cancel event cancels it. A change to reminders, color, or busy and free time alone follows the event tool permission.
The agent can add a Microsoft Teams meeting instead of a Google Meet link. The card then shows Microsoft Teams link added when you book. When you approve, d5s creates the Teams meeting with an Outlook connection of the person who connected that Google Calendar. It puts the link in the event description, and in the location when the location is empty. The meeting also appears in that Outlook calendar as free time with no reminder. Keep that Outlook entry: deleting it ends the Teams meeting.
A Teams meeting needs these conditions:
- An Outlook connection for a work or school Microsoft account, made by the same person as the Google Calendar connection and activated for the project. Personal Microsoft accounts cannot create Teams meetings.
- Permission to create Outlook calendar events. If the card asks you to reconnect Outlook, reconnect it and select Retry.
- An event with a start time and an end time, not an all-day event.
If a condition is not met, the card fails and d5s books no event.
An older Google Calendar MCP connection does not become a Calendar API connection automatically. Connect the new Calendar API method, activate it for the relevant projects or agents, and reselect it in any agent auto-join setup. Then an admin can disconnect the retired MCP credential. If Calendar access fails after connecting, confirm the intended Google account and permissions; approving an operation in d5s does not grant missing Google permissions.
Gmail drafts and sending
The Gmail API connection supports reading email, creating and updating Gmail Drafts, sending messages, and sending saved drafts. If write access is available for your workspace, use Reconnect on an older read-only connection and approve the additional Google access. Reconnecting targets that same connection; existing grants do not expand silently.
Use the standard tool permissions to configure each operation. Draft creation, draft updates, message sending, and draft sending are separate write operations, which start on Ask. You can allow draft operations while leaving both sending operations on Ask or Deny. Saved drafts may also be edited directly in Gmail.
If Google grants mailbox management access when you connect, the agent can also delete drafts, create, edit or delete labels, change labels on selected messages and threads, and move messages or threads to trash or restore them. These actions have separate permissions and start on Ask. Permanent message or thread deletion, whole-mailbox deletion, and Gmail account settings changes are unavailable. An older connection needs fresh Google consent for these additional actions. Agent mailbox connections keep their separate read and send permissions.
Each email the agent sends waits on a card that shows the exact recipients, subject, text, and attachments when the work runs in a d5s chat or in any run of a named agent: its d5s conversation, its Slack, Teams, or Telegram runs, its scheduled, manual, or event-triggered work, an email it receives, a message from another agent, and its first setup. Before you approve, you can click the subject or the text to change it. A reply keeps the subject of its thread, and the recipients and attachments stay as the agent set them. If you change the text, the email goes out as plain text. Your changes stay in that browser until you decide, and the revert button restores the agent's text. Send delivers the message as the card shows it; Reject discards it. When the agent offers up to three wordings, the card shows them as lettered options. Choose an option to see it, change it if needed, and Send delivers only that option, as plain text. Each option keeps its own changes, and the revert button restores only the option on screen. Approve in Slack or the mobile app sends option A; choose another option in d5s on the web. Copy copies the subject and text of the option on screen, also after the card is sent, rejected, or expired. The card's footer names what started the work, for example "From the 10:00 scheduled check", "From the 09:12 email", "From the 14:05 message from Max", or "From the agent setup". The card waits even when sending is allowed or the conversation uses Allow all; Deny still blocks the send. The agent continues its work and gets the result in a later turn. A card that nobody decides within 72 hours expires. A bound Slack channel shows the cards in the run's thread when the run ends; a Slack direct message, Teams, or Telegram gets a link to review them in d5s. In this work the agent cannot send a saved draft directly: it sends the draft's content as a new message, so the card can show it, and the saved draft stays in Gmail. Each email card is also saved in the Gmail Drafts of the connected account, and the waiting card links to it for the person who connected that account. In this work the agent does not save drafts of its own: when you ask for a draft, you get a card, and the card's draft is the one in Gmail. Send removes that draft and sends the text on the card, with your changes; changes made to the draft in Gmail are not sent. If the draft was already sent or deleted in Gmail, the card does not send and says so. Rejecting the card, or letting it expire, removes the draft. If d5s cannot save the draft, for example when draft deletion is set to Deny, the card works without it. Automations, dashboards, and sub-agents cannot show a card, so they cannot send email or book, change, or cancel an event from a Gmail, Outlook, or Google Calendar account, under any approval setting. The agent tells you, and puts the email or event in its answer instead; a sub-agent returns it to the chat that started it. If approval cards are off for your workspace, these sends and bookings are off too.
Google must also grant the required access. Approval in d5s cannot upgrade a read-only Google credential. Immediate permanent message or thread deletion and account settings changes are not included. After an uncertain send result, check Gmail before retrying to avoid sending the same email twice.
Connecting Gmail here does not configure an agent's incoming email channel.
IMAP / SMTP mailbox folders
Ask the agent to list the folders in your connected mailbox before a broad email search. It can search Inbox, Sent, archives and custom folders by their actual names. Folder names can differ by mail provider and language.
Each search covers one folder. Ask for the searched folders, date range and any gaps in the result. No matches in Inbox does not mean no matching mail exists elsewhere. An incomplete folder list or search must be reported as incomplete.
Folder discovery, searches and message reads do not move messages or mark them as read. An explicit folder choice applies to that read; it does not change the connection's default folder or the folder used by scheduled mailbox checks. Sending remains a separate operation with its existing approval requirements.
Outlook mail and calendar
Connect Outlook with the Microsoft account whose mail and calendar the agent should use. The agent can read mail, folders, contacts, calendars, and events, send new email, reply or reply to everyone, and create events, with or without a Microsoft Teams meeting. It cannot forward, delete, or move mail, or read another person's mailbox. Reading starts on Allow and changes start on Ask.
New email, replies, new events, and event changes and cancellations wait on a card, the same as Gmail and Google Calendar, in the same work. An email card shows the recipients, subject, text, and attachments; a reply to everyone says Reply all in the thread. An event card shows the time, guests, location, repeat rule, and description, and Outlook emails the guests when you book. Before you approve, you can change the same fields as on the Gmail and Google Calendar cards. In this work the agent cannot send a saved Outlook draft directly: it sends the draft's content as a new message. Each email card is also saved in the Outlook Drafts of the connected account and works as the Gmail draft does, so the agent does not save drafts of its own; a removed draft moves to Deleted Items.
For a Teams meeting, the event card shows Microsoft Teams link added when you book. Teams meetings need a work or school Microsoft account and an event with a start and an end time. If the account cannot create Teams meetings, the card fails and d5s books no event. If Outlook books the event without a Teams link, the card fails and links the event in Outlook, because the guests already have the invitation. Neither failure offers Retry.
An Outlook connection made before sending was available can only read. If a card asks you to reconnect Outlook, select Reconnect on the connection, approve the additional Microsoft access, and ask the agent again. After an uncertain result, check Outlook before you ask again.
Jira issues and attachments
Connect Jira Cloud with Atlassian sign-in to read projects, releases, issues, users, field metadata, links, and attachments. Agents can search issues with filters or JQL, add comments, perform available status transitions, create or update issues, change issue links, and upload files within the connected account's Jira permissions.
Choose the connected account and intended site. A sole accessible site is used automatically for issue work; multiple accessible sites require an explicit choice. Reading starts on Allow and changes start on Ask. Each action has its own tool permission. A d5s approval cannot grant missing Jira access.
Uploads use a file available in the current conversation or supplied file bytes, up to 50 MiB per file. Attachment reads have the same limit. The agent can inspect supported files through the saved result without repeating a Jira change. A timeout after a change requires checking Jira before retrying. Follow Connect Jira Cloud for setup, site selection, and attachment handling.
HubSpot CRM access
Connect one HubSpot account for CRM records, activities, owners, properties, schemas, and associations. The agent can inspect a curated set of actions on that connection, including search, record reads and writes, archive, company merge, and association changes when the connected account grants the required scope. Lead association removal is intentionally unavailable because removing a lead's final primary association can delete the lead in HubSpot.
The former HubSpot MCP connection is not converted to this OAuth connection. Disconnect it and connect HubSpot again to use these actions. Reattach the new connection to any project or agent that used the old one.
CRM reads start with the normal read-oriented policy. Every write starts on Ask, including create, update, archive, company merge, property changes, and association changes. Archive moves a supported CRM record to HubSpot's recycle bin; company merge keeps the named primary company and folds the other company into it. Before approving either action, verify the HubSpot account, object type, record IDs, and primary record. After a write, have the agent read the affected records again before retrying or continuing a cleanup.
The HubSpot connection deliberately excludes permanent purge (including email engagement deletion), custom-object deletion, restore, property deletion, schema mutation, imports, workflows, administration, and marketing sends. An approval can permit a listed operation, but it cannot enable lead association removal or add a missing HubSpot product entitlement or OAuth scope.
X and LinkedIn publishing
X and LinkedIn Pages are in beta. Connect them from Connectors when they appear in your workspace. X uses the account that completes OAuth. For LinkedIn, open the installed connection and select one or more company Pages administered by that LinkedIn member. Activate the connection for each project or agent that should be able to draft for those destinations.
Agents cannot publish through the connector directly. They create an exact draft for one or both destinations, and the originating conversation shows an X- or LinkedIn-style preview. A signed-in human with access to that work must approve the current revision before d5s contacts either provider. The approval binds the displayed destinations, copy, and optional image bytes; editing the copy creates a new revision and clears the prior decision. Session Allow all and connector tool policy do not bypass this social-post approval.
Each destination reports its own outcome. Successful posts link to the provider when a permalink is available. A definite failure can be retried explicitly, up to the attempt limit. An Uncertain result means the provider may already have accepted the post; d5s does not retry it automatically, so check the external account before creating another post.
Disconnecting or removing the connector from a project blocks new approvals and retries. A workspace admin can reconnect or remove the account from its connection settings.
Meeting intelligence
Meeting-intelligence connectors let agents find meeting records and work with provider-authorized transcripts, summaries, notes, highlights, and action items. Use the generated directory and provider pages to compare the currently available services, supported connection methods, and any provider plan requirements.
Meeting content follows the same credential, project activation, and per-tool approval boundaries as other MCP connectors. Keep write-capable meeting actions in Ask for approval mode until their targets and effects are clear.
GTM workflows
Use the connector directory to find connectors for prospecting, sales operations, analytics, billing and revenue work. A provider page lists every currently supported connection method without requiring you to know whether it uses remote MCP or an API credential.
Start credit-consuming outreach, billing changes, refunds, and other external writes in Ask for approval mode. Review the exact account, target, and arguments before approving; the external provider's permissions and usage limits still apply.
Connect and activate
Workspace owners and admins select a provider from the connector directory to review its detail page, then choose Connect. Depending on the provider, setup uses OAuth, a token, or an MCP connection. Saved secrets are not shown again in connection details.
Each provider detail page shows three example requests. Before connection, these are previews. On a connected account, choose an example to open the workspace-agent picker. It lists agents that can use a connected method for that provider; add the connection to an existing agent's project if the agent is missing. Select an agent, or choose Add an agent → Quick create; d5s opens Chat with that agent selected and the example as an editable draft. Nothing runs until you press Send. The provider may still restrict the requested operation.
For Slack, Connect Slack is also available on an agent’s Slack channel page under Manage agent → Channels → Slack. Approve access once for the workspace; the same connection supports agents selected inside Slack threads. A workspace admin can choose Reconnect Slack beside an existing connection to refresh its permissions for visible agent names and characters; reconnect targets that exact credential and keeps the existing connection. The installing user’s verified Slack account is linked during OAuth, so that user does not need a second account-link step. Other teammates may be asked privately to connect their d5s account before choosing an agent. Existing identity links are never reassigned to a different account by reconnecting Slack. See Agents for the thread picker and optional dedicated identities.
A workspace can keep more than one connection for the same provider—for example, separate Notion workspaces or customer and internal accounts. Choose Add another in the connector directory, or Add account in an installed account's settings dialog. Give each connection a recognizable name. d5s keeps activation, approvals, usage, rotation, and removal scoped to the selected connection rather than guessing between credentials.
A workspace connection is available by default to ordinary chats, automations, dashboards, and agents made through advanced creation. Agents made through conversation use only the connections reviewed in their draft and do not inherit future workspace connections. Turn off a connection that a project or agent should not use in its connector settings. Disconnecting a workspace account removes it from active use.
The Connectors page shows connected providers in the Installed section. Select a provider to see its Connections list first: each credential's method, who set it up, when, its status, and its approval choice. Workspace owners and admins can choose Manage permissions next to Add another connection, select a connection's approval choice, or use the controls on a connection to reconnect or archive it. With several connections, Manage permissions asks which one to open. The settings dialog has a shareable URL. In an agent's Manage → Connectors tab, each connection shows its approval choice as a link to the same dialog. The setting applies to every agent that uses the connection.
For Gmail attachment limits, see Gmail attachments.
A Gmail account chosen under Manage channels → Email serves that agent's mailbox and its incoming and outgoing rules. It is not automatically available as a general project connector. Connect the account separately if the project needs other Gmail actions.
Use a connected account
Ask the agent to use the service and identify the intended account when the workspace has several. The agent can find the operations available for that account. An unavailable account does not cause a silent switch to another connection. Finding an operation does not connect another account or grant additional access.
Returned images, audio, and large results can be saved as files for further work. Supported MCP PDF download actions, including Moneybird invoice PDFs, can import a returned file link during the same connector call. Microsoft 365 can download supported work or school SharePoint and OneDrive files through the connected account. Other links remain references; a read-only download may require separate access to the file host and a fresh link after approval. See using connector results.
Connection is not permission
A workspace credential makes an integration available throughout the workspace unless a project removes it. Tool policy then determines whether an individual operation is:
- Allow — the agent may run it without pausing;
- Ask first — the agent must surface an approval card before the call;
- Block — the operation is blocked.
In an installed account's Tool permissions section, under Approval, choose Always ask, Allow reading (the default), or Allow all. Allow all requires confirmation because known write operations can run without another prompt; unclassified operations still ask. Tools are grouped as Reading information, Making changes, and Unclassified. Hover a tool to see its API name. Use the menu on a tool to choose Allow, Ask first, Block, or Use default. Tool settings override the Approval choice, and Reset on a group clears its custom settings. Choosing another Approval option replaces custom settings after confirmation. Search appears when an account has more than ten tools.
A tool that sends email or books or cancels a meeting (Gmail, Outlook, and Google Calendar) offers only Card or Block. Card means each request waits on a card, under every Approval choice; the help line under Approval says so. A meeting change keeps the usual choices: a change that notifies guests still waits on a card, and a quiet change, such as a reminder or a colour, follows the setting. Sending a saved draft shows Block only.
On MCP connectors, tools that send email or book meetings are off and show Block only; the agent uses Gmail, Outlook, or Google Calendar instead, so you approve each request in a card. AgentMail and an agent's own email address keep their own rules.
Some connectors can email people outside your workspace: AgentMail, Gmail MCP, Superhuman Mail, Zapier, Make, IFTTT, outreach and CRM tools such as Apollo, Close, Outreach, Klaviyo, and MailerLite, e-signature tools such as DocuSign and PandaDoc, Pylon, and any custom MCP server. Their write and unclassified tools ask on every call. Allow once is the only approval that covers such a call. Allow, Allow all, Always allow, and Allow for this run do not cover it, and Block still blocks it. In Tool permissions, these tools show Every call and offer only Every call or Block, and the help line under Approval says so. Approval cards for these tools offer only Decline (or Deny) and Allow once, with a line that says why.
Custom API connections ask on every POST, PATCH, PUT, or DELETE in the same way. GET and HEAD calls run without a card. A Custom API connection that uses an API token shows Write requests instead of Approval: Ask every time is the default. An admin can choose Allow for a run after a confirmation; write requests then ask once, and Allow for this run and Allow all can cover them.
For MCP connectors, review available tools in Tool permissions; the Refresh tools control finds new ones. Known reads normally allow, while writes and unclassified actions normally ask. An action not yet reviewed also asks unless you set an explicit policy. API operation controls appear only for connections that support them.
Each conversation starts in Ask for approval mode. The approval card in d5s shows the connector's logo and asks whether the agent may access that app. It offers Decline, Always allow, and Allow once; a tool that asks on every call offers only Decline and Allow once. Allow once covers one matching action and expires after 15 minutes. It does not change the connected account's long-term policy. Always allow approves the current call once, then sets that action to Allow in the connected account's Tool permissions, for every chat in the workspace. Only workspace admins can choose Always allow. To undo it, change the action in Tool permissions. If d5s cannot save the setting, the current call is still approved once.
Allow all lets actions configured to Ask continue in that session without individual cards. Gmail, Outlook, and IMAP / SMTP sends and new, changed, and cancelled Google Calendar and Outlook events still wait on a card (see Gmail drafts and sending and Outlook mail and calendar). Switching back to Ask applies to later actions. Explicit denials, account permissions, and workspace restrictions still apply.
Approving from a bound channel
When a run started from a bound Slack channel pauses on an Ask operation, the agent posts an approval card in that thread offering Deny, Allow for this run, and Allow once (only Deny and Allow once for a tool that asks on every call). Any member of that channel can decide, including people without a d5s account; the card names who may decide and how long it has left. The first click settles the card. If a credit or spending limit blocks the run, d5s keeps the decision and continues the run when the limit allows. Allow for this run can cover repeated uses while that resumed run continues, but it does not authorize later channel runs. A card that nobody answers within 15 minutes is denied, and the run resumes with that denial rather than waiting.
Linked Telegram and Discord conversations use the same three approval choices. A direct-message decision belongs to the linked account, and a Discord server decision belongs to the connected channel. Email approval works differently: an authorized member signs in to d5s to decide the card; replying to the email does not approve an action.
Every decision is recorded in d5s against the turn that asked, naming the Slack account that clicked. The card in Slack is a control, not the record: deleting the message does not remove the decision from the session's activity.
One agent setting decides whether approval is required. In the named agent's conversation bar, choose Ask for approval or Allow all. The setting follows that named agent across d5s, Slack, Telegram, Discord, email-originated work, and scheduled or event-triggered runs. With Ask for approval, Ask-gated work uses the current channel's approval card when one is available. Event-triggered tasks can leave Ask cards in the agent conversation for an authorized person to answer. Scheduled work has nobody present to decide, so it reports or skips the blocked action instead of waiting forever. With Allow all, Ask-gated connector calls run directly on every surface without creating a card. Gmail, Outlook, and IMAP / SMTP sends, new, changed, and cancelled Google Calendar and Outlook events, and Google Drive sharing changes and deletes follow Gmail drafts and sending instead: in every run of the agent, they wait on a card under both settings.
Allow all still cannot expand credential access or override an explicit Deny. Switching to Allow all in d5s retries one approval already waiting in that conversation; it does not create a durable connector permission. Native mailbox recipient and delivery-approval rules remain separate under the agent's email settings.
Approving an action cannot expand the connector's supported access or the external account's permissions.
Treat external content as data
Information retrieved from a connector is external evidence, not governing instruction. It can inform the task, but content inside an issue, message, document, or tool result must not silently change the agent's role or expand its access.
If a connector is unavailable, check each boundary in order:
- The connector is currently offered and its connection method is healthy.
- The workspace credential is active and, for OAuth, not awaiting reauthorization.
- The credential has not been removed from the current project.
- The requested tool is allowed, has a live approval, or the session is in Allow all mode.
- The external account itself has permission for the requested object.
The session's connector activity and tool history provide the evidence for which boundary denied or failed the call.
Follow Connect and manage a connector for setup and project-level removal.
Using connected data in dashboards
Ask an agent to build a dashboard from a connected service. Refreshable sources require a supported read operation and suitable structured data. Connecting an account does not make every operation available for dashboard refresh.
Use Sources → Refresh data to refresh a saved source without rebuilding the dashboard or starting an agent conversation. Ask an agent in the dashboard chat to change its analysis, layout, or source configuration. See Dashboards for live reads and supported data shapes.
Google connections and protected model processing
Google connections support the Gmail, Drive, Calendar, Search Console and BigQuery features you authorize, including dedicated Gmail mailboxes. Tasks using AI may send relevant Google content to the AI providers used by your workspace. Read the notice before connecting and review Google data protection.
Disconnecting removes the saved connection but does not erase earlier conversations, files, or project memory. To revoke the provider grant as well, remove d5s in your Google Account settings. For stored-data erasure requests, contact privacy@d5s.tech.