The moment it happens
Turn support requests into prioritised Asana tasks
Each request from your form becomes a task with a priority and summary, and your team sees it in Slack.
- Runs
- The moment it happens
- Apps
- Asana
- AI
- Yes, uses the built-in AI allowance
- Access
- write
Send this to your assistant
Create a ClickRuntime automation: give me a link my support form can send requests to. For each one, set a priority of high, medium or low, create a task in my Support project in Asana, and post it to #support in Slack.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A support lead at a software company receives requests through a web form, a shared inbox and a partner portal. Someone has to read each one, decide whether it is urgent, write a task in Asana, pick a project and tell the team. When two people are out, requests wait for hours, a billing complaint is treated like a feature idea, and the customer who wrote in with a broken checkout hears nothing until the afternoon.
As soon as a request is sent to your ClickRuntime link, the built-in AI reads it, writes a short summary and assigns a priority such as urgent, normal or low. ClickRuntime then creates the Asana task with that summary and priority in the project you chose, and posts a message to Slack so the team sees it immediately.
Small support and operations teams that cannot afford a dedicated triage person get the most from it, and the same flow suits internal requests to IT or finance.
What you get out of it
Urgent requests jump the queue
A customer reporting a failed payment is flagged as urgent and shown in Slack at once. It no longer waits behind a pile of low-priority questions until someone finally scrolls far enough.
Triage no longer depends on who is online
Requests that arrive at 7 pm or during a team offsite are still summarized, prioritized and filed. The morning shift starts with an ordered list instead of a pile to sort.
Tasks are readable at a glance
A two-line summary replaces a rambling email thread in the task title and description. Whoever picks it up knows the issue in seconds and does not have to reread the original message.
The team hears about it together
Because Slack gets a post the moment the task is created, nobody works on it twice by accident and a lead can reassign the task in the thread right away.
Response times become measurable
Every request has a creation time in Asana, so you can compare how long urgent and normal tasks take to close. That gives you real numbers for staffing and for promises to customers.
How it works
What happens, step by step
When a support request arrives, ClickRuntime picks it up straight away.
AI reads it, writes a one-line summary and decides how urgent it is.
A task is created in your Asana project with that summary and priority.
A message goes to your #support Slack channel with the priority, the summary, who sent it and a link to the task.
Before it runs live
- Connect Asana
- 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
- Change what the AI looks for, or how it writes the result
- Add another app, for example also send it to Slack
- Combine it with other Asana steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_event, http, credentials, ai, notify
SUPPORT_PROJECT = "SUPPORT_PROJECT_GID"
def asana(method, path, body=None, **params):
r = http.request(method, f"https://app.asana.com/api/1.0{path}", params=params,
json={"data": body} if body else None,
headers={"Authorization": f"Bearer {credentials.secret('ASANA_TOKEN')}"})
r.raise_for_status()
return r.json().get("data")
@on_event
def handle(event):
req = event.json or {}
text = f"{req.get('subject', '')}\n{req.get('message', '')}"[:2000]
try:
priority = ai.generate(f"Priority (high, medium or low) for this support request:\n{text}",
max_output_tokens=5).text.strip().lower()
except (ai.AINotIncluded, ai.AILimitReached):
priority = "medium"
task = asana("POST", "/tasks", {"name": f"[{priority}] {req.get('subject', 'Support request')}",
"notes": f"From {req.get('email')}\n\n{req.get('message', '')}",
"projects": [SUPPORT_PROJECT]})
notify.slack(f"{priority.upper()}: {req.get('subject')} from {req.get('email')}\n{task['permalink_url']}", channel="#support")
return {"priority": priority}FAQ
Common questions
How does the AI decide what is urgent?
Where do requests come from?
What if the AI gets the priority wrong?
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
Turn app errors into Asana tasks
Each new error becomes a task with a likely cause and a suggested fix, and repeats of the same error are skipped.
See how it worksTurn meeting notes into Asana tasks
Paste your notes and each action item becomes a task with an owner and due date, with a summary in your inbox.
See how it worksCreate Asana tasks from anything you send
Text sent to your link becomes a task in your Asana inbox project, ready to sort later.
See how it worksKeep exploring
Set up “Turn support requests into prioritised Asana tasks” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.