Save Gong call notes to a Notion database for the sales team

Every call Gong processes becomes a new item in a Notion database you pick, so your sales team can look back over customer conversations in the workspace they already use for notes.

Gong

Notion

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 1.8k sites Free to import

The Save Gong call notes to a Notion database for the sales team workflow on the FlowMattic canvas, with 2 steps across Gong, Notion — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Gong records and processes your sales calls, but plenty of reps plan their week in Notion and rarely open the call library. Copying each call into a shared database by hand gets skipped after the first busy week. This workflow adds the entry for you each time a call is ready.

The Gong trigger fires when Gong finishes processing a new call. FlowMattic receives the call data Gong sends and makes it available to map. The Notion step then creates a database item, and you decide which call details fill which properties, such as a title, a date or a link back to the recording.

Which call fields you get depends on what Gong includes for that call, so run one call through after import and check the captured data before you map it. Every call creates its own Notion item; the workflow does not group calls by account or deal. Task History lists each run, so you can see what reached Notion and spot a step that returned an error.

Call log for a small sales team

Each processed Gong call appears as a row in a team Notion database, where reps sort by date and open the ones they need before a follow-up.

Onboarding new reps

A new hire browses the Notion database of recent calls to hear how the team handles discovery and demos, without needing their own way around Gong.

Sharing calls with product and marketing

Colleagues who live in Notion see which customer calls happened this week and follow the link to the recording when a topic matters to them.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Gong New Call
Fires when Gong has processed a new call. The call data Gong sends with the event is captured so you can map it into Notion.
Step 2Action
Notion Create Database Item
Adds an item to whichever Notion database you select. Connect your Notion account, make sure FlowMattic can reach that database, and map call details to its properties.

What you need

FlowMatticCore
Gong AccountAccount
Notion AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Set up the Notion database with its properties before you import, then match each one to a Gong call field in the Create Database Item step.
Add a Filter after the trigger if only some calls belong in Notion, for example ones where a call field you saw in a test run contains a word your team uses for demos.
Run one real call through Gong after import, then open Task History to see which call fields arrived before you finish the mapping.

Questions about this workflow

Will past Gong calls be copied into Notion?

No. The trigger reacts to calls Gong processes after the workflow is on. Earlier calls stay in Gong unless you add them to Notion another way.

Does the Notion item include the full Gong transcript?

The template maps only what Gong sends with the new call event, and you choose the fields. Check a test run in Task History to see what data is there before you promise anything to the team.

Can the Gong calls go to an existing Notion database?

Yes. Pick that database in the Notion step after you connect your account, and make sure it is shared with the connection so FlowMattic can add items.

What if the same Gong call is processed twice?

Each trigger event creates a fresh Notion item. The Create Database Item step does not check for an existing entry, so a repeat event would add a second one.