Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Scheduled Monitoring and AlertingAI systemIntermediate

SSL Certificate Expiry Alert Workflow

SSL Certificate Expiry Alert Workflow is a 11-node automation blueprint connecting Google Sheets, Gmail, Telegram. Inspect its trigger, execution graph, branches, and implementation requirements.

Google SheetsGmailTelegramNtfy

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

10

Links

1

Run groups

Connected tools

4 integrations

  • Google Sheets
  • Gmail
  • Telegram
  • Ntfy

Canvas controls

Fit wide systems, then zoom into any run group.

SSL Certificate Expiry Alert Workflow execution lanes1 run groups containing 11 workflow nodes and 10 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.Weekly Trigger. trigger node, scheduleTrigger. 0 incoming and 1 outgoing connections.STARTWeekly TriggerTRIGGERSCHEDULETRIGGER0 IN / 1 OUTFetch URLs. Google Sheets node, googleSheets. 1 incoming and 1 outgoing connections.STEP 02Fetch URLsGOOGLE SHEETSGOOGLESHEETS1 IN / 1 OUTCheck SSL. integration node, httpRequest. 1 incoming and 2 outgoing connections.STEP 03Check SSLINTEGRATIONHTTPREQUEST1 IN / 2 OUTURLs to Monitor. Google Sheets node, googleSheets. 1 incoming and 0 outgoing connections.STEP 04URLs to MonitorGOOGLE SHEETSGOOGLESHEETS1 IN / 0 OUTSwitch. decision node, switch. 1 incoming and 6 outgoing connections.STEP 04SwitchDECISIONSWITCH1 IN / 6 OUTSend Alert Email2. Gmail node, gmail. 1 incoming and 0 outgoing connections.OUTCOMESend Alert Email2GMAILGMAIL1 IN / 0 OUTTelegram. Telegram node, telegram. 1 incoming and 0 outgoing connections.OUTCOMETelegramTELEGRAMTELEGRAM1 IN / 0 OUTSend Alert Email4. Gmail node, gmail. 1 incoming and 0 outgoing connections.OUTCOMESend Alert Email4GMAILGMAIL1 IN / 0 OUTSend Alert Email1. Gmail node, gmail. 1 incoming and 0 outgoing connections.OUTCOMESend Alert Email1GMAILGMAIL1 IN / 0 OUTSend Alert Email6. Gmail node, gmail. 1 incoming and 0 outgoing connections.OUTCOMESend Alert Email6GMAILGMAIL1 IN / 0 OUTNtfy4. integration node, Ntfy. 1 incoming and 0 outgoing connections.OUTCOMENtfy4INTEGRATIONNTFY1 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

Weekly Trigger

10 Execution Links

  1. Start

    Weekly Trigger

    Trigger

  2. Step 2

    Fetch URLs

    Integration

  3. Step 3

    Check SSL

    Integration

  4. Step 4

    URLs to Monitor

    Integration

    Switch

    Decision

  5. Outcome

    Send Alert Email2

    Integration

    Telegram

    Integration

    Send Alert Email4

    Integration

    Send Alert Email1

    Integration

    Send Alert Email6

    Integration

    Ntfy4

    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