Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
ETL PipelineAI systemIntermediate

AI-Powered Resume Analysis Workflow

AI-Powered Resume Analysis Workflow is a 12-node automation blueprint connecting OpenAI, Google Sheets, Google Drive. Inspect its trigger, execution graph, branches, and implementation requirements.

OpenAIGoogle SheetsGoogle Drive

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.

12

Nodes

15

Links

1

Run groups

Connected tools

3 integrations

  • OpenAI
  • Google Sheets
  • Google Drive

Canvas controls

Fit wide systems, then zoom into any run group.

AI-Powered Resume Analysis Workflow execution lanes1 run groups containing 12 workflow nodes and 15 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.On form submission. trigger node, formTrigger. 0 incoming and 2 outgoing connections.STARTOn form submissionTRIGGERFORMTRIGGER0 IN / 2 OUTUpload to google drive. Google Drive node, googleDrive. 1 incoming and 0 outgoing connections.STEP 02Upload to google driveGOOGLE DRIVEGOOGLEDRIVE1 IN / 0 OUTResume extraction. integration node, extractFromFile. 1 incoming and 2 outgoing connections.STEP 02Resume extractionINTEGRATIONEXTRACTFROMFILE1 IN / 2 OUTPersonal Info. ai node, informationExtractor. 2 incoming and 1 outgoing connections.STEP 03Personal InfoAIINFORMATIONEXTRACTOR2 IN / 1 OUTQualification. ai node, informationExtractor. 2 incoming and 1 outgoing connections.STEP 03QualificationAIINFORMATIONEXTRACTOR2 IN / 1 OUTMerge. decision node, merge. 2 incoming and 1 outgoing connections.STEP 04MergeDECISIONMERGE2 IN / 1 OUTSummarizer. ai node, chainSummarization. 2 incoming and 1 outgoing connections.STEP 05SummarizerAICHAINSUMMARIZATION2 IN / 1 OUTwanted profile. transform node, set. 1 incoming and 1 outgoing connections.STEP 06wanted profileTRANSFORMSET1 IN / 1 OUTHR Expert. ai node, chainLlm. 3 incoming and 1 outgoing connections.STEP 07HR ExpertAICHAINLLM3 IN / 1 OUTGoogle Sheets. Google Sheets node, googleSheets. 1 incoming and 0 outgoing connections.OUTCOMEGoogle SheetsGOOGLE SHEETSGOOGLESHEETS1 IN / 0 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 4 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 4 OUTStructured Output Parser. ai node, outputParserStructured. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Structured Output ParserAIOUTPUTPARSERSTRUCTURED0 IN / 1 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.12 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

On form submission

10 Execution Links5 Support Dependencies

  1. Start

    On form submission

    Trigger

  2. Step 2

    Upload to google drive

    Integration

    Resume extraction

    Integration

  3. Step 3

    Personal Info

    AI reasoning

    Qualification

    AI reasoning

  4. Step 4

    Merge

    Decision

  5. Step 5

    Summarizer

    AI reasoning

  6. Step 6

    wanted profile

    Transform

  7. Step 7

    HR Expert

    AI reasoning

  8. Outcome

    Google Sheets

    Integration

Attached dependencies

These nodes support the runtime above; they are not additional starts or outcomes.

2 nodes

  • Structured Output Parser

    AI reasoning dependency

  • OpenAI Chat Model

    AI reasoning dependency

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