Bear Brown
← All N8N workflows
Data & databasesCodeExecute WorkflowExecute Workflow TriggerFilterGmail

Calling a Sub-workflow

Configured with Execute Workflow, Execute Workflow Trigger, Filter, Gmail, and additional nodes. Review the connections and setup before adapting this template.

Download workflow JSONView files on GitHub ↗36 nodes · MIT
Workflow preview
TriggerWhen clicking ‘Testworkflow’Manual TriggerWeb / APIGet list of ownersHTTP RequestWeb / APIGet list of clients forownerHTTP RequestRoutingIfIfTransformEditEdit FieldsTransformIncrement PageEdit FieldsTransformSplit Out1Split OutCodeMerge al the entriesCodeRoutingIf linkedin url isemptyIfRoutingif new postIfSubworkflowGet list of clientsExecute WorkflowTriggerWhen Executed byAnother WorkflowExecute Workflow TriggerSubworkflowGet last postExecute WorkflowMessagingGmailGmailWeb / APISearch for user by linkHTTP RequestRoutingDo nothingNo OpCodeMerge profileURLCodeTransformSet last_postEdit FieldsTransformSet last_positionEdit FieldsRoutingif new positionIfTransformSet data hereEdit FieldsRoutingChange this for testingFilterData storeCreate entry with emailGoogle SheetsData storeGet rows from documentGoogle SheetsWeb / APISearch for user profileby namesHTTP RequestRoutingProfile URL not found?IfTransformSet the profile URLEdit FieldsTransformSet the profile URL1Edit FieldsData storeUpdate last postGoogle SheetsData storeUpdates last positionGoogle SheetsTransformSet post_updatedEdit FieldsTransformSet position_updatedEdit FieldsCodeGenerate the email textCodeTransformMerge on emailMergeTransformSplit Out ownersSplit OutRoutingGet current ownerFilter

Node categories in this workflow

  • Trigger
  • Web / API
  • Routing
  • Transform
  • Code
  • Subworkflow
  • Messaging
  • Data store

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
When clicking ‘Test workflow’TriggerManual TriggerSee node parameters
Get list of ownersWeb / APIHTTP RequestSee node parameters
Get list of clients for ownerWeb / APIHTTP RequestPOST
IfRoutingIfSee node parameters
EditTransformEdit FieldsSee node parameters
Increment PageTransformEdit FieldsSee node parameters
Split Out1TransformSplit OutSee node parameters
Merge al the entriesCodeCodeSee node parameters
If linkedin url is emptyRoutingIfSee node parameters
if new postRoutingIfSee node parameters
Get list of clientsSubworkflowExecute WorkflowSee node parameters
When Executed by Another WorkflowTriggerExecute Workflow TriggerSee node parameters
Get last postSubworkflowExecute WorkflowSee node parameters
GmailMessagingGmailSee node parameters
Search for user by linkWeb / APIHTTP RequestSee node parameters
Do nothingRoutingNo OpSee node parameters
Merge profileURLCodeCodeSee node parameters
Set last_postTransformEdit FieldsSee node parameters
Set last_positionTransformEdit FieldsSee node parameters
if new positionRoutingIfSee node parameters
Set data hereTransformEdit FieldsSee node parameters
Change this for testingRoutingFilterSee node parameters
Create entry with emailData storeGoogle SheetsappendOrUpdate
Get rows from documentData storeGoogle SheetsSee node parameters
Search for user profile by namesWeb / APIHTTP RequestSee node parameters
Profile URL not found?RoutingIfSee node parameters
Set the profile URLTransformEdit FieldsSee node parameters
Set the profile URL1TransformEdit FieldsSee node parameters
Update last postData storeGoogle SheetsappendOrUpdate
Updates last positionData storeGoogle SheetsappendOrUpdate
Set post_updatedTransformEdit FieldsSee node parameters
Set position_updatedTransformEdit FieldsSee node parameters
Generate the email textCodeCodeSee node parameters
Merge on emailTransformMergeSee node parameters
Split Out ownersTransformSplit OutSee node parameters
Get current ownerRoutingFilterSee 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

  • gmailOAuth2
  • googleSheetsOAuth2Api
  • httpHeaderAuth
  • hubspotOAuth2Api

Workflow notes

Settings

Settings

  • Set in "Set data here" the email you are registered with in Hubspot as an Owner, and the link of a Google sheet copied from this one
Search for user by link

Search by Name and company

Hubspot API

Hubspot API

Calls a Hubpot API endpoint to get the list of Owners You have to select "Predefined credential type" and choose "Hubspot Oauth2 API". Then folow the instructions here

Calling a Sub-workflow

Calling a Sub-workflow

For lisibility only

For testing

For testing

We recommend to filter a small number of clients here

Preparing the Google sheet

Preparing the Google sheet

  • Create an entry for each client with his email
  • Get rows for later comparison
Adding other tests

Adding other tests

Here you can set other tests like:

  • New comments in LinkedIn
  • Hubspot activities
  • Hubspot updates etc.
Searching for the LinkedIn URL

Searching for the LinkedIn URL

  • Set here you rapid API key
  • If we find the URL, searches for more info about the client
Get all clients for this owner

Get all clients for this owner

As we are limited to 200 clients by the Hubsot API, we have to loop to get all of them

Contact me

Contact me

  • If you need any modification to this workflow
  • if you need some help with this workflow
  • Or if you need any workflow in n8n, Make, or Langchain / Langgraph

Write to me: user@example.com

Calling a Sub-workflow

Calling a Sub-workflow

Purpose and structure

This folder contains the Calling a Sub-workflow workflow. Its executable nodes use code, executeWorkflow, executeWorkflowTrigger, filter, gmail, googleSheets, httpRequest, if, manualTrigger, merge, noOp, set, splitOut. 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

When clicking ‘Test workflow’, When Executed by Another Workflow

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/Splitout/0915_Splitout_Code_Create_Webhook.json MIT; preserve source notices.

Canvas section labels

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

  • Generating the alert email

More in Data & databases

1/ Add Your credentials1/ Add Your credentials2. Add Beehiiv newsletter subscribers from Gumroad sales