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

Email Query Translator & Executor

Email Query Translator & Executor is a 23-node automation blueprint connecting Langchain, PostgreSQL. Inspect its trigger, execution graph, branches, and implementation requirements.

LangchainPostgreSQL

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.

23

Nodes

25

Links

1

Run groups

Connected tools

2 integrations

  • LangChain
  • PostgreSQL

Canvas controls

Fit wide systems, then zoom into any run group.

Email Query Translator & Executor execution lanes1 run groups containing 23 workflow nodes and 25 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.When clicking "Test workflow". trigger node, manualTrigger. 0 incoming and 1 outgoing connections.STARTWhen clicking "Test workf…TRIGGERMANUALTRIGGER0 IN / 1 OUTChat Trigger. trigger node, chatTrigger. 0 incoming and 1 outgoing connections.STARTChat TriggerTRIGGERCHATTRIGGER0 IN / 1 OUTWorkflowTrigger. trigger node, executeWorkflowTrigger. 0 incoming and 1 outgoing connections.STARTWorkflowTriggerTRIGGEREXECUTEWORKFLOWTRIGGER0 IN / 1 OUTList all tables in a database. PostgreSQL node, postgres. 2 incoming and 1 outgoing connections.STEP 02List all tables in a data…POSTGRESQLPOSTGRES2 IN / 1 OUTLoad the schema from the local file. integration node, readWriteFile. 3 incoming and 1 outgoing connections.STEP 03Load the schema from the …INTEGRATIONREADWRITEFILE3 IN / 1 OUTList all columns in a table. PostgreSQL node, postgres. 1 incoming and 1 outgoing connections.STEP 04List all columns in a tablePOSTGRESQLPOSTGRES1 IN / 1 OUTIf file exists or already retried generating it. decision node, if. 1 incoming and 2 outgoing connections.STEP 05If file exists or already…DECISIONIF1 IN / 2 OUTAdd table name to output. transform node, set. 1 incoming and 1 outgoing connections.STEP 06Add table name to outputTRANSFORMSET1 IN / 1 OUTExtract data from file. integration node, extractFromFile. 1 incoming and 1 outgoing connections.STEP 07Extract data from fileINTEGRATIONEXTRACTFROMFILE1 IN / 1 OUTConvert data to binary. integration node, convertToFile. 1 incoming and 1 outgoing connections.STEP 08Convert data to binaryINTEGRATIONCONVERTTOFILE1 IN / 1 OUTCombine schema data and chat input. transform node, set. 1 incoming and 1 outgoing connections.STEP 09Combine schema data and c…TRANSFORMSET1 IN / 1 OUTSave file locally. integration node, readWriteFile. 1 incoming and 1 outgoing connections.STEP 10Save file locallyINTEGRATIONREADWRITEFILE1 IN / 1 OUTAI Agent. ai node, agent. 2 incoming and 1 outgoing connections.STEP 11AI AgentAIAGENT2 IN / 1 OUTIf ran manually. decision node, if. 1 incoming and 1 outgoing connections.STEP 12If ran manuallyDECISIONIF1 IN / 1 OUTExtract SQL query. transform node, set. 1 incoming and 1 outgoing connections.STEP 13Extract SQL queryTRANSFORMSET1 IN / 1 OUTCheck for trailing semicolon. decision node, if. 1 incoming and 2 outgoing connections.STEP 14Check for trailing semico…DECISIONIF1 IN / 2 OUTAdd trailing semicolon. transform node, set. 1 incoming and 1 outgoing connections.STEP 15Add trailing semicolonTRANSFORMSET1 IN / 1 OUTCheck if query exists. decision node, if. 2 incoming and 3 outgoing connections.STEP 16Check if query existsDECISIONIF2 IN / 3 OUTPostgres. PostgreSQL node, postgres. 1 incoming and 1 outgoing connections.STEP 17PostgresPOSTGRESQLPOSTGRES1 IN / 1 OUTFormat empty output. transform node, set. 1 incoming and 0 outgoing connections.STEP 18Format empty outputTRANSFORMSET1 IN / 0 OUTFormat query results. transform node, set. 1 incoming and 1 outgoing connections.STEP 19Format query resultsTRANSFORMSET1 IN / 1 OUTCombine query result and chat answer. decision node, merge. 2 incoming and 0 outgoing connections.OUTCOMECombine query result and …DECISIONMERGE2 IN / 0 OUTOllama Chat Model. ai node, lmChatOllama. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Ollama Chat ModelAILMCHATOLLAMA0 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.23 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

When clicking "Test workflow"

24 Execution Links1 Support Dependency

  1. Start

    When clicking "Test workflow"

    Trigger

    Chat Trigger

    Trigger

    WorkflowTrigger

    Trigger

  2. Step 2

    List all tables in a database

    Integration

  3. Step 3

    Load the schema from the local file

    Integration

  4. Step 4

    List all columns in a table

    Integration

  5. Step 5

    If file exists or already retried generating it

    Decision

  6. Step 6

    Add table name to output

    Transform

  7. Step 7

    Extract data from file

    Integration

  8. Step 8

    Convert data to binary

    Integration

  9. Step 9

    Combine schema data and chat input

    Transform

  10. Step 10

    Save file locally

    Integration

  11. Step 11

    AI Agent

    AI reasoning

  12. Step 12

    If ran manually

    Decision

  13. Step 13

    Extract SQL query

    Transform

  14. Step 14

    Check for trailing semicolon

    Decision

  15. Step 15

    Add trailing semicolon

    Transform

  16. Step 16

    Check if query exists

    Decision

  17. Step 17

    Postgres

    Integration

  18. Step 18

    Format empty output

    Transform

  19. Step 19

    Format query results

    Transform

  20. Outcome

    Combine query result and chat answer

    Decision

Attached dependencies

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

1 node

  • Ollama 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