CallForge - AI Gong Sales Call Processing Workflow Automate your Gong.io sales call analysis with AI-driven insights, real-time tracking, and structured CRM integration. Who is This For? This workflow is designed for: ✅ Sales teams looking to automate sales call processing. ✅ Revenue operations (RevOps) professionals managing high volumes of call data. ✅ AI-driven sales intelligence teams using Gong.io for data-driven insights. What Problem Does This Workflow Solve? Manually managing and analyzing large volumes of Gong call data is time-consuming and error-prone. With CallForge, you can: ✔ Automate call processing to scale AI-driven insights. ✔ Integrate with Notion to track and organize sales call data efficiently. ✔ Get real-time Slack updates to stay informed on call processing progress. ✔ Handle API failures gracefully, allowing easy reruns if a rate limit is hit. ✔ Ensure AI-ready analysis, feeding structured call data into an AI-powered system. What This Workflow Does 1. Triggers on New Gong Calls Captures new Gong calls and retrieves metadata, call summaries, and participant details. 2.
Tags
NotionSlackRelated workflows
See all Notion→Route workflow error incidents to Slack alerts with a Notion incident log
Quick overview This workflow captures n8n workflow execution errors, classifies and deduplicates them, logs incidents to a Notion database, and routes high-severity alerts to a Slack channel, with an optional daily Slack digest of open incidents. How it works Triggers when an n8n workflow execution fails via the built-in Error Trigger. Normalizes the error payload and extracts key metadata like workflow, execution, node, and stack details. Classifies the error into a category, severity, and suggested fix using rule-based text matching. Builds an incident fingerprint and formatted Slack message, then searches a Notion database for an existing incident with the same fingerprint. If a matching Notion incident exists, it updates the page’s last-seen timestamp, severity, suggested fix, and occurrence count and optionally posts a repeated Slack alert based on the minimum severity threshold. If no incident exists, it creates a new Notion incident page and posts a Slack alert only when the severity meets or exceeds the configured threshold. Runs daily on a schedule, fetches unresolved incidents from Notion, and posts a summary digest to the same Slack channel when any open incidents exist.
Check To Do on Notion and send message on Slack
This workflow allows you to check the To-Do list on Notion and send a message on Slack. Prerequisites Create a Notion page similar to this page. Create credentials for Notion by following the instructions mentioned in the documentation. Follow the steps mentioned in the documentation to create credentials for Slack. Cron node: This node triggers the workflow every day. Notion node: This node fetches all the tasks from Notion. IF node: This node checks if the task is assigned to a particular user. Create a Direct Message: This node will create a direct message channel with the user. Send a Direct Message: This node will send the to-do lists in the direct message. NoOp: This node is connected to the false output of the IF node. If the condition is false, no further action will be taken.
Report number of weekly created records in an app
This template shows how you can create reports on data in an app and share a summary in another app. Specifically, this example checks a Notion database for new submissions, filters for submissions with a specific tag, and then sends a Slack message with the number created this week. Setup instructions are located inside the workflow template.