Your team already runs its automations in n8n because workflows are visible, integrations and credentials stay managed in one place, and each step is easy to inspect or adapt. A Gong follow-up belongs there too—but n8n cannot start the workflow when a new Gong call becomes available on its own.
Glean supplies the missing trigger and permission-aware context. When a customer call is indexed, it automatically starts the n8n workflow, which summarizes the conversation, records it only when one Salesforce account matches, and alerts the reviewed Slack destination. The workflow stays in the automation platform your team already uses.
Scaffold the workflow
npx -y tiged@2.12.8 --mode=git gleanwork/glean-cookbook/recipes/gong-call-follow-up-n8n gong-call-follow-up-n8nInstall the Glean n8n nodes
Settings, Community nodes, Install, then @gleanwork/n8n-nodes-gleanclient@0.4.1; verified end to end on n8n 2.35. It ships a Trigger and a Search action and no Chat node, so summarization is an HTTP Request. n8n Cloud works as shipped; self-hosted needs WEBHOOK_URL set to its public origin.
Import the workflow
In n8n, use Workflows, Import from URL with the raw workflow.json link. If n8n cannot reach GitHub, copy and paste the workflow onto an empty canvas. Import from File uses the browser's filesystem, so it cannot see files scaffolded on a remote host. Confirm that ten nodes and the Start here note appear.
Attach credentials
A TRIGGERS-scoped Glean Trigger credential for the trigger, a SEARCH+CHAT-scoped Glean Client credential for Search and Chat, plus Salesforce and Slack. The trigger matches the Glean credential owner's calls; there is no user to pick.
Configure Glean Chat and Slack routing
Replace the placeholder backend URL in the Glean Chat node. Then configure either one reviewed central Slack channel or an Account-to-channel map in Resolve channel. n8n Variables may override these values but are not required.
Verify the workflow with no credentials
Verifies the imported workflow, account resolution, Salesforce activity, and Slack routing using recorded data.
cd gong-call-follow-up-n8n && npm run verify:fixturePublish the workflow
Publish in n8n. The Glean Trigger node registers n8n's production webhook and stores the one-time signing secret in workflow static data.
Verify with a real Gong call
Complete a short call with yourself as a participant. Confirm one execution, one completed Salesforce activity on the matched Account, and one Slack post, and read the summary before widening the audience.
Writes happen only after exactly one Salesforce Account matches; ambiguity halts the run rather than choosing.
Summaries come from the call and permission-aware Glean results. The prompt forbids unsupported commitments, dates, and pricing.
Glean Chat identifies the customer from the call context. The workflow proceeds only when Salesforce returns one matching Account; otherwise it stops for manual resolution.
- Create owner-assigned Salesforce follow-up tasks from explicit call action items, so a commitment made on the call has an owner.
- Send a daily digest of completed and unresolved call follow-ups, so the account team sees the backlog rather than individual posts.
- Route unresolved accounts to a human-owned queue instead of stopping, once someone owns that review path.
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.