← All N8N workflows
Automation & utilitiesAggregateExecute Workflow TriggerHTTP RequestIfNotion

Integration Data Processing

Configured with Aggregate, Execute Workflow Trigger, HTTP Request, Notion, and additional nodes. Review the connections and setup before adapting this template.

Workflow preview
RoutingCheck if CompetitorData FoundIfRoutingCheck if IntegrationData FoundIfTriggerExecute WorkflowTriggerExecute Workflow TriggerRoutingCheck if objectionfoundIfIntegrationCreate Competitors inDBNotionIntegrationCreate IntegrationsNotionIntegrationUpdate Call withObjection SummaryNotionRoutingCheck for use casesIfIntegrationUpdate Notion Callobject with AI dataNotionTransformSplit Out allobjectionsSplit OutTransformFormat Tag Data fornotionEdit FieldsTransformBundle all TagsAggregateWeb / APIAdd Objection Tag toNotionHTTP RequestWaitWait for rate limitingagainWaitTransformMerge Objection ThreadsEdit FieldsWaitWait for rate limiting- IntegrationWaitTransformSplit Out IntegrationdataSplit OutTransformBundle Integration Datato 1 objectAggregateTransformMerge IntegrationThreadEdit FieldsWaitWait for rate limiting- CompetitorsWaitWaitWait for rate limiting- ObjectionWaitWaitWait for rate limiting- Use CasesWaitTransformSplit Out Use CasesSplit OutIntegrationCreate Use CasesNotionTransformBundle Use Case Data to1 objectAggregateTransformBundle Competitor Datato 1 objectAggregateTransformSplit Out CompetitorDataSplit OutTransformGet AI Response -CompetitorsEdit FieldsTransformMerge Competitor ThreadEdit FieldsTransformMerge Use Case ThreadEdit Fields

Node categories in this workflow

  • Routing
  • Trigger
  • Integration
  • Transform
  • Web / API
  • Wait

Icons describe general node roles, inferred from node types. Inspect the parameters for the configured action.

Drag to pan; use + and − to zoom. Reconstructed from the exported node positions; nothing runs here. Dashed lines represent non-main connections. Full node names and notes appear below.

How it works

The exported workflow contains the following configured nodes. Their connections are shown above; inspect the JSON for the complete logic, expressions, and external actions.

Workflow node names, types, and operations
NodeCategoryTypeOperation
Check if Competitor Data FoundRoutingIfSee node parameters
Check if Integration Data FoundRoutingIfSee node parameters
Execute Workflow TriggerTriggerExecute Workflow TriggerSee node parameters
Check if objection foundRoutingIfSee node parameters
Create Competitors in DBIntegrationNotiondatabasePage
Create IntegrationsIntegrationNotiondatabasePage
Update Call with Objection SummaryIntegrationNotiondatabasePage / update
Check for use casesRoutingIfSee node parameters
Update Notion Call object with AI dataIntegrationNotiondatabasePage / update
Split Out all objectionsTransformSplit OutSee node parameters
Format Tag Data for notionTransformEdit FieldsSee node parameters
Bundle all TagsTransformAggregateSee node parameters
Add Objection Tag to NotionWeb / APIHTTP RequestPATCH
Wait for rate limiting againWaitWaitSee node parameters
Merge Objection ThreadsTransformEdit FieldsSee node parameters
Wait for rate limiting - IntegrationWaitWaitSee node parameters
Split Out Integration dataTransformSplit OutSee node parameters
Bundle Integration Data to 1 objectTransformAggregateSee node parameters
Merge Integration ThreadTransformEdit FieldsSee node parameters
Wait for rate limiting - CompetitorsWaitWaitSee node parameters
Wait for rate limiting - ObjectionWaitWaitSee node parameters
Wait for rate limiting - Use CasesWaitWaitSee node parameters
Split Out Use CasesTransformSplit OutSee node parameters
Create Use CasesIntegrationNotiondatabasePage
Bundle Use Case Data to 1 objectTransformAggregateSee node parameters
Bundle Competitor Data to 1 objectTransformAggregateSee node parameters
Split Out Competitor DataTransformSplit OutSee node parameters
Get AI Response - CompetitorsTransformEdit FieldsSee node parameters
Merge Competitor ThreadTransformEdit FieldsSee node parameters
Merge Use Case ThreadTransformEdit FieldsSee node parameters

Setup

  1. Download the JSON and import it into an isolated n8n instance. Leave the workflow inactive.
  2. Connect your own credentials through n8n’s credential store. Replace REPLACE_WITH_* values with your resource identifiers.
  3. Inspect API destinations, Code nodes, database queries, file paths, and outbound actions.
  4. Run with synthetic data and harmless destinations. Enable triggers only after checking the actual outputs.

Requirements

An n8n instance with the listed node types and compatible versions. Service-connected workflows may require accounts, credentials, or paid APIs.

Credential types declared in the source

  • notionApi

Workflow notes

Integration Data Processing

Integration Data Processing

If it's found, we add it to Notion.

CallForge - The AI Gong Sales Call Processor

CallForge - The AI Gong Sales Call Processor

CallForge allows you to extract important information for different departments from your Sales Gong Calls.

AI Output Processor

Once the AI data is generated, it is then added (or not!) to the Notion Database here. This is also where the Pipedrive or Salesforce integration will be added once that portion is complete.

Integration Data Processing

Integration Data Processing

Purpose and structure

This folder contains the Integration Data Processing workflow. Its executable nodes use aggregate, executeWorkflowTrigger, httpRequest, if, notion, set, splitOut, wait. The table and connection map below are derived from the JSON, not an inferred guarantee of behavior.

Setup

Import inactive. Configure your own credentials and replace REPLACE_WITH_* values. Review external destinations and Code nodes before running.

Entry points

Execute Workflow Trigger

Verification

Sanitized source candidate; not runtime-tested. This overview is generated from node metadata. Read the folder README for the connection map, credential types, and license.

Attribution

https://github.com/Zie619/n8n-workflows/blob/94007c1445d9258a7da116646b79473e7c7c3282/workflows/Wait/0763_Wait_Splitout_Create_Webhook.json MIT; preserve source notices.

Canvas section labels

These name areas of the original canvas; they do not include explanatory instructions.

  • Competitor Data Processing
  • Receives AI Data from other workflow
  • Objection Data Processing
  • Use Case Processing
  • Core Data Processing

More in Automation & utilities