# Newsletter send desk for drafts you write in Google Docs

> Move every draft from Drive to your email list in one screen: pick the audience, see the real recipient count, and send without fixing formatting by hand.

- Workflow type: app
- Services: GetResponse, Google Drive, Google Docs, Slack Bot
- Categories: Marketing
- Published: 2026-08-22

## What it does

- Pulls every newsletter draft from a Google Drive folder you choose into a three column board: Drafts, Ready, and Sent.
- Opens any draft as a live email preview beside a send panel where you pick the list or a narrower audience, choose a verified sender, and see exactly how many people it will reach.
- A prep button hands the draft to a background assistant that converts it into clean email formatting, suggests three subject lines and a preheader, and flags spammy wording and broken links for you to approve.
- Sends only after a confirmation step that restates the audience size, marks the newsletter as queued until your email provider confirms it went out, and posts a short note to Slack so the team knows what landed.

## What you'll need

- A GetResponse account with at least one contact list and a verified sender address
- A Google account with your newsletter drafts saved in a Drive folder
- A Slack workspace, if you want the team notified whenever a send goes out

## Prompt

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.

## How to customize

- Point the Drafts column at any Drive folder, and switch folders when you run more than one newsletter series.
- Decide whether each send goes to a whole list or a narrower saved audience, and pick which Slack channel gets the note.
- Tune what the prep assistant checks for, such as your own banned phrases, link rules, or house style for subject lines.

## FAQ

### Will my Google Doc formatting survive the move into email?

That is exactly what the prep step is for. Instead of pasting the document into a composer and fixing the spacing and fonts by hand, a background assistant rewrites the draft into clean email formatting, and you see the result in a preview next to the send panel before anything goes out.

### Can I see how many people a send will actually reach?

Yes. When you pick a list or narrow down to a saved audience, the send panel shows the real recipient count pulled from your account rather than an estimate, and the confirmation step restates that number before the send goes anywhere.

### Why does a newsletter show as queued instead of sent?

GetResponse accepts a send and processes it in the background rather than finishing instantly. The app marks the newsletter as queued right away and checks its real status the next time you open the board, so the Sent column always reflects what genuinely went out.

### Does anything send on its own?

No. Every send needs a person to choose the audience and confirm it. The prep assistant only drafts, suggests, and flags problems. A human approves the result before anything is queued.

### Can I send a newsletter I already drafted inside GetResponse?

Yes. Alongside the Google Docs path, the desk lists newsletters you already built in GetResponse and lets you send one through the same confirmation step, so both routes live on the same screen.

Use this prompt in General Input: https://www.generalinput.com/prompts/newsletter-send-desk-for-drafts-you-write-in-google-docs