Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Featured blueprintBrowse workflows
Event-Driven AutomationAI systemIntermediate

AI-Driven Phone Agent & RetellAI Integration

AI-Driven Phone Agent & RetellAI Integration is a 29-node automation blueprint connecting OpenAI, Telegram, Google Calendar. Inspect its trigger, execution graph, branches, and implementation requirements.

OpenAITelegramGoogle CalendarGoogle DriveQdrant

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.

29

Nodes

25

Links

4

Run groups

Connected tools

5 integrations

  • OpenAI
  • Telegram
  • Google Calendar
  • Google Drive
  • Qdrant

Canvas controls

Fit wide systems, then zoom into any run group.

AI-Driven Phone Agent & RetellAI Integration execution lanes4 run groups containing 29 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 2 outgoing connections.STARTWhen clicking ‘Test workf…TRIGGERMANUALTRIGGER0 IN / 2 OUTCreate collection. integration node, httpRequest. 1 incoming and 0 outgoing connections.STEP 02Create collectionINTEGRATIONHTTPREQUEST1 IN / 0 OUTRefresh collection. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 02Refresh collectionINTEGRATIONHTTPREQUEST1 IN / 1 OUTGet folder. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 03Get folderGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTDownload Files. Google Drive node, googleDrive. 1 incoming and 1 outgoing connections.STEP 04Download FilesGOOGLE DRIVEGOOGLEDRIVE1 IN / 1 OUTQdrant Vector Store. ai node, vectorStoreQdrant. 3 incoming and 0 outgoing connections.OUTCOMEQdrant Vector StoreAIVECTORSTOREQDRANT3 IN / 0 OUTEmbeddings OpenAI. OpenAI node, embeddingsOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Embeddings OpenAIOPENAIEMBEDDINGSOPENAI0 IN / 1 OUTDefault Data Loader. ai node, documentDefaultDataLoader. 1 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Default Data LoaderAIDOCUMENTDEFAULTDATALOAD1 IN / 1 OUTToken Splitter. ai node, textSplitterTokenSplitter. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2Token SplitterAITEXTSPLITTERTOKENSPLITT0 IN / 1 OUTn8n_check_available. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTn8n_check_availableTRIGGERWEBHOOK0 IN / 1 OUTConcert start date. ai node, chainLlm. 3 incoming and 1 outgoing connections.STEP 02Concert start dateAICHAINLLM3 IN / 1 OUTGoogle Calendar. Google Calendar node, googleCalendar. 1 incoming and 0 outgoing connections.OUTCOMEGoogle CalendarGOOGLE CALENDARGOOGLECALENDAR1 IN / 0 OUTOpenAI Chat Model3. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat Model3OPENAILMCHATOPENAI0 IN / 1 OUTStructured Output Parser1. ai node, outputParserStructured. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Structured Output Parser1AIOUTPUTPARSERSTRUCTURED0 IN / 1 OUTn8n_call. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTn8n_callTRIGGERWEBHOOK0 IN / 1 OUTFilter. decision node, filter. 1 incoming and 1 outgoing connections.STEP 02FilterDECISIONFILTER1 IN / 1 OUTSet call fields. transform node, set. 1 incoming and 1 outgoing connections.STEP 03Set call fieldsTRANSFORMSET1 IN / 1 OUTExtract key points. ai node, chainLlm. 3 incoming and 1 outgoing connections.STEP 04Extract key pointsAICHAINLLM3 IN / 1 OUTTelegram. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMETelegramTELEGRAMTELEGRAM1 IN / 0 OUTStructured Output Parser. ai node, outputParserStructured. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1Structured Output ParserAIOUTPUTPARSERSTRUCTURED0 IN / 1 OUTOpenAI Chat Model. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat ModelOPENAILMCHATOPENAI0 IN / 1 OUTn8n_rag_function. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTn8n_rag_functionTRIGGERWEBHOOK0 IN / 1 OUTRetrive Agent. ai node, agent. 3 incoming and 1 outgoing connections.STEP 02Retrive AgentAIAGENT3 IN / 1 OUTRespond to Webhook. trigger node, respondToWebhook. 1 incoming and 0 outgoing connections.OUTCOMERespond to WebhookTRIGGERRESPONDTOWEBHOOK1 IN / 0 OUTOpenAI Chat Model2. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1OpenAI Chat Model2OPENAILMCHATOPENAI0 IN / 1 OUTRAG. ai node, toolVectorStore. 2 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 1RAGAITOOLVECTORSTORE2 IN / 1 OUTRetrive Qdrant Vector Store. ai node, vectorStoreQdrant. 1 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2Retrive Qdrant Vector StoreAIVECTORSTOREQDRANT1 IN / 1 OUTOpenAI Chat Model1. OpenAI node, lmChatOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 2OpenAI Chat Model1OPENAILMCHATOPENAI0 IN / 1 OUTEmbeddings OpenAI2. OpenAI node, embeddingsOpenAi. 0 incoming and 1 outgoing connections.DEPENDENCY · DEPTH 3Embeddings OpenAI2OPENAIEMBEDDINGSOPENAI0 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.29 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’

5 Execution Links3 Support Dependencies

  1. Start

    When clicking ‘Test workflow’

    Trigger

  2. Step 2

    Create collection

    Integration

    Refresh collection

    Integration

  3. Step 3

    Get folder

    Integration

  4. Step 4

    Download Files

    Integration

  5. Outcome

    Qdrant Vector Store

    AI reasoning

Attached dependencies

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

3 nodes

  • Embeddings OpenAI

    AI reasoning dependency

  • Default Data Loader

    AI reasoning dependency

  • Token Splitter

    AI reasoning dependency

02

Run Group

n8n_check_available

2 Execution Links2 Support Dependencies

  1. Start

    n8n_check_available

    Trigger

  2. Step 2

    Concert start date

    AI reasoning

  3. Outcome

    Google Calendar

    Integration

Attached dependencies

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

2 nodes

  • OpenAI Chat Model3

    AI reasoning dependency

  • Structured Output Parser1

    AI reasoning dependency

03

Run Group

n8n_call

4 Execution Links2 Support Dependencies

  1. Start

    n8n_call

    Trigger

  2. Step 2

    Filter

    Decision

  3. Step 3

    Set call fields

    Transform

  4. Step 4

    Extract key points

    AI reasoning

  5. Outcome

    Telegram

    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

04

Run Group

n8n_rag_function

2 Execution Links5 Support Dependencies

  1. Start

    n8n_rag_function

    Trigger

  2. Step 2

    Retrive Agent

    AI reasoning

  3. Outcome

    Respond to Webhook

    Trigger

Attached dependencies

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

5 nodes

  • OpenAI Chat Model2

    AI reasoning dependency

  • RAG

    AI reasoning dependency

  • Retrive Qdrant Vector Store

    AI reasoning dependency

  • OpenAI Chat Model1

    AI reasoning dependency

  • Embeddings OpenAI2

    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