Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineIntermediate

Daily Fundraise Data Aggregator

Daily Fundraise Data Aggregator is a 11-node automation blueprint connecting Piloterr API, Google Sheets. Inspect its trigger, execution graph, branches, and implementation requirements.

Piloterr APIGoogle Sheets

Interactive system map

Follow the runtime. Inspect what supports it.

Solid horizontal paths show main-channel execution. Violet dependencies sit beneath the exact step they configure or empower.

11

Nodes

13

Links

1

Run groups

Connected tools

2 integrations

  • Piloterr API
  • Google Sheets

Canvas controls

Fit wide systems, then zoom into any run group.

Daily Fundraise Data Aggregator execution lanes1 run groups containing 11 workflow nodes and 13 visible links. Solid horizontal lines are main-channel runtime links. Violet dashed lines connect typed dependencies beneath the runtime step they support. Focus any node to inspect its immediate path.Schedule Trigger - Run Workflow Every Day. trigger node, scheduleTrigger. 0 incoming and 3 outgoing connections.STARTSchedule Trigger - Run Wo…TRIGGERSCHEDULETRIGGER0 IN / 3 OUTPiloterr - Get Recent Fundraise - Serie A. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02Piloterr - Get Recent Fun…INTEGRATIONHTTPREQUEST1 IN / 1 OUTPiloterr - Get Recent Fundraise - Serie B. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02Piloterr - Get Recent Fun…INTEGRATIONHTTPREQUEST1 IN / 1 OUTPiloterr - Get Recent Fundraise - Seed. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02Piloterr - Get Recent Fun…INTEGRATIONHTTPREQUEST1 IN / 1 OUTSplit results. transform node, itemLists. 3 incoming and 1 outgoing connections.STEP 03Split resultsTRANSFORMITEMLISTS3 IN / 1 OUTPrepare data. transform node, set. 1 incoming and 2 outgoing connections.STEP 04Prepare dataTRANSFORMSET1 IN / 2 OUTPiloterr - Enrich company. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 05Piloterr - Enrich companyINTEGRATIONHTTPREQUEST1 IN / 1 OUTGet Linkedin URL from object. transform node, code. 1 incoming and 1 outgoing connections.STEP 06Get Linkedin URL from obj…TRANSFORMCODE1 IN / 1 OUTPrepare data before importing to Gsheets. transform node, set. 1 incoming and 1 outgoing connections.STEP 07Prepare data before impor…TRANSFORMSET1 IN / 1 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 08MergeDECISIONMERGE2 IN / 1 OUTGoogle Sheets. Google Sheets node, googleSheets. 1 incoming and 0 outgoing connections.OUTCOMEGoogle SheetsGOOGLE SHEETSGOOGLESHEETS1 IN / 0 OUT

Signal inspector

Focus, hover, or select a step to isolate its runtime and support links.

Main-channel runtimeTyped dependencytriggeraidecisiontransformintegration
Scroll horizontally to follow every connected flow.11 connected nodesEnter or click to lock · Escape to clear

Runtime breakdown

Read the execution spine before its dependencies.

Each run group separates main-channel steps from the models, tools, retrievers, and data services that support them. Start and outcome labels apply only to runtime nodes.

01

Run Group

Schedule Trigger - Run Workflo…

13 Execution Links

  1. Start

    Schedule Trigger - Run Workflow Every Day

    Trigger

  2. Step 2

    Piloterr - Get Recent Fundraise - Serie A

    Integration

    Piloterr - Get Recent Fundraise - Serie B

    Integration

    Piloterr - Get Recent Fundraise - Seed

    Integration

  3. Step 3

    Split results

    Transform

  4. Step 4

    Prepare data

    Transform

  5. Step 5

    Piloterr - Enrich company

    Integration

  6. Step 6

    Get Linkedin URL from object

    Transform

  7. Step 7

    Prepare data before importing to Gsheets

    Transform

  8. Step 8

    Merge

    Decision

  9. Outcome

    Google Sheets

    Integration

Turn the map into a plan

Adapt this blueprint to your company.

Bring the system shape into a workspace, then define the production controls, data boundaries, owners, and delivery sequence around your context.

Create a build planReturn to the atlas