Turn every GetResponse newsletter into LinkedIn and X posts
Every newsletter you send gets rewritten into a LinkedIn post and an X thread, drafted for your approval in Slack before anything goes live.
Whenever I send a new newsletter from GetResponse, I want it automatically repurposed into social content instead of dying in the inbox. Trigger this on the GetResponse poll trigger for the "New Newsletter" event, so the workflow runs each time a new newsletter appears in my account.
Start by pulling the full newsletter body with the GetResponse "Get Newsletter" operation using the newsletter ID from the trigger. The trigger payload alone is not enough, so always fetch the complete content before doing anything else. Read the whole thing carefully, including the subject line.
Before writing anything, decide whether this newsletter is worth repurposing at all. Skip it entirely if it is purely transactional or a promotional blast with no substantive content: order confirmations, receipts, password resets, event reminders, discount or sale announcements, and "last chance" pushes are all skips. If there is no real idea, insight, story, or argument in the email, stop the workflow and do not post anything. Only continue when the newsletter genuinely has something to say.
For newsletters that pass, identify the two or three strongest ideas in the piece. These should be the arguments, insights, or stories that would stand on their own, not a summary of every section. Then write two drafts from those ideas.
The first draft is one LinkedIn post. Lead with a hook in the very first line that makes someone stop scrolling. Use short paragraphs with line breaks between them so it stays readable on mobile. Do not put any link in the opening line. Always include my newsletter subscribe link somewhere in the body of the post, near the end, but never in that first line, because a link up top suppresses reach.
The second draft is one X post, or a short thread if the content needs more room. Respect the X character limit: if the idea does not fit in a single post, split it into a numbered thread rather than truncating it. Never cut a sentence off mid thought to make it fit.
Both drafts must be genuinely rewritten for their platform, not the same text pasted twice and not lifted verbatim from the email. LinkedIn gets a more considered, paragraph driven version; X gets a tighter, punchier version. Match the tone of the newsletter itself rather than defaulting to a generic marketing voice: if the newsletter is casual and personal, the posts should be casual and personal, and if it is technical and dry, keep that register.
Before anything goes live, post both drafts into my Slack review channel using the Slack Bot "Send a Message" operation. Label them clearly as the LinkedIn draft and the X draft, include the newsletter subject line for context, and show the full text of each so I can read them without opening anything else. Then wait for a human response in that thread.
If I approve, publish both: use the LinkedIn "Create Post" operation for the LinkedIn post, and the X (Twitter) "Create Tweet" operation for the X post. If the X content is a thread, post the first tweet and then post each subsequent tweet as a reply to the previous one so the thread chains correctly. If instead I reply with edits, apply my feedback, post the revised drafts back into the same Slack thread, and wait for approval again. Never publish anything without an explicit approval.
Once both are published, reply in the same Slack thread with the live links to the LinkedIn post and the X post so I have a record of what went out and where.
What does this prompt do?
- Watches your GetResponse account and picks up each new newsletter automatically, so nothing has to be forwarded or copied by hand.
- Reads the full newsletter, finds the two or three strongest ideas in it, and writes a LinkedIn post plus an X post or short thread, each written for that platform rather than copy and pasted from the email.
- Drops both drafts into a Slack channel and waits, so you can approve them or reply with edits before anything is published.
- Publishes to LinkedIn and X once you approve, then replies in the same Slack thread with the live links.
What do I need to use this?
- A GetResponse account where you send your newsletters.
- A LinkedIn account you want to publish posts from.
- An X (Twitter) account with posting turned on.
- A Slack workspace and a channel where the drafts should land for review.
How can I customize it?
- Change which Slack channel the drafts go to, or route them to a private channel only you can see.
- Adjust what counts as skippable so promotional blasts, receipts, and event reminders never get repurposed.
- Tune the writing style, post length, and whether X gets a single post or a longer thread.
FAQs
Does anything get posted without my approval?
What happens to newsletters that are just promotions or receipts?
Will my X post get cut off if the newsletter is long?
Will the posts sound like generic marketing copy?
Can I still promote my newsletter signup in the posts?
Related templates
See how your brand's news coverage and sentiment stack up against four competitors, then let an assistant write the weekly report for you.
One screen showing every social post waiting on approval, sorted by deadline, so reviewers can approve or reject without leaving the page.
Every Monday, find the past champions and closed-won contacts who changed jobs, update Attio, and get the moves worth chasing in Slack.
Staff submit what happened, your social manager edits the copy, picks the accounts and puts it on the calendar without a single spreadsheet.
Open one board each morning, see which voice calls went badly, replay the exact moment the caller got frustrated, and file the fix.
A personal queue of every overdue Guru card, sorted by how late it is, with one-click verify, reassign, comment, and an agent that drafts the refresh for you.
Stop letting your best newsletter ideas die in the inbox.
Send one newsletter and get a LinkedIn post and an X thread ready for review, with you approving every word before it publishes.