Configure incoming-mail workflows
Prepare a workflow around Stacksync’s built-in Gmail new-message trigger and an authorized Gmail connection. This trigger does not require a custom HTTP step; other mailbox actions may.
Your connection path
Your assistant works through your Stacksync workspace and its available connections.
“Design a new-email intake workflow”
Stacksync MCP · Communications
Use Stacksync MCP to design workflows that start from Gmail. Stacksync documents a built-in new-message trigger; broader mailbox search or draft operations must be verified in the catalog or implemented as custom Gmail API steps.
01 / The connection
Use Stacksync MCP to design workflows that start from Gmail. Stacksync documents a built-in new-message trigger; broader mailbox search or draft operations must be verified in the catalog or implemented as custom Gmail API steps. Add the Stacksync MCP server to ChatGPT, then use the connection path below.
The server belongs to Stacksync. The available Gmail operations depend on your connection, permissions, and connector modules.
Explore the Gmail connector →02 / Capabilities
Choose the connection path that fits the job. Your assistant inspects the available tools before configuring or running an action.
Prepare a workflow around Stacksync’s built-in Gmail new-message trigger and an authorized Gmail connection. This trigger does not require a custom HTTP step; other mailbox actions may.
When no catalog action fits, prepare custom HTTP or code steps using Gmail message search and a separate detail fetch.
Design a workflow that prepares a Gmail draft through a verified action or custom API request, keeping sending as a separate decision.
03 / Setup
Connect the MCP server first. Then connect Gmail using the requirements below.
Add Stacksync as a custom MCP app in ChatGPT and sign in with OAuth.
Open Settings → Apps → Advanced settings and turn on Developer mode. If the option is unavailable, check the account or workspace policy with your administrator.
Select Create app, name it Stacksync, enter the server URL below and choose OAuth. Complete the Stacksync sign-in and select your default workspace.
https://mcp.stacksync.com/mcp Select Stacksync from the chat tools menu so the conversation can use its tools. Signing in to ChatGPT itself does not sign you in to Stacksync.
Ask “List my Stacksync workspaces.” Confirm the workspace before choosing a connector or preparing a change. Connecting the assistant does not start a sync.
Ask “List my Stacksync workspaces.” Select the workspace you want to use, then ask the assistant to inspect the available Gmail connection and capabilities.
04 / Put it to work
Example prompts for Gmail in ChatGPT. The outcomes describe what to expect, not results from your account. Review the proposed configuration before running it.
Inspect my Gmail connections, the Gmail trigger form and any existing intake workflow. Propose a workflow for new incoming messages with the sender and subject criteria I choose, then a review step before any downstream record is created. Show the trigger configuration and permitted message fields. Do not save or activate the workflow before I approve it.
An incoming-message workflow proposal with explicit filtering and downstream review.
Check whether the Stacksync catalog has the Gmail read action needed for my request. If not, propose custom API steps using messages.list for my search query and messages.get only for selected results. Explain the OAuth scopes, date range, result limit and pagination. Keep credentials outside chat and wait for review before running the reads or saving a workflow.
A mailbox review plan with bounded scope and an explicit custom API path.
Inspect available Gmail modules and my intended workflow. If a draft action is absent, propose a custom Gmail drafts.create step with securely configured OAuth. Use the recipient and source message I identify, show the full proposed subject and body, and separate draft creation from sending. Do not create a draft, send mail or deploy anything yet.
A draft-only workflow proposal with the intended recipient and complete message visible for review.
05 / Before you run
OAuth access follows your Stacksync role. Choose read-only access during sign-in when appropriate. Workspace owners can enable “Ask before every change”; it is a configurable setting. Direct connector actions also follow gateway policies.
Read about permissions and approvals ↗06 / Common questions
The workflow trigger reference explicitly documents a built-in Gmail trigger for new messages on a connected mailbox. You do not need to implement this trigger as a custom API call. Search, draft and send actions must be checked separately.
First inspect the current catalog. If the needed action is unavailable, Stacksync’s documented custom HTTP or code path can be used to implement the Gmail API, with separate OAuth configuration and testing.
No. Gmail draft creation and message sending are distinct API operations. These examples request a reviewed draft proposal and do not authorize sending.
Reviewed · Product documentation and connector references
Keep building