Skip to Workflow Atlas
Event-Driven AutomationIntermediate

Mattermost Standup Automation Workflow

Mattermost Standup Automation Workflow is a 29-node automation blueprint connecting Mattermost, Custom User Data API. Inspect its trigger, execution graph, branches, and implementation requirements.

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

2 integrations

  • Mattermost
  • Custom User Data API

Canvas controls

Fit wide systems, then zoom into any run group.

Mattermost Standup Automation Workflow 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.Every hour. integration node, cron. 0 incoming and 1 outgoing connections.STARTEvery hourINTEGRATIONCRON0 IN / 1 OUTRead Config 3. integration node, executeWorkflow. 1 incoming and 1 outgoing connections.STEP 02Read Config 3INTEGRATIONEXECUTEWORKFLOW1 IN / 1 OUTFilter Due Standups. transform node, function. 1 incoming and 1 outgoing connections.STEP 03Filter Due StandupsTRANSFORMFUNCTION1 IN / 1 OUTPrep Request Standup. transform node, function. 1 incoming and 1 outgoing connections.STEP 04Prep Request StandupTRANSFORMFUNCTION1 IN / 1 OUTGet User. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 05Get UserINTEGRATIONHTTPREQUEST1 IN / 1 OUTCreate Channel. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 06Create ChannelINTEGRATIONHTTPREQUEST1 IN / 1 OUTPrep Reminder. transform node, function. 1 incoming and 1 outgoing connections.STEP 07Prep ReminderTRANSFORMFUNCTION1 IN / 1 OUTRemind Users. integration node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMERemind UsersINTEGRATIONHTTPREQUEST1 IN / 0 OUTSlash Cmd from MM. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTSlash Cmd from MMTRIGGERWEBHOOK0 IN / 1 OUTconfig?. decision node, if. 1 incoming and 1 outgoing connections.STEP 02config?DECISIONIF1 IN / 1 OUTRead Config 1. integration node, executeWorkflow. 1 incoming and 1 outgoing connections.STEP 03Read Config 1INTEGRATIONEXECUTEWORKFLOW1 IN / 1 OUTPrep Config Dialog. transform node, function. 1 incoming and 1 outgoing connections.STEP 04Prep Config DialogTRANSFORMFUNCTION1 IN / 1 OUTopen config dialog. integration node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMEopen config dialogINTEGRATIONHTTPREQUEST1 IN / 0 OUTAction from MM. trigger node, webhook. 0 incoming and 1 outgoing connections.STARTAction from MMTRIGGERWEBHOOK0 IN / 1 OUTRead Config 2. integration node, executeWorkflow. 1 incoming and 1 outgoing connections.STEP 02Read Config 2INTEGRATIONEXECUTEWORKFLOW1 IN / 1 OUTcallback ID?. decision node, switch. 1 incoming and 3 outgoing connections.STEP 03callback ID?DECISIONSWITCH1 IN / 3 OUTstandup-config. integration node, noOp. 1 incoming and 1 outgoing connections.STEP 04standup-configINTEGRATIONNOOP1 IN / 1 OUTstandup-answers. integration node, noOp. 1 incoming and 1 outgoing connections.STEP 04standup-answersINTEGRATIONNOOP1 IN / 1 OUTopen-standup-dialog?. decision node, if. 1 incoming and 1 outgoing connections.STEP 04open-standup-dialog?DECISIONIF1 IN / 1 OUTPrep Config Override. transform node, function. 1 incoming and 1 outgoing connections.STEP 05Prep Config OverrideTRANSFORMFUNCTION1 IN / 1 OUTget user data. integration node, httpRequest. 1 incoming and 1 outgoing connections.STEP 05get user dataINTEGRATIONHTTPREQUEST1 IN / 1 OUTPrep Standup Dialog. transform node, function. 1 incoming and 1 outgoing connections.STEP 05Prep Standup DialogTRANSFORMFUNCTION1 IN / 1 OUTOverride Config. integration node, executeWorkflow. 1 incoming and 1 outgoing connections.STEP 06Override ConfigINTEGRATIONEXECUTEWORKFLOW1 IN / 1 OUTPrep Report. transform node, function. 1 incoming and 1 outgoing connections.STEP 06Prep ReportTRANSFORMFUNCTION1 IN / 1 OUTopen standup dialog. integration node, httpRequest. 1 incoming and 0 outgoing connections.STEP 06open standup dialogINTEGRATIONHTTPREQUEST1 IN / 0 OUTconfirm success. integration node, mattermost. 1 incoming and 0 outgoing connections.STEP 07confirm successINTEGRATIONMATTERMOST1 IN / 0 OUTpublish report. integration node, mattermost. 1 incoming and 1 outgoing connections.STEP 07publish reportINTEGRATIONMATTERMOST1 IN / 1 OUTUpdate Post. integration node, httpRequest. 1 incoming and 0 outgoing connections.OUTCOMEUpdate PostINTEGRATIONHTTPREQUEST1 IN / 0 OUTDelete ReminderPost. integration node, mattermost. 0 incoming and 0 outgoing connections.CORE RUNTIMEDelete ReminderPostINTEGRATIONMATTERMOST0 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.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

Every hour

7 Execution Links
  1. Start

    Every hour

    Integration

  2. Step 2

    Read Config 3

    Integration

  3. Step 3

    Filter Due Standups

    Transform

  4. Step 4

    Prep Request Standup

    Transform

  5. Step 5

    Get User

    Integration

  6. Step 6

    Create Channel

    Integration

  7. Step 7

    Prep Reminder

    Transform

  8. Outcome

    Remind Users

    Integration

02

Run Group

Slash Cmd from MM

4 Execution Links
  1. Start

    Slash Cmd from MM

    Trigger

  2. Step 2

    config?

    Decision

  3. Step 3

    Read Config 1

    Integration

  4. Step 4

    Prep Config Dialog

    Transform

  5. Outcome

    open config dialog

    Integration

03

Run Group

Action from MM

14 Execution Links
  1. Start

    Action from MM

    Trigger

  2. Step 2

    Read Config 2

    Integration

  3. Step 3

    callback ID?

    Decision

  4. Step 4

    standup-config

    Integration

    standup-answers

    Integration

    open-standup-dialog?

    Decision

  5. Step 5

    Prep Config Override

    Transform

    get user data

    Integration

    Prep Standup Dialog

    Transform

  6. Step 6

    Override Config

    Integration

    Prep Report

    Transform

    open standup dialog

    Integration

  7. Step 7

    confirm success

    Integration

    publish report

    Integration

  8. Outcome

    Update Post

    Integration

04

Run Group

Delete ReminderPost

0 Execution Links
  1. Core Runtime

    Delete ReminderPost

    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.