The moment it happens

Share new Tally responses in Slack

Your channel gets a short post for every response, so nobody has to check the form.

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

Send this to your assistant

Create a ClickRuntime automation: post every new response to my Tally "Customer feedback" form in #feedback on Slack, with the rating and the comment.

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

A small team shares one Tally form for support requests, partnership enquiries and demo bookings. The submissions go to one person's inbox, or to the Tally dashboard, and everyone else asks in chat whether anyone saw the new request. Two people reply to the same enquiry, or nobody does, because each assumes someone else has it. Requests then wait in silence for hours.

When a Tally response arrives, ClickRuntime formats a short summary of the answers and posts it to the Slack channel you pick. The whole team sees the request at the same moment and can claim it with a reaction or a reply, so ownership is settled in a few seconds.

It suits support desks, sales teams and community groups who handle forms together rather than through a single mailbox.

What you get out of it

Requests have an owner within seconds
A message in a shared channel invites someone to say I have this. That removes the duplicate replies and the dropped requests that come from a hidden inbox. Fewer requests go unanswered because everyone assumed someone else had them.
Shared visibility improves response times
When everyone can see how long a request has been waiting, someone steps up. Public queues move faster than private ones, particularly during busy periods. A visible queue is hard to ignore for long.
Handoffs are simple
A teammate can reply in the thread with the details they found, tag a colleague who knows the customer and keep the discussion attached to the original submission. Context stays attached to the request throughout.
The channel becomes a log of enquiries
Scrolling or searching the channel shows past requests and who handled them. That is useful for spotting repeat issues and for onboarding new colleagues. Searching the history later is as simple as typing a name.
Urgent forms can stand out
Using a condition on an answer, such as priority or product, you can tag the on-call person for urgent requests while routine ones simply post. Important enquiries get attention without spamming everyone.

How it works

What happens, step by step

When someone answers your Tally form, the response reaches ClickRuntime straight away.
It turns the answers into a short summary, such as the rating and the comment.
The summary is posted to your Slack channel, so nobody has to check the form.

Before it runs live

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

What you get

RunsThe moment it happens

Share new Tally responses in Slackjust nowSucceeded

Slack · #feedbackNew feedback: ★★★★ > Setup was quick, but I couldn't find the export button.

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 Tally 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.

slack_alert_for_new_submissions_tally.pyexample

from clickruntime import on_event, notify

def fields(payload):
    out = {}
    for f in payload["data"]["fields"]:
        value = f.get("value")
        if f.get("options") and value:
            ids = value if isinstance(value, list) else [value]
            value = ", ".join(o["text"] for o in f["options"] if o["id"] in ids)
        out[f["label"]] = value
    return out

@on_event
def handle(event):
    answers = fields(event.json)
    rating = next((v for k, v in answers.items() if "rating" in k.lower()), "?")
    comment = next((v for k, v in answers.items() if "comment" in k.lower()), "") or "(no comment)"
    notify.slack(f"New feedback: {'★' * int(rating) if str(rating).isdigit() else rating}\n> {comment}",
                 channel="#feedback")
    return {"rating": rating}

FAQ

Common questions

Can I post to different channels for different answers?

Yes. A rule on a field, such as topic equals billing, can send the message to a billing channel, while other topics go elsewhere. Explain the rule and approve the change before the next submission.

Does the Slack message include every answer?

By default it shows a compact summary of the main fields. You can include all answers or only a few, and long text can be shortened with a link to the full response so that the channel stays easy to read.

What if the same person submits twice?

Each submission creates its own message, because Tally sends one event per response. If duplicates are a problem, a check on the email address and a short time window can suppress repeats within a few minutes.

What permissions does it need?

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