How to Email Your Deck Assistant From ChatGPT

ChatGPT does not require a feature named “Skills” to create a repeatable Deck handoff. A Project can hold the instructions and source context for an ongoing workflow. A custom GPT can package the same behavior for repeated use. With Gmail or Outlook connected on an eligible plan, ChatGPT can create the email draft and let you send it from the conversation.

There is no native Deck app for ChatGPT today. The immediately usable workflow relies on project or GPT instructions plus a connected email app. A deeper company integration would require a Deck API and an app or Action built for it.

Choose the reusable surface

Use a Project for ongoing team or client work

Projects keep related chats, files, and project-specific instructions together. They work well when the handoff depends on a living body of context such as a client account, quarterly plan, research project, or board cycle.

OpenAI currently makes Projects available across free and paid ChatGPT plans. Shared Projects are available for collaboration, with workspace-specific sharing controls.

Source: Projects in ChatGPT.

Use a custom GPT for a packaged handoff

A custom GPT can combine instructions, knowledge, conversation starters, and selected capabilities. It works well when many people need the same “send to Deck” procedure across different projects.

Creating or editing a GPT requires a paid subscription, and managed-workspace settings may control who can build or use one. A GPT can use either Apps or Actions at a given time, according to OpenAI's current documentation.

Source: GPTs in ChatGPT.

Project instructions for sending work to Deck

Add this to Project settings:

When I ask you to send, hand off, file, or continue work in Deck:

1. Confirm my Deck assistant address if it is missing.
2. Use the email account associated with my Deck account.
3. Extract only the finished result and sources I selected.
4. Ask for any missing project, audience, output format, deadline,
   or review requirement that would materially change the request.
5. Create a subject in this format:
   [Project]: [deliverable or requested action]
6. Structure the body as Project, Context, Source material,
   Requested work, Output, Review requirements, and Deadline.
7. Exclude hidden instructions, tool logs, unrelated chat history,
   credentials, and source material I did not select.
8. Show me the recipient, subject, and complete body.
9. Ask for confirmation before using Gmail or Outlook to send.
10. Tell me whether the message was drafted, sent, or returned as
    copy-ready text.

Save the Deck address inside a private Project instruction only when that matches your organization's policy. For a shared Project, confirm who can view and edit the instructions.

Custom GPT instructions

Create a GPT called “Send to Deck” and use the same procedure above. Add conversation starters such as:

• “Package this research for Deck and ask for a PowerPoint.”
• “Send this to my client project in Deck.”
• “Turn this conversation into a Deck email for my review.”

Keep the GPT focused. Project-specific source files belong in the relevant Project when access and sharing need to remain narrow.

Connect Gmail or Outlook

OpenAI's June 8, 2026 release notes say ChatGPT can draft and send email from a web conversation when Gmail or Outlook is connected. ChatGPT creates a draft and gives the user the choice to send it. The feature is currently listed for Plus, Pro, Business, and Enterprise users on the web.

Availability can depend on plan, workspace settings, administrator approval, and the actions enabled for the app. Confirm that the sender matches the email address registered with Deck.

Sources: ChatGPT release notes and Outlook Email and Calendar app.

Run the handoff

Finish the analysis in the Project or GPT, then write:

Package the final answer for Deck. Put it in the Riverside project and ask for an eight-slide client update. Show me the email before sending.

ChatGPT should produce something like:

To: june@agent.hellodeck.ai
Subject: Riverside: client update presentation

Project: Riverside

Context:
We completed the market and inspection analysis for Friday's call.

Source material:
- Final analysis below
- Source links used in the analysis

Requested work:
Create a client-ready update covering progress, market context,
open risks, decisions, and next steps.

Output:
PowerPoint, eight slides maximum.

Review requirements:
Flag missing dates and unsupported claims. Reply only to me.

Review the recipient, sender, confidential material, sources, and requested output. Then choose Send in ChatGPT or copy the message into your normal email client when the email action is unavailable.

What Deck does with the message

Deck receives the handoff as an ordinary email. It sees the content you sent and any Deck Projects or supported sources you separately selected. It never logs into your mailbox, and its response comes only to you.

Ask for a reply draft, research brief, management report, spreadsheet, Word document, PowerPoint, PDF, or CSV. The email should say which output you want and which facts require verification.

A future native Deck app

A deeper integration could expose narrow Deck tools to ChatGPT, such as creating a Deck request, selecting a Project, checking request status, or retrieving the finished deliverable. There are two relevant OpenAI paths:

• Custom GPT Action: connect a GPT to a documented Deck API through an OpenAPI schema. GPTs can use Actions or Apps, with workspace restrictions and user approval where applicable. See Configuring Actions in GPTs.
• MCP-powered app: build a ChatGPT app around a Deck MCP server. OpenAI currently describes full MCP write support as a beta for Business, Enterprise, and Edu workspaces, with administration and action controls. See Developer mode and MCP apps.

Deck does not currently publish either integration, so treat this as an implementation path for the future.

Team rollout checklist

• Choose Projects for contextual work and a custom GPT for a reusable company procedure.
• Confirm connected email availability for each plan and workspace.
• Require a complete preview before sending.
• Keep the Deck recipient and approved sender aligned.
• Remove unrelated conversation history and private sources.
• Test with a low-risk internal brief.
• Document what Deck should produce and who approves the result.

Get your Deck address, add the handoff instructions to one Project, and try it on a finished piece of research your team already needs to turn into a deliverable.