Slack only knows its half.
Slack tracks email history (gmail/outlook), but can't see documents authored (Google Drive/SharePoint). So what you read there is already partial.
Build a Content Ghostwriter Agent withSlack, Confluence, and Gmail
The data for your status review already exists in Gmail / Slack / Confluence. The problem is no one view joins it. Effective ghostwriting requires learning from someone's actual writing across multiple platforms; their emails, their docs, their messages.
Slack says one thing about email history (Gmail/Outlook), Confluence says another.
The status review eats the gap.
The status review eats the gap.
Confluence holds what Slack misses.
Documents authored (Google Drive/SharePoint) lives in Confluence, cut off from email history (gmail/outlook), so content ghostwriter guesses at the link.
Gmail catches it quietly.
Slack messages surfaces in Gmail ahead of time, but that tab is closed during content ghostwriter.
Under The Hood
Generates content drafts that match a specific person's writing style using their past work from Slack, Confluence, and Gmail in one prompt, nothing to stitch. Already connected.
01
Pull generates content drafts that match a specific person's writing style using their past work from Slack (comms layer)
Email history (Gmail/Outlook)
02
Check documents authored (Google Drive/SharePoint) from Confluence (docs hub)
documents authored (Google Drive/SharePoint)
03
Check slack messages from Gmail (comms layer)
Slack messages
output
Agent-ready output
Content Ghostwriter's rundown: Generates content drafts that match a specific person's writing style using their past work. Sorted by what needs you first.
The Context Store
Email history (Gmail/Outlook) and the rest of Gmail / Slack / Confluence, already one record.
Before the prompt runs, the Context Store has matched email history (Gmail/Outlook), documents authored (Google Drive/SharePoint), Slack messages, Confluence pages from Gmail / Slack / Confluence and 2 more onto one record record. Content ghostwriter just reads it, no ID-stitching.
Your agent queries one surface instead of three APIs. Faster responses, lower cost per query, and results that work because the relationships were built before you asked the question.
PRE-JOINED RECORDUNIFIED SCHEMAONE API SURFACE
The Prompt
Copy. Paste.
a Content Ghostwriter Agent
Two steps. Your data, your results, under 60 seconds.
01install
Connect the Airbyte Agent MCP02copy and run
Help me turn Slack, Confluence, and Gmail into a single status review I can act on.
SETUP
Use Airbyte's MCP. 5+ connected sources behind one natural-language surface.
WORKFLOW
list connectors -> link Slack, Confluence, and Gmail -> pull email history (Gmail/Outlook), documents authored (Google Drive/SharePoint), Slack messages, Confluence pages -> join on the record key -> analyze. An unlinked tool returns a self-describing prompt; a one-time browser auth and retry.
TASK
Generates content drafts that match a specific person's writing style using their past work. Deliver a rundown I can paste into the status review. Ranked, sourced, one action per item.The Outcome
Content Ghostwriter: 2 hours of work, one short run.
10x
Faster
10x speed: content ghostwriter turns a 2-hour status review into under a minute.
90%
Cheaper to run
90% off the build cost: 5 sources already licensed, nothing extra to generates content drafts that match a specific person's writing style using their past work.
3 -> 1
Tools, one query
3 sources, 1 prompt: Slack, Confluence, and Gmail reconciled before content ghostwriter runs.
Based on internal benchmarks comparing Context Store queries to sequential API calls across equivalent datasets.
01 · Output
Ranked, not dumped
A 1-10 score on each record means the urgent email history (Gmail/Outlook) rises to the top of content ghostwriter on its own.
02 · Signal
Where the tools disagree
When Confluence and your comms layer disagree on generates content drafts that match a specific person's writing style using their past work, the gap is flagged. Not averaged into a guess.
03 · Context
Inline evidence
Each line carries its evidence. Generates content drafts that match a specific person's writing style using their past work pulled from Confluence and Gmail. Right where you read it.
04 · Action
Next action per item
Every row ends in a move: content ghostwriter tells you the owner and the move.
05 · Brief
Rundown-ready
The rundown arrives meeting-ready: email history (Gmail/Outlook) first, sources attached, Slack, Confluence, and Gmail reconciled.
More cross-functional agents like Content Ghostwriter
view All use casesMeeting Action Item Tracker
Your status review is only as fresh as the slowest tab. 70% of meeting action items are never completed because they're buried in notes. Yet the inputs sit split across Granola / Jira / Slack.
AI Meeting Assistant
The data for your status review already exists in Gmail, HubSpot, and Salesforce. The problem is no one view joins it. Manual note-taking misses 50% of details.
Delegation Tracker
Cross-functional teams run status reviews on stale, scattered data: Linear, Slack, and Intercom each hold a piece, none hold the whole. Managers send requests that get lost; tracking responses requires monitoring multiple communication channels and understanding conversational threading.
Common questions
Didn't find your answer? Please don't hesitate to reach out.
Why not call the Slack, Confluence, and Gmail APIs directly to generates content drafts that match a specific person's writing style using their past work?
Auth, paging, rate limits and schema-stitching per tool. Airbyte's MCP hands content ghostwriter one surface over email history (Gmail/Outlook), documents authored (Google Drive/SharePoint), Slack messages, Confluence pages.
Is email history (Gmail/Outlook) stored anywhere by Content Ghostwriter?
No, content ghostwriter reads email history (Gmail/Outlook), documents authored (Google Drive/SharePoint), Slack messages, Confluence pages live through the connectors and returns the rundown; nothing persists outside Slack, Confluence, and Gmail.
How do I trust the status review?
Content Ghostwriter cites a source per line. Email history (Gmail/Outlook) from Slack, the rest from Confluence and Gmail. So any figure traces back.
What Slack data does Content Ghostwriter touch?
Just email history (Gmail/Outlook), plus documents authored (Google Drive/SharePoint), Slack messages, Confluence pages, via Slack's scoped permissions. Content ghostwriter copies nothing outside your stack.
Content Ghostwriter is one prompt away from Gmail / Slack / Confluence.
50+ connectors including Slack, Confluence, and Gmail are ready. Give content ghostwriter the access to generates content drafts that match a specific person's writing style using their past work.
