Resources · n8n integration

Gong n8n integrationAutomate Gong with n8n.

Where does a call go once the deal moves on? The Gong n8n integration reads that history back out: 4 operations across 2 resources, calls and users, from a single call record to a filtered list of workspace users. Gong has no trigger node in n8n, so a Schedule Trigger opens the run.

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Gong n8n integration actually do?

The Gong node ships with n8n and talks to the Gong API. It covers 2 resources, Call and User, with 4 operations in total: read one call, list calls, read one user, list users. Anything the Gong API offers beyond those 4 goes through the HTTP Request node, which reuses the same credential through its predefined authentication.

So think of the node as the reading end of the pipe. It brings call and user records into a workflow, and the nodes after it decide where those records land.

The weekly export is the plainest use of it. A Schedule Trigger fires every Monday, Get Many on the Call resource uses the After and Before filters to cover the last 7 days, and each call becomes a row in Google Sheets. Leave Return All off and the run stops at Limit, which is usually what you want while you are still testing the sheet layout.

A coaching queue works on the same operation with a different filter. The Organizer filter returns only the calls hosted by one person, so a manager gets a Slack message listing that rep's week before the one-to-one. Tick Participants under Call Data to Include and the participant information travels with each call, which saves a second lookup.

The User resource covers the other half: keeping a local copy of who is in the Gong workspace. Get Many with Created After returns the accounts created since the last run, and an insert into Postgres keeps a table you can join against your CRM without calling Gong every time.

Two practical points before you build. Return All chains the API pages until everything is in, so a full history export needs it on, while a daily digest rarely does. And the media option on a single call returns audio and video URLs that stay available for 8 hours, which means a workflow that stores the link for later needs to fetch the file inside that window, not the link.

For the rest of the Gong API, HTTP Request is the way through: same credential, endpoint of your choice. If you are still weighing the platform itself, the n8n review goes through the hosting and pricing model, and the n8n training covers expressions and pagination in detail.

Connect

How do you connect Gong to n8n?

  1. 01

    Choose an authentication method

    The Gong node accepts two credential types: Access Token and OAuth2. Pick one before you start building, because the credential you select is the one every Gong node in the workflow points to. A credential in n8n is the stored set of values that proves who is calling the API, created once in the Credentials menu and reused everywhere after that.

  2. 02

    Create the credential in n8n

    Open the Credentials menu, search for Gong, and fill in the values from your Gong account for the type you chose. Save it and it becomes available in the credential dropdown of every Gong node, on n8n Cloud or on a self-hosted instance. The same credential also works from an HTTP Request node through its predefined authentication, which is how you reach Gong endpoints outside the 4 operations.

  3. 03

    Run one operation to check the wiring

    Drop a Gong node on the canvas, select the Call resource and Get Many, leave Return All off, and execute the node on its own. A short list back means the credential works. Then add the filters you need, since it is much easier to see what a field does on a small result set than on a full export.

Actions

What can the Gong node do?

The Gong node exposes 4 operations across 2 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceGetGet Many
Call✓✓
User✓✓

Call

2 operations
01

Get call

call.get

What you see in n8n

Notes & use cases

Retrieves the data of one call and returns it as a single item in the workflow.

Key parameters

  • Call to Get: required, identifies which call to read. When the identifier comes from an earlier node, point the field at it with an expression like {{ $json.field }}.
  • Call Data to Include: an option that decides what travels with the call. Choose among Transcript, Participants, Brief, Keypoints, Highlights, Outline, Structure, Topics, Trackers, Action Items, Outcome, Comments, and Audio and Video URLs, whose links stay available for 8 hours.
Use cases
a deal review that reads one call, asks for Brief and Keypoints, and writes them next to the opportunity.
02

Get many calls

call.getAll

What you see in n8n

Notes & use cases

Returns a list of calls, one item per call, with filters that narrow the list before it reaches the next node.

