Newsletter send desk for drafts you write in Google Docs

Build me a newsletter send desk so I can stop copying drafts out of Google Docs and pasting them into GetResponse by hand. The main screen is a three column board: Drafts, Ready, and Sent.

The Drafts column lists every document in a Google Drive folder I choose, using Google Drive List Files scoped to that folder. Let me set the folder once inside the app and change it later. Ready holds the drafts I have already prepped and approved. Sent shows newsletters that actually went out, reconciled against GetResponse List Newsletters so the column reflects reality rather than what the app assumed happened.

Opening a draft loads its full content with Google Docs Get Document and shows an email preview on the left beside a send panel on the right. The preview should render what the email will really look like, not the raw document structure.

In the send panel I choose the audience. Load my GetResponse lists with List Campaigns, and let me optionally narrow to a saved audience from List Segments. When I pick a segment, show the real recipient count from Get Contacts In Segment rather than an estimate. I also pick the sender, and only addresses returned by List From-Fields are selectable, because those are the verified ones.

Pressing send goes through a confirmation step that restates the audience size in plain words, something like: this goes to 4,812 people on Weekly Digest. Only after I confirm does the app call Send Newsletter.

Important nuance: GetResponse queues sends and returns an accepted response rather than a finished one, so do not show a newsletter as sent immediately. Mark it queued in the Sent column, persist that, and reconcile the real status the next time the board loads by checking List Newsletters and Get Newsletter. A queued item that has resolved flips to sent with its real send time.

Add a prep this draft button on each draft that fires a background agent. The agent reads the document content, converts it into clean email ready HTML, proposes three subject line options and a preheader, and flags spammy phrasing and broken links. It writes all of that back into the app and attaches it to the draft, so I see the converted HTML in the preview, pick one of the three subject lines, and read the flags before anything is queued. Nothing the agent produces is sent automatically. A human approves it, and only then does the draft move to Ready.

When a send goes out, post a short note to Slack using Slack Bot Send a Message so the team knows what landed. Include the subject line, the audience name, and the recipient count, and let me choose the channel in the app.

Alongside the Google Docs path, wire a second path for newsletters already drafted inside GetResponse: list those drafts and let me send one with Send Draft Newsletter from the same desk, using the same confirmation step and the same Slack note.

Persist the app's own state: which Drive folder feeds the Drafts column, the prep output and chosen subject line for each draft, which drafts I have marked Ready, and the queued sends still waiting to be reconciled.