The moment it happens

Post form submissions to a Discord channel

Form entries and app events show up as tidy messages in the channel you pick.

Runs: The moment it happens
Apps: Discord
AI: Not needed
Access: Send Messages (+ Manage Channels to create channels)

Send this to your assistant

Create a ClickRuntime automation: give me a link my site's contact form can send to. Post each submission's name, email and message as a formatted message in #leads on my Discord.

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 form on your website collects sign-ups, bug reports or order requests, and the responses go to an inbox nobody checks quickly. A payment tool, a game server or a monitoring service can send events, but raw webhook data is an unreadable blob of JSON. Teams end up either missing the submissions or pasting them into Discord by hand, which loses detail and takes someone's time.

When a form submission or app event arrives, the automation receives the payload, picks out the fields that matter and posts them as a tidy embed in the channel you choose. You can send each form to its own channel, so support requests, feedback and orders land where the right people are already reading.

It suits small businesses, indie developers and communities that want events in Discord without writing a bot.

What you get out of it

Submissions seen in seconds
A message in a channel the team watches is noticed far sooner than an email in a shared inbox. A customer who wrote in gets a faster reply, and a bug report reaches the person who can fix it while the details are still fresh.
Readable instead of raw data
Fields are laid out with labels in an embed, so a person can understand a submission at a glance without decoding JSON. Nobody on the team needs to be technical to read what a customer, player or sensor actually sent.
Right channel for each source
Sending each form to its own channel keeps support, sales and feedback apart. Each group sees only the messages meant for them, so channels stay relevant and nobody mutes them because of unrelated noise.
No bot to write or host
You get the convenience of a custom integration without code, hosting or upkeep. If a form field is renamed or added, the layout is updated by telling your AI assistant, instead of redeploying anything.
Shared visibility for the team
Everyone in the channel can see an event, react to it and reply in a thread. That beats a single person forwarding emails around, and it shows at a glance whether someone has already picked a submission up.

How it works

What happens, step by step

When someone submits your form, ClickRuntime receives their answers straight away.
It formats the name, email and message into a tidy card.
The card is posted to your Discord channel, such as #leads. You can send each form to its own channel.

Before it runs live

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

What you get

RunsThe moment it happens

Post form submissions to a Discord channeljust nowSucceeded

Discord · #leadsNew contact: Dana Ortiz Email: dana@northwind.example · "Do you offer annual billing?"

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

forward_incoming_webhook_events_to_a_channel.pyexample

from clickruntime import on_event, http, credentials

LEADS_CHANNEL = "LEADS_CHANNEL_ID"

def discord(method, path, **kw):
    r = http.request(method, f"https://discord.com/api/v10{path}",
                     headers={"Authorization": f"Bot {credentials.secret('DISCORD_BOT_TOKEN')}"}, **kw)
    r.raise_for_status()
    return r.json() if r.content else None

@on_event
def handle(event):
    f = event.json or {}
    discord("POST", f"/channels/{LEADS_CHANNEL}/messages", json={"embeds": [{
        "title": f"New contact: {f.get('name', 'Unknown')}",
        "description": str(f.get("message", ""))[:3000],
        "fields": [{"name": "Email", "value": f.get("email", "-")}],
    }]})
    return {"posted": True}

FAQ

Common questions

Which tools can send events to it?

Anything that can send an HTTP POST with JSON can post to the ClickRuntime webhook address, including form builders, payment tools, game servers and monitoring services. Each sender needs the webhook URL pasted into its settings, and no further setup is required on its side.

Can it handle several different forms?

Yes. The payload usually identifies the form or event type, so each can be formatted differently and sent to a different channel. Tell your AI assistant to map each form to its channel and fields, and the rest follows automatically.

What if a field is missing from a submission?

Missing fields are skipped rather than shown as blank, so the embed stays clean. If an essential field is absent, the run log in the ClickRuntime dashboard shows the raw payload, so you can see exactly what the sender actually delivered.

What permissions does it need?

Send Messages (+ Manage Channels to create channels). 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.

Every 5–60 minutes