Key parameters

  • Return All: on, n8n walks the API pages until every matching call is in; off, Limit caps how many come back.
  • After and Before: the date and time bounds of the window, in the format 2018-02-18T08:00:00Z. After is inclusive, Before excludes its own timestamp.
  • Workspace ID, Call IDs, Organizer: restrict to one workspace, to a comma separated set of call IDs, or to the calls hosted by one user.
Use cases
the Monday export of last week's calls into a sheet.

User

2 operations
03

Get user

user.get

What you see in n8n

Notes & use cases

Reads the data of one Gong user and hands it to the next node. It is the lookup you place after a call, when the workflow has a user reference in hand and needs the person behind it.

Key parameters

  • User to Get: the only required field, and the only one this operation takes. It identifies the user to read, either picked in the node or passed in with an expression such as {{ $json.field }}.
Use cases
enriching a call notification so the message names the host instead of showing a bare identifier.
04

Get many users

user.getAll

What you see in n8n

Notes & use cases

Lists the users of the Gong workspace, one item each, with three filters to cut the list down.

Key parameters

  • Created After and Created Before: keep only accounts created at or after, and before, the timestamps you give, again as 2018-02-18T02:30:00-07:00 or its UTC form.
  • User IDs: a comma separated set of Gong numeric user identifiers, up to 20 digits each, when you already know who you are after.
  • Return All and Limit: full workspace, or a capped batch.
Use cases
a nightly sync that adds newly created Gong accounts to an internal directory.
Need help

Need help automating Gong with n8n?

A person reads every message.

FAQ

Gong and n8n, the questions that come up next

01Is the Gong n8n integration free to use?
Yes on the n8n side. The Gong node ships with n8n, so there is nothing to install and nothing extra to pay for the node itself, whether you run n8n Cloud or a self-hosted Community Edition instance under the Sustainable Use licence. A workflow behaves the same way in both. What you pay Gong for your own account is a separate matter and depends on your agreement with them. The only thing to plan for on the n8n side is where the data goes afterwards, since a sheet, a database or a messaging app each come with their own node and their own credential.
02What credentials does the Gong node need?
The node accepts two authentication methods: Access Token and OAuth2. Both are set up once in the Credentials menu of n8n and then reused across every workflow that touches Gong, which means you do not re-enter anything when you add a second or third Gong node. Once saved, the credential shows up in the node's dropdown list. It also serves the HTTP Request node through its predefined authentication, so a call to a Gong endpoint outside the 4 node operations runs with the same setup rather than a second set of keys.
03What are the limits of the Gong node in n8n?
The catalogue holds 4 operations over 2 resources, and all of them retrieve data: one call, many calls, one user, many users. Anything in the Gong API beyond those operations goes through the HTTP Request node, reusing the Gong credential via its predefined authentication. On the list operations, leaving Return All off means the run stops at Limit, so a full export needs it on. And on a single call, the audio and video URLs returned by the media option stay available for 8 hours, which matters if a workflow stores links instead of files.
04Can a workflow react to a new Gong call in real time?
Not through a Gong trigger, because the catalogue has no trigger node for this tool. A workflow starts somewhere else: a Schedule Trigger running at a fixed interval, an n8n Webhook called by a third-party service, or the trigger of another app already in your setup. The usual pattern is a Schedule Trigger plus Get Many on calls, with the After filter set to the start of the period you want, so each run picks up what appeared since the previous one. The gap between a call ending and your workflow seeing it is whatever interval you set.
05n8n or Make for Gong?
It depends on where you want the automation to live. Make is hosted by Make, with no self-hosting option, and it bills per operation, so a high-volume call export has a cost that scales with the number of items. n8n runs on n8n Cloud or on your own server through Docker or npm, and a workflow is identical either way, which matters when call data has to stay on infrastructure you control. Both give you a visual canvas. Judge on hosting, data control, the cost model and how comfortable your team is with expressions.