Automate Gong call follow-up with Glean Triggers in n8n

Use the Glean Trigger node in n8n to summarize a Gong call, log it in Salesforce, and post a Slack heads-up.

~1.5 hrAdvanced

Problem

Important follow-up gets lost after customer calls—not because the information is missing, but because it is scattered across Gong, Salesforce, and Slack.

This recipe connects those systems in n8n. When a new Gong call is indexed, Glean finds permission-aware context and summarizes it, Salesforce gets an activity only when one account matches, and Slack receives a focused update for the right audience.

Architecture

GongA new indexed call involving you

Glean TriggerDelivers the call securely to n8n

n8nFinds context, writes the summary, and matches one account

Salesforce + SlackRecords the activity and shares the right update

Prerequisites

Glean Triggers enabled with the Gong preset available, Gong calls indexed, and credentials scoped for Triggers, Search, and Chat

A publicly reachable n8n instance, or a local one exposed with npx n8n start --tunnel

Permission to install the Glean n8n community nodes

Salesforce and Slack credentials with the required write access

Node 20+

Steps

Choose n8n hosting before scaffolding

Choose n8n Cloud or local/self-hosted n8n before downloading anything. Cloud is public by default. Local/self-hosted needs a public HTTPS webhook origin—use n8n's development `--tunnel`, Cloudflare Tunnel, or another ingress, and keep it available before publishing.

Scaffold the workflow

npx -y tiged@2.12.8 --mode=git gleanwork/glean-cookbook/recipes/gong-call-follow-up-n8n gong-call-follow-up-n8n

Resolve the Glean backend

Run the cookbook resolver with the work email. It may see a legacy frontend address such as `*.askscio.com`, but it returns the API backend `https://<instance>-be.glean.com`. Use that result for Glean Chat; do not paste the discovery address into the workflow.

cd gong-call-follow-up-n8n && node <cookbook-plugin-root>/scripts/resolve-backend.mjs "<work-email>"

Install the Glean n8n nodes

In n8n, open Settings → Community nodes → Install and add `@gleanwork/n8n-nodes-gleanclient@0.4.2`. It provides the Trigger and Search nodes; the workflow uses an HTTP Request for Chat. Cloud works as shipped. For self-hosted n8n, set the webhook base to your public origin or start the development tunnel.

Import the workflow

In n8n, choose Workflows → Import from File and select the scaffolded `workflow.json`; this is the route that keeps your local edits. Import from URL always fetches the untouched GitHub file. If your browser cannot see the scaffolded file, copy and paste it onto a blank canvas. Confirm that the ten nodes and Start here note appear.

Attach credentials

Attach a Glean Trigger credential with `TRIGGERS`, a Glean Client credential with `SEARCH` and `CHAT`, plus your Salesforce and Slack credentials. The trigger follows the Glean credential owner; there is no separate user to select.

Configure Glean Chat and Slack routing

Set the Glean Chat node to the backend returned by the resolver, then choose one reviewed Slack channel or an Account-to-channel map. n8n Variables can hold the backend and routing values, but they are optional.

Verify the workflow with no credentials

Run the fixture verifier against recorded data. If you edited the local workflow.json, run `npm run verify:config` too. That command cannot see values entered in the n8n UI or stored in n8n Variables, so verify those configurations inside n8n before publishing.

cd gong-call-follow-up-n8n && npm run verify:fixture

Publish the workflow

Publish the workflow in n8n. The Glean Trigger node registers the production webhook and stores the signing secret used to verify deliveries.

Verify with a real Gong call

Make a short Gong call with yourself as a participant. Confirm one execution, one completed Salesforce activity on the matched Account, and one Slack post. Read the summary before widening the audience.

One account or no write

The workflow writes only after exactly one Salesforce Account matches. Ambiguity stops the run instead of choosing for you.

Evidence before summary

The summary uses the call and permission-aware Glean results. Unsupported commitments, dates, and pricing stay out.

Account matching still needs a review path

Glean Chat proposes the customer from the call context, but Salesforce remains the authority. The workflow continues only when exactly one Account matches; otherwise it stops for resolution.

Take it further

Create Salesforce follow-up tasks from explicit call action items, so every commitment has an owner.
Send a daily digest of completed and unresolved follow-ups instead of one Slack post per call.
Route unresolved accounts to a human review queue once that ownership path is in place.

Try it

Finish a Gong call involving the trigger owner and a customer with a matching Salesforce Account

The workflow summarizes the call, creates one completed Salesforce activity on the matched Account, and posts the summary and source link to the configured Slack destination.

Choose your tool
Install the plugin
1
```
claude plugin marketplace add gleanwork/glean-cookbook
```
2
```
claude plugin install cookbook@glean-cookbook
```
Run the recipe
```
/cookbook:gong-call-follow-up-n8n
```
Run /reload-plugins to pick it up without restarting.

View source

Runs the recipe through the Glean cookbook plugin.

Auth

The host signs in with Glean OAuth. Do not mint an API token for this recipe. Resolve the server URL first if a setup command asks for it.

At a glance

SurfacesPlatform API, Client API

StatusShowcase

Time~1.5 hr

Required scopes

TRIGGERSSEARCHCHAT