GONG n8n INTEGRATION: AUTOMATE GONG WITH N8N

This action retrieves multiple user records from your Gong workspace in a single operation, making it ideal for syncing your entire sales team's data or building user directories across systems.

Key parameters:

• Credential to connect with: Select your configured Gong account from the dropdown. This is required for API authentication.
• Resource: Set to "User" to target user data. Selected via dropdown menu.
• Operation: Choose "Get Many" to retrieve multiple records rather than a single entry.
• Return All: Toggle switch (off by default). When disabled, respects the limit you set; enable to fetch every user.
• Limit: Numeric field specifying maximum users to return—defaults to 50. Useful for pagination or testing.
• Filters: Optional section to narrow results based on specific criteria.

Practical use cases:

• Sync all Gong users to your CRM nightly to ensure sales rep records stay current
• Build an internal directory combining Gong user data with Slack profiles
• Generate weekly reports showing active users and their roles
• Audit user access by comparing Gong users against HR system records

Use this action when you need bulk user data for reporting, synchronization, or compliance workflows. It's particularly valuable during onboarding/offboarding automations where you need to track who has Gong access.

This action retrieves detailed information about a specific Gong user, perfect when you need to look up individual team members or pull data for a particular sales rep.

Key parameters:

• Credential to connect with: Dropdown to select your Gong account credential. Required for authentication.
• Resource: Set to "User" via dropdown to specify you're working with user data.
• Operation: Select "Get" to retrieve a single user record rather than multiple.
• User to Get: Combination dropdown allowing you to specify the target user. "From list" mode lets you select from available users directly in the interface.

Practical use cases:

• Fetch a specific rep's details when they're mentioned in a support ticket
• Retrieve user metadata to personalize automated email reports
• Look up manager information for approval workflow routing
• Validate user existence before attempting other Gong operations

This action shines in conditional workflows where you need to check or retrieve data about one specific person. Combine it with data from other systems—like pulling the Gong profile for whoever just closed a deal in your CRM.

This action fetches multiple call records from Gong, enabling bulk retrieval of your team's conversation data for analysis, reporting, or synchronization with external systems.

Key parameters:

• Credential to connect with: Select your Gong account credential from the dropdown. Required.
• Resource: Set to "Call" to indicate you're retrieving call data.
• Operation: "Get Many" retrieves multiple call records in one execution.
• Return All: Toggle (off by default). Enable to fetch all calls matching your criteria; disable to respect the limit.
• Limit: Numeric input defaulting to 50. Controls maximum calls returned when "Return All" is off.
• Filters: Expandable section for adding criteria to narrow down which calls are retrieved (by date range, participants, etc.).
• Options: Additional configuration for customizing API request behavior or response handling.

Practical use cases:

• Export weekly calls to a Google Sheet for sales management review
• Feed call data into a data warehouse for custom BI dashboards
• Identify calls from specific time periods for training material creation
• Build activity reports combining call volume with outcome data from your CRM

This is your go-to action for call analytics workflows. The Filters section is particularly powerful—use it to retrieve only calls from the past week, calls involving specific reps, or calls meeting other criteria relevant to your automation.

This action retrieves detailed information about a single specific call, giving you access to metadata, participants, and other call-level data for individual conversation records.

Key parameters:

• Credential to connect with: Dropdown for selecting your authenticated Gong account. Required.
• Resource: Set to "Call" via dropdown to target call data.
• Operation: "Get" retrieves a single call record based on your specification.
• Call to Get: Specifies which call to retrieve. Use "From list" to select from available calls or provide a call ID dynamically from previous workflow steps.
• Options: Expandable section for additional parameters to customize the request or response.

Practical use cases:

• Retrieve full call details when a deal closes to log in your CRM
• Fetch call metadata to attach to support tickets referencing specific conversations
• Pull individual call data for automated post-call summary emails
• Validate call existence before triggering downstream workflows

Use this action when your workflow centers on a specific call—perhaps triggered by an event in another system that references a Gong call ID. It's the precision tool compared to "Get Many Call's" bulk approach.