Every 15 minutes
Post an AI summary of each Gong call to Slack
Shortly after a call is recorded, the channel gets a summary with the action items.
- Runs
- Every 15 minutes
- Apps
- Gong
- AI
- Yes, uses the built-in AI allowance
- Access
- technical admin key (read)
Send this to your assistant
Create a ClickRuntime automation: every 15 minutes, check Gong for newly processed calls, summarise each one in 5 bullets with next steps and owners, and post it to #sales-calls in Slack.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
A sales manager with eight reps can listen to maybe two of the thirty calls recorded in Gong each day. Everyone else is guessed at from CRM notes that are three words long: "good call, send pricing". Objections that keep coming up, a competitor mentioned in passing and a promised follow-up for Thursday all sit inside transcripts that nobody reads, and the rep moves on to the next call.
Every 15 minutes, ClickRuntime checks Gong for calls recorded since the last run, fetches each transcript and uses its built-in AI to write a short summary with next steps. That summary is posted to the Slack channel you pick, one message per call, shortly after the call ends and is processed.
Revenue teams often send it to a shared deals channel so the whole team learns from every conversation, not just their own.
What you get out of it
Managers see every call, not a sample
Each recorded call gets a short written summary in Slack, so a manager can skim thirty calls over coffee. Coaching stops depending on which two calls happened to get listened to.
Follow-ups stop disappearing
Next steps are pulled out of the transcript and posted where the team works. A promised pricing sheet or a security questionnaire is visible the same afternoon, which cuts deals that stall from a forgotten promise.
Objections get noticed across reps
When three summaries in one week mention the same competitor, someone in the channel sees the pattern. Product and marketing can react in days rather than waiting for a quarterly win-loss review.
Newer reps learn from the channel
A stream of short call summaries shows what good discovery and handling look like in practice. New hires pick up phrasing and questions without needing access to hours of recordings.
CRM notes get a reliable source
Reps can paste the posted summary into the deal record instead of writing from memory. Records become more accurate, and pipeline reviews rely on what was actually said instead of on memory.
How it works
What happens, step by step
Every 15 minutes, ClickRuntime checks Gong for calls recorded since its last check, so each call is handled once.
For each new call it fetches the full transcript.
AI reads the transcript and writes a five-bullet summary followed by next steps with owners.
The summary is posted to #sales-calls in Slack with the call title and a link to the recording in Gong.
Before it runs live
- Connect Gong
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 Gong steps into one automation
Under the hood
The code that runs this automation
from datetime import datetime, timezone
from clickruntime import on_trigger, state_initializer, credentials, notify, http, state, ai, report_fetched
@state_initializer
def init():
state.set("since", datetime.now(timezone.utc).isoformat())
@on_trigger
def run(event):
auth = (credentials.secret("GONG_ACCESS_KEY"), credentials.secret("GONG_ACCESS_SECRET"))
since = state.get("since")
now = datetime.now(timezone.utc).isoformat()
resp = http.get("https://api.gong.io/v2/calls", auth=auth, params={"fromDateTime": since})
calls = resp.json().get("calls", []) if resp.status_code != 404 else []
report_fetched(len(calls))
if not calls:
return {"posted": 0}
for call in calls:
tr = http.post("https://api.gong.io/v2/calls/transcript", auth=auth,
json={"filter": {"callIds": [call["id"]]}}).json()["callTranscripts"][0]
text = " ".join(s["text"] for part in tr["transcript"] for s in part["sentences"])
summary = ai.generate(f"Summarise this sales call in 5 bullets, then list next steps with owners.\n\n{text[:60000]}",
max_output_tokens=600).text
notify.slack(f"*{call['title']}*\n{summary}\n{call['url']}", channel="#sales-calls")
state.set("since", now)
return {"posted": len(calls)}FAQ
Common questions
How soon after a call does the summary appear?
Can summaries go to different channels per team?
Will it summarize calls that have no transcript?
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 a morning digest of yesterday's Gong calls
One email each morning covers every call from the day before.
See how it worksEmail weekly call activity per rep
Every Friday I see how many calls each rep had and how long they talked.
See how it worksLabel new emails automatically
New mail is sorted into labels like Inquiry, Invoice and Newsletter within minutes of arriving.
See how it worksKeep exploring
Set up “Post an AI summary of each Gong call to Slack” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
