Turn AI summaries from sales calls into clean Notion records. The flow sorts content into AI use cases, product feedback, and a simple flag for AI mentions on the call. It keeps teams aligned and gives sales and product a single source of truth.

Data arrives from a parent workflow through an Execute Workflow Trigger. Three checks decide what to store: product data, AI use case content, and whether AI was mentioned. Wait steps control write speed to respect rate limits. The flow creates pages in two Notion databases, splits product items into separate entries, bundles records for summaries, merges threads, and updates the call page with a short AI data summary. This structure reduces back and forth and keeps details easy to find.

To run it, you need Notion and access to the databases used for AI use cases, product feedback, and call records. Expect less manual note taking, faster handoffs, and better tracking across calls. Great for sales and RevOps teams that analyze call transcripts and want product insights captured without extra work.

• Executes on data passed from another workflow using Execute Workflow Trigger
• Checks for product data, AI use case content, and AI mention flags with If nodes
• Controls Notion write speed with Wait nodes to avoid rate limits
• Creates Notion pages for AI use cases in a dedicated database
• Splits product items into separate Notion records for clear tracking
• Bundles multiple records into a single summary object with Aggregate nodes
• Merges content threads and prepares a clean payload for updates using Set nodes
• Updates the original call record in Notion with an AI data summary

• Reduce manual logging from 60 minutes to under 5 minutes per call
• Automate 90 percent of repetitive updates to Notion call pages
• Improve data accuracy by 80 percent by removing copy and paste errors
• Handle 3 times more call summaries without adding headcount
• Connect Notion with your AI output so sales and product see the same facts

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Notion. See the Tools Required section above for links to create accounts with these services.
3. In Notion, create or identify three databases: one for AI use cases, one for product feedback, and one for call records. Add properties that match your needs, such as Company, Department, Sentiment, Feedback, and Date.
4. In n8n, open each Notion node and set credentials: double click the node, then on the 'Credential to connect with' dropdown, click 'Create new credential', then follow the on screen instructions to integrate that service.
5. In each Notion node, choose the correct database in the Database field. Match property names to your Notion database properties so titles, multi select fields, and dates map correctly.
6. Review the Wait nodes named Wait for rate limiting. Keep a short delay if you see rate limit errors. If they are set to wait for a webhook, leave them as is and let the flow resume automatically.
7. Check the If nodes for the fields used to detect product data, AI use case data, and AI mentions. Make sure your upstream payload includes these keys.
8. Create a short parent workflow with an Execute Workflow node that calls this workflow. Pass a sample JSON item with metaData, AIoutput, and any product feedback fields so you can test end to end.
9. Run a test from the parent workflow. Confirm new pages appear in the AI use case and Product Feedback databases and that the call page shows the AI data summary.
10. If you get 429 rate limit errors, increase the delay in the Wait nodes. If fields do not save, align property names in the Notion nodes with your database schema.
11. Once tested, enable both workflows. Monitor the first few runs and adjust delays or field mappings as needed.