AI Call Data Processor for Notion - n8n Workflow

This n8n automation is ideal for:

Product Managers and Researchers: Who need structured data from sales conversations about product feedback.
Sales Operations Teams: Seeking to automate the documentation of AI-related opportunities or mentions in sales calls.
Developers and Automation Engineers: Looking for robust n8n templates that handle complex branching logic and database integration.
Users of CallForge or Similar AI Call Analysis Systems: Needing a reliable post-processing n8n workflow step.

This crucial backend n8n workflow acts as the data ingestion layer for the CallForge AI call processing system. After an upstream n8n workflow analyzes a sales call transcript using AI (extracting key data like product feedback and potential AI use cases), this dedicated n8n node setup takes that raw structured output and strategically files it into corresponding Notion databases. The value of this n8n template lies in its efficiency: it eliminates manual data entry, ensures immediate logging of critical sales insights, and uses conditional logic to manage rate limiting and data splitting. Every component of this n8n workflow is designed for stability and high data integrity.

This n8n workflow executes a three-pronged analysis and ingestion process immediately upon being triggered by the main CallForge processor.

1. Workflow Trigger: The process begins with the Execute Workflow n8n trigger, which receives the output payload from the preceding AI processing workflow, including AI analysis data and metadata.


2. Product Feedback Processing: The flow first hits the 'Check if Product Data Found' n8n node. If the AI output contains product feedback items (array length > 0), the workflow pauses for a 3-second wait period (critical for avoiding Notion rate limits). It then uses the 'Split Out Product Data' n8n node to process each piece of feedback individually before creating a new page in the dedicated 'Product Feedback' Notion database.


3. AI Use Case Ingestion: Simultaneously, the 'Check if AI Use Case Data Found' n8n node verifies if an AI use case was identified. If true, a similar 3-second delay is initiated. The data is then ingested into the 'AI use-case database' Notion database, mapping detailed AI requirements (like RAG, Agents, development status) directly to database properties. This is a vital step in this specific n8n workflow.


4. Call Summary Update: A third check confirms if any AI was mentioned on the call. If so, the original Notion call summary page (created by the initial n8n template) is updated using the 'Update Call with AI Data Summary' n8n node, checking the 'AI Related' checkbox and adding the general AI context summary.


5. Completion and Merge: Finally, all successful data ingestion threads are aggregated and merged back into clean output objects, concluding this highly segmented n8n workflow execution.

To deploy this n8n workflow template effectively:

1. Import: Copy the provided JSON code and import it directly into your n8n instance via the 'New' > 'Import from JSON' option.


2. Notion Credentials: You must update the Notion credential configurations in the following three Notion n8n node steps: 'Create Product Data Object1', 'Create Product Feedback Data Object', and 'Update Call with AI Data Summary'. Ensure your Notion API keys have access to the target databases.


3. Database IDs: The Notion n8n node configurations rely on specific database IDs (1775b6e0-c94f-80ac-9885-d9695af5bc89 for AI Use Case and 1375b6e0-c94f-80a8-93c9-c623b76dd14a for Product Feedback). You must replace these placeholder IDs with the actual IDs of your Notion databases.


4. Trigger Setup: This n8n workflow is designed to be executed by another parent workflow. Ensure the calling n8n workflow correctly passes the required input data structure (including AIoutput, metaData, and notionData). The 'Execute Workflow Trigger' is the starting n8n trigger for this specific automation.

Execute Workflow Trigger: The starting point and n8n trigger for this automation. It receives the complex JSON payload containing the AI analysis results from the previous processing n8n workflow.
If Node (Checks): Three conditional n8n node checks ('Check if Product Data Found', 'Check if AI Use Case Data Found', 'Check if AI Mentioned On Call') control the flow. They evaluate if corresponding data elements exist in the AI output, determining which branch of the n8n workflow should proceed.
Wait Node: Used twice ('Wait for rate limiting - AI Use Case' and 'Wait for rate limiting - Product Data') to introduce a 3-second delay. This is a critical component of this n8n template for adherence to external API rate limits, especially Notion.
Split Out Product Data: This n8n node processes the AIoutput.ProductFeedback array. If multiple feedback items are found, this n8n node splits them into separate items so that each item can be logged as its own page in the Notion database.
Notion Node (Create & Update): Used to interface with Notion. Specifically, the 'Create Product Data Object1' and 'Create Product Feedback Data Object' nodes ingest new records, while the 'Update Call with AI Data Summary' n8n node modifies an existing page.
Aggregate Node & Set Node: Used at the end of successful paths to bundle the output data and merge it into a consolidated object, ensuring the subsequent flow maintains the necessary context from this n8n workflow branch.