The moment it happens

Log sales call summaries on the HubSpot contact and in Slack

After each sales call, a summary with next steps is added to the contact in HubSpot and shared in #sales.

Runs: The moment it happens
Apps: HubSpot, Slack
AI: Yes, uses the built-in AI allowance
Access: HubSpot contacts read, notes write; Slack chat:write

Send this to your assistant

Create a ClickRuntime automation: when a call transcript is posted, summarise it with next steps, add it as a note on the matching HubSpot contact and share it in #sales.

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 sales rep finishes four demos in a day. By the evening, the details of the second call have blurred, the CRM notes say 'good call, follow up', and her manager has no idea which deals moved.

A summary written straight from the transcript, saved on the contact and shared with the team, keeps the CRM accurate and the next step clear without extra admin after every call.

What you get out of it

CRM notes that are actually useful
Every call leaves a record of pain points, objections and agreed next steps on the contact, not a one-line reminder.
Handovers lose nothing
When an account moves to another rep or to onboarding, the history of every conversation is on the contact.
Managers see the pipeline move
Summaries in #sales show what happened on calls today without a status meeting.
Reps get their evenings back
Writing up calls is one of the most skipped sales tasks. Taking it off the list means it is done every time.

How it works

What happens, step by step

When a call ends, your call recorder sends the transcript to ClickRuntime.
AI writes a short summary of the call with the agreed next steps.
ClickRuntime finds the contact in HubSpot by email and adds the summary as a note on their record.
The same summary is posted in your #sales Slack channel.

Before it runs live

Connect HubSpot
Connect Slack, then invite the app to the channel (type /invite @ClickRuntime there)
Paste your automation's link into the other app's webhook settings

What you get

RunsThe moment it happens

Log sales call summaries on the HubSpot contact and in Slackjust nowSucceeded

Slack · #salesCall with ops@northwind.example: wants SSO before Q1 rollout, budget approved. Next: send security doc by Thursday.

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
Change what the AI looks for, or how it writes the result
Add another app, for example also send it to Google Sheets
Combine it with other HubSpot and Slack 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.

call_summary_into_hubspot_and_slack.pyexample

from clickruntime import on_event, credentials, http, ai, notify

HS = "https://api.hubapi.com/crm/v3/objects"

@on_event
def handle(event):
    p = event.json or {}
    summary = ai.generate(["Summarise this sales call in 4 bullets, then list next steps with owners.", (p.get("transcript") or "")[:25000]],
                          max_output_tokens=500).text
    h = {"Authorization": f"Bearer {credentials.secret('HUBSPOT_API_KEY')}"}
    found = http.post(f"{HS}/contacts/search", headers=h, json={"filterGroups": [{"filters": [
        {"propertyName": "email", "operator": "EQ", "value": p.get("email")}]}]}).json().get("results", [])
    if found:
        http.post(f"{HS}/notes", headers=h, json={
            "properties": {"hs_note_body": summary, "hs_timestamp": event.received_at},
            "associations": [{"to": {"id": found[0]["id"]},
                              "types": [{"associationCategory": "HUBSPOT_DEFINED", "associationTypeId": 202}]}]})
    label = p.get("email") if found else f"{p.get('email')} (no HubSpot contact)"
    notify.slack(f"*Call with {label}*\n{summary}", channel="#sales")
    return {"contact_found": bool(found)}

FAQ

Common questions

Where do the transcripts come from?

Your call recorder or dialler sends each transcript to your trigger link when the call ends, with the contact's email address.

What if the contact is not in HubSpot?

The summary is still posted in Slack, marked as having no matching contact, so the rep can create one and paste it in.

Does the note include the full transcript?

No. The note holds the summary and next steps. Keep the full recording in your call tool, where it already lives.

What permissions does it need?

HubSpot contacts read, notes write; Slack chat:write. Nothing else in your accounts is used.

Does it need AI?

Yes. It uses ClickRuntime's built-in AI, so you don't need an OpenAI or Anthropic key. Every plan includes a monthly 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