Turn sales call recordings into clear notes your team can use. The flow collects new calls, writes a parent record in Notion, and keeps everyone updated in Slack. It fits sales and RevOps teams that want fast summaries and a single place to review calls.

A parent workflow starts the job using an execute workflow trigger. Older call IDs are pulled from Notion, then a compare step filters out any call that was already processed. The system posts a start message in Slack, merges that thread info with the new calls, and loops through each one. For every call, it creates a Notion page with date, link, company, owner, and title, then sends the call plus the Notion page ID into an AI subworkflow. Slack progress updates after each call, and a final message posts when the job is done. The loop design lets you rerun safely if a step fails and helps with Notion rate limits.

Set up needs a Notion database and a Slack channel. Map the Notion fields, choose your Slack channel, and confirm the unique call ID used for filtering. Expect faster handoffs, fewer missed notes, and a clean audit trail in Notion. Teams that review many calls or want reliable summaries gain the most value.

• Execute Workflow Trigger accepts batched calls from a parent job for hands off starts.
• Compare Datasets filters out calls already stored in Notion to avoid duplicates.
• Notion page creation maps fields like title, call date, recording URL, company, owner, and contact name.
• Slack start, progress, and completion messages keep the team updated in one thread.
• Loop Over Calls with a noOp step supports safe iteration and easy reruns after errors.
• Merge and Aggregate nodes bundle Slack thread data with call items for accurate updates.
• Execute subworkflow sends the call and parent Notion page ID to an AI processor.
• Resilience against rate limits by creating pages one by one and updating progress as it runs.

• Reduce manual call notes from 30 minutes to 5 minutes per call
• Streamline review by filtering out processed calls, cutting rework by about 70 percent
• Improve data quality by using a single Notion template for every call
• Handle up to 10 times more calls with loop and resume friendly design
• Connect Slack and Notion so sales and ops stay aligned in real time
• Avoid duplicate processing with near 100 percent ID matching

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 Slack and Notion. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, double click the Notion node named Create Notion DB Page, choose Create new credential, then follow the on screen steps to connect your Notion account. Make sure your Notion database is shared with the integration.
4. In the n8n credentials manager, double click each Slack node, choose Create new credential, then follow the on screen steps to authorize Slack. Select the workspace and grant permission to post messages.
5. In Notion, create or pick a database with these properties: Title, Call Date as date, Recording URL as url, Company as rich text, Call Owner as rich text, and Contact Name as rich text. Copy the database URL to capture the database ID.
6. Open the Create Notion DB Page node and set the Database ID. Map the title to metaData.title, the Call Date to metaData.started, and the Recording URL to metaData.url. Map the other fields to your input data as needed.
7. Open the Get all older Calls node and set the same Notion database so the workflow can read existing pages. Confirm it returns the records you expect.
8. Open the Only Process New Calls node and set the comparison fields. Make sure the unique call ID from your incoming data is compared to the correct property from Notion so duplicates are skipped.
9. Configure Slack nodes: in Post Slack Receipt choose the channel for the start message. In Update Slack Progress keep the same channel and ensure the message timestamp from the first Slack step is passed in. In Post Completed Calls Message select the channel for the final summary.
10. Prepare a small parent workflow for testing. Add an Execute Workflow node that calls this workflow and passes a few call items with metaData.title, metaData.started, metaData.url, and a unique call ID. Run it and watch Slack for the start, progress, and done messages.
11. Validate results in Notion. Confirm each new call has its own page with the correct fields. If you hit rate limits or see duplicates, reduce batch size in the loop and recheck the ID mapping in the compare step.