The moment it happens
Post new Jotform entries to Slack
Your team sees the key details of each submission in their channel as soon as it comes in.
- Runs
- The moment it happens
- Apps
- Jotform
- AI
- Not needed
- Access
- Full Access
Send this to your assistant
Create a ClickRuntime automation: when my Jotform "Event Registration" form gets a new submission, post the attendee's name, email and ticket type to #events in Slack.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A wedding photographer gets a Jotform inquiry on Saturday night, the studio manager checks the form inbox on Monday, and by then the couple has already booked someone else. The same thing happens to agencies with project briefs, schools with enrollment forms and clinics with intake requests. The entries pile up in a place nobody watches, and every hour of delay lowers the odds of a reply.
Each time someone submits one of your Jotform forms, the entry arrives in ClickRuntime the moment Jotform sends it. A short summary of the answers that matter, such as name, email, the request itself and the date, is posted to the Slack channel you choose, so the person who owns the follow-up sees it in the tool they already have open.
It suits small teams where one shared channel doubles as the front desk, and it works the same for a lead form, an order form or an event signup.
What you get out of it
Replies go out while interest is warm
A prospect who filled in a quote request at lunch is far more likely to answer a reply sent within the hour than one sent two days later. Seeing the entry in Slack turns a missed opportunity into a same-day conversation.
No one has to babysit the form inbox
Checking Jotform several times a day is a chore that gets skipped on busy days. The post in Slack removes that duty, so the check happens on its own and nobody carries the worry that something sat unread.
The whole team sees the same entry
When an entry lands in a channel, a colleague can reply in the thread that they are taking it. That stops two people answering the same customer and stops everyone assuming someone else did.
A searchable trail of what came in
Slack keeps every post, so you can later search the channel for a customer name or a phrase from their request. That is faster than opening each submission in Jotform to find one conversation.
Fewer hand-offs to the right person
Because the key answers are in the message, whoever reads it can tell at a glance whether it is sales, support or spam and tag the right colleague, instead of forwarding screenshots around.
How it works
What happens, step by step
When someone submits your Jotform form, the entry reaches ClickRuntime straight away.
It picks out the key details, such as the person's name, email and the option they chose.
A short message with those details is posted to your Slack channel.
Before it runs live
- Connect Jotform
- Paste your automation's link into the other app's webhook settings
What you get
Build your own
Need it to work differently?
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 Jotform steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_event, credentials, http, notify
@on_event
def handle(event):
sub_id = (event.json or {}).get("submissionID")
sub = http.get(f"https://api.jotform.com/submission/{sub_id}",
headers={"APIKEY": credentials.secret("JOTFORM_API_KEY")}).json()["content"]
by_label = {a.get("text", "").lower(): a.get("prettyFormat") or a.get("answer")
for a in sub["answers"].values()}
notify.slack(f"New registration: {by_label.get('name')} ({by_label.get('email')})"
f" · {by_label.get('ticket type', 'no ticket type')}", channel="#events")
return {"submission": sub_id}FAQ
Common questions
Which Jotform fields end up in the Slack message?
Does it work if I have several Jotform forms?
Do I need a paid Jotform plan for this?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Get each Jotform submission by email
Every new entry on your form arrives in your inbox as a tidy list of question labels and answers.
See how it worksGet a weekly count of submissions per form
Each Monday morning you see how many entries every form received the week before.
See how it worksPost new orders and sign-ups to Slack
When something happens in your shop, app or form, the details land in the right channel straight away.
See how it worksKeep exploring
Set up “Post new Jotform entries to Slack” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
