On a schedule

Post new support tickets to Slack

Every new HubSpot ticket shows up in your support channel with its subject and priority.

Runs: On a schedule
Apps: HubSpot
AI: Not needed
Access: tickets

Send this to your assistant

Create a ClickRuntime automation: every 5 minutes, post new HubSpot tickets to #support in Slack with the subject and priority.

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 customer writes in about a failed invoice export. It becomes a HubSpot ticket in the Support pipeline, set to High priority, and then it waits. The support team is working in Slack and in the help desk inbox, and nobody has HubSpot's ticket view open. Three hours later the customer writes a second time, now angry that nobody has answered, and the first ticket's age has become a complaint rather than a number.

On a schedule you set, ClickRuntime searches HubSpot for tickets created since its last run and posts each new one to your support channel in Slack. Each post shows the subject, the pipeline stage and the priority, so the person who sees it knows how urgent it is before opening anything.

It helps most when tickets arrive from several sources, such as email, chat and forms, and the team does not sit inside HubSpot all day.

What you get out of it

Urgent tickets stop waiting unseen
A High priority ticket that sits for three hours is how a small problem becomes a cancellation. Seeing every new ticket in Slack with its priority means the urgent ones get a human within the same check interval.
Customers do not have to chase
The second email asking whether anyone has seen the first is the most damaging message in support. A timely post in the channel means a first response often goes out before the customer feels ignored.
Support load is visible to the team
When posts arrive in bursts, everyone sees a spike building and can rebalance work. A manager notices that six billing tickets landed in an hour without opening a report or asking around.
No extra seat needed to stay informed
Engineers and account managers who are not support agents can follow the channel and spot tickets about their product area. They get awareness without being given access to the ticket pipeline.
Every ticket has a timestamped trail
The channel history shows when each ticket was announced. In a review of a missed response time, you can see exactly when the team was told rather than reconstructing it from memory.

How it works

What happens, step by step

Every five minutes, ClickRuntime checks HubSpot for tickets created since the last check.
Each new ticket is posted to your support channel in Slack with its number, subject and priority.
It remembers where it left off, so each ticket is posted only once.

Before it runs live

Connect HubSpot

What you get

RunsOn a schedule

Post new support tickets to Slacktoday, 9:00Succeeded

Slack · #supportNew ticket #4821: Can't export invoices to PDF (priority: HIGH)

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

new_ticket_notification.pyexample

import time
from clickruntime import on_trigger, credentials, http, state, notify, report_fetched

@on_trigger
def run(event):
    since = state.get("since") or int((time.time() - 300) * 1000)
    tickets = http.post("https://api.hubapi.com/crm/v3/objects/tickets/search",
        headers={"Authorization": f"Bearer {credentials.connection('hubspot', 'work')}"},
        json={"limit": 50, "properties": ["subject", "hs_ticket_priority", "createdate"],
              "filterGroups": [{"filters": [{"propertyName": "createdate", "operator": "GT", "value": since}]}]}).json()["results"]
    report_fetched(len(tickets))
    if not tickets:
        return {"posted": 0}
    for t in tickets:
        p = t["properties"]
        notify.slack(f"New ticket #{t['id']}: {p['subject']} (priority: {p.get('hs_ticket_priority') or 'none'})", channel="#support")
    state.set("since", int(time.time() * 1000))
    return {"posted": len(tickets)}

FAQ

Common questions

Can it post only tickets with a certain priority?

Yes. A request such as "only post tickets marked High or Urgent" adds a filter on the priority property before anything is posted, and lower-priority tickets are simply skipped. The change is shown to you for approval first, so you can confirm the filter before it applies.

How soon after a ticket is created will it show up in Slack?

It depends on the schedule you pick. A run every 5 minutes means a new ticket appears within about 5 minutes, while an hourly run means up to an hour. Tickets are found by their creation date, so none are missed between runs.

Does it work with tickets created by email or chat?

Yes. It reads tickets from HubSpot itself, so it does not matter whether a ticket came from the support inbox, a form, a chat conversation or was added by hand. If HubSpot holds the ticket and your connection can read tickets, it is included.

What permissions does it need?

tickets. 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 each time it checks. Checks that find nothing new and stop right away aren't counted.

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 10 minutes