The moment it happens

Share reader survey answers in Slack

When a reader answers one of your surveys, the response is posted for the team to read.

Runs: The moment it happens
Apps: beehiiv
AI: Not needed
Access: API key

Send this to your assistant

Create a ClickRuntime automation: when a reader answers a beehiiv survey, post the question and their answer to #reader-feedback in Slack.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Readers who answer a survey are telling you something they will not say in an email: why they subscribed, what they would pay for, what they did not like. In beehiiv, responses collect in a report that you open occasionally. A reader who writes that they are about to unsubscribe because of an issue, or a sponsor prospect who mentions their budget in an answer, is found after the moment to respond has passed.

When a reader submits a survey answer in beehiiv, an event reaches ClickRuntime. ClickRuntime posts the response to Slack, so you and your team read what readers say as it arrives and can reply while the survey is still on their mind.

It is a good fit for publishers who use surveys to guide editorial choices or to qualify sponsors. Teams with a growth lead can use it to spot patterns in how readers describe the newsletter.

What you get out of it

Feedback is read while it is fresh
Reading an answer the day it is written lets you respond before the reader has moved on. A quick reply can turn a complaint into loyalty. A quick, friendly reply can turn a complaint into loyalty before the reader leaves for good.
Sponsors and leads are not missed
Sometimes a survey reveals a business reader who might advertise. Seeing the answer in a channel lets you follow up within hours and win the conversation. Business readers rarely repeat themselves, so a fast follow-up often wins the whole conversation.
Editorial decisions use real words
Reading answers one by one gives a feel for readers that averages do not. Direct quotes make it easier to pick topics and angles people want. Direct quotes make it easier to pick topics and angles that readers genuinely want to see.
The team shares one view of the audience
Everyone in the channel sees the same answers. Disagreements about what readers want become discussions based on quotes, not on opinion. Disagreements about what readers want become discussions anchored in actual quotes from them.
Problems are noticed early
A cluster of complaints about the same issue shows up quickly. You can fix a broken link or a confusing format before it affects many more readers. Fixing a broken link or confusing format early limits the number of readers who are affected.

How it works

What happens, step by step

When a reader answers one of your beehiiv surveys, beehiiv tells ClickRuntime straight away.
The automation picks out the reader's email, the question and their answer.
It posts them to your #reader-feedback Slack channel for the team to read.

Before it runs live

Connect beehiiv
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Share reader survey answers in Slackjust nowSucceeded

Slack · #reader-feedbackSurvey answer from sam@northwind.example *What should we cover next?* > More teardown posts

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Act only on the items that match your own rules, and skip the rest
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other beehiiv steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

survey_response_alert.pyexample

from clickruntime import on_event, notify

@on_event
def handle(event):
    body = event.json
    data = body.get("data") or {}
    notify.slack(f"Survey answer from {data.get('email', 'a reader')}\n*{data.get('question')}*\n> {data.get('answer')}",
                 channel="#reader-feedback")
    return {"posted": True}

FAQ

Common questions

Does it post every answer or only some?

By default every response is posted. If volume is high, ask your AI assistant to post only answers to a specific question or answers that contain certain words, such as cancel or advertise, so the channel highlights what matters.

Are reader emails shown with the response?

Only if you want them. The message can include the subscriber's email so you can reply, or it can show answers anonymously if your survey promised anonymity. Choose according to what readers were told when they answered.

What if the survey has several questions?

Each question and answer can be listed together in a single message, so you read the full response at once. For long surveys, the message can show only the questions you pick, which keeps the channel readable.

What permissions does it need?

API key. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run for each event the app sends.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

The moment it happens