AI Sales Call Insight Processor for Notion Databases - n8n Workflow

Sales Operations Specialists: Seeking to automate CRM data enrichment based on call intelligence.
Revenue Enablement Teams: Who need structured data on objections and competitors for training materials.
n8n Developers: Looking for advanced examples of conditional logic, batch processing, and rate limiting in an n8n workflow.
Product Managers: Tracking feature requests, use cases, and integration requirements mentioned in sales conversations.

Sales calls generate massive amounts of unstructured data that are critical for product development, marketing, and sales training. This n8n workflow, part of the larger 'CallForge' solution, serves as the central data processor. It receives rich AI-generated summaries from a previous n8n workflow step (likely processing a Gong or similar recording) and intelligently distributes this information across specialized Notion databases.

By leveraging conditional checks and batch processing via the Split Out n8n node, this n8n templates ensures that only relevant data (such as competitor mentions or newly discovered use cases) is created as new, linked pages in your Notion workspace. This automation eliminates manual data entry, turning raw AI output into actionable, structured sales intelligence within Notion.

This highly specialized n8n workflow functions as a data sink, ensuring that complex AI output is correctly formatted and inserted into multiple Notion databases while adhering to API limitations.

1. Trigger and Input: The n8n workflow starts with the Execute Workflow Trigger n8n node, which receives structured JSON data, including the core call metadata (notionData) and the analyzed AI results (AIoutput).


2. Core Update: The first action updates the primary Notion Call object with essential data: call summary, next steps, sentiment, and customer pain points.


3. Conditional Objection Processing: The flow checks if an objection was found. If so, it updates the main Notion call page with the objection summary. Crucially, it uses the Split Out n8n node to isolate individual objection tags, bundles them, and uses an HTTP Request n8n node to patch the multi-select property on the Notion page, ensuring rate limits are managed via Wait nodes.


4. Conditional Integration Processing: The workflow checks for integration mentions. If the AIoutput.Integrations array has data, it splits the items and uses a Notion n8n node (Create Integrations) to create new, linked pages in the dedicated Integrations Database.


5. Conditional Competitor Processing: Similarly, the flow checks for competitor data. If found, it uses the Split Out n8n node to handle multiple competitors and creates separate pages in the Competitors Database using the Create Competitors in DB Notion n8n node, linking back to the source call summary.


6. Conditional Use Case Processing: Finally, it checks for documented use cases. If present, the workflow splits the use cases and creates new entries in the Use Cases Notion database.

To set up this powerful n8n workflow, follow these steps:

1. Import: Copy the provided n8n workflow JSON code and paste it into your n8n canvas using the 'Import from JSON' option.


2. Notion Credentials: You need active Notion API credentials. This n8n templates uses credentials named 'Notion david-internal' and 'Angelbot Notion'. Replace these with your authenticated Notion API key.


3. Database IDs: Configure the Notion n8n node parameters with the correct database IDs corresponding to your Notion workspace for:

1. Connecting Workflows: Since this n8n workflow uses an Execute Workflow Trigger n8n node, ensure that the preceding workflow (the one generating the AI analysis) is configured to successfully trigger this workflow and pass the required structured JSON inputs (notionData and AIoutput).


2. Activation: Once configured, activate the n8n workflow.

This n8n workflow relies on core logic and data manipulation nodes to handle structured AI output:

Execute Workflow Trigger (Trigger): Acts as the trigger, receiving the structured data payload (AI analysis results and Notion page metadata) from an upstream n8n workflow.
Notion (Update Call object with AI data): Updates the primary sales call page with high-level summaries, next steps, and sentiment using the update operation.
If (Check nodes): Multiple If n8n nodes (Check if objection found, Check if Competitor Data Found, etc.) control the flow, ensuring subsequent operations only run if the corresponding AI data (e.g., competitor list length > 0) is present.
Split Out (Split Out data): Essential for handling arrays of structured data (like multiple Competitors, Integrations, or Objection Tags). This n8n node breaks the array into separate items, allowing the Notion nodes to create individual database pages for each entry.
Wait (Rate Limiting): Critical Wait n8n nodes are placed before sequences of Notion API calls (like Wait for rate limiting - Objection) to prevent hitting Notion's strict API rate limits during batch page creation.
HTTP Request (Add Objection Tag to Notion): Used specifically to perform a PATCH request to the Notion API to update multi-select fields (Objections) which often require complex JSON structuring not easily handled by the standard Notion n8n node property editor.