Skip to Workflow Atlas
Playbook AtlasWorkflow Atlas
Workflow blueprintBrowse workflows
Event-Driven AutomationIntermediate

Twitter Mentions to Slack Alert

Twitter Mentions to Slack Alert is a 7-node automation blueprint connecting Twitter, Slack. Inspect its trigger, execution graph, branches, and implementation requirements.

TwitterSlack

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.

7

Nodes

6

Links

1

Run groups

Connected tools

2 integrations

  • Twitter
  • Slack

Canvas controls

Fit wide systems, then zoom into any run group.

Twitter Mentions to Slack Alert execution lanes1 run groups containing 7 workflow nodes and 6 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.Run Every 10 Minutes. integration node, cron. 0 incoming and 1 outgoing connections.STARTRun Every 10 MinutesINTEGRATIONCRON0 IN / 1 OUTSetup. transform node, set. 1 incoming and 1 outgoing connections.STEP 02SetupTRANSFORMSET1 IN / 1 OUTNow - 10 minutes. integration node, dateTime. 1 incoming and 1 outgoing connections.STEP 03Now - 10 minutesINTEGRATIONDATETIME1 IN / 1 OUTGet last 50 mentions. integration node, twitter. 1 incoming and 1 outgoing connections.STEP 04Get last 50 mentionsINTEGRATIONTWITTER1 IN / 1 OUTCreated since last run?. decision node, if. 1 incoming and 1 outgoing connections.STEP 05Created since last run?DECISIONIF1 IN / 1 OUTFilter Tweet Data. transform node, set. 1 incoming and 1 outgoing connections.STEP 06Filter Tweet DataTRANSFORMSET1 IN / 1 OUTPost to Slack. Slack node, slack. 1 incoming and 0 outgoing connections.OUTCOMEPost to SlackSLACKSLACK1 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.7 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

Run Every 10 Minutes

6 Execution Links

  1. Start

    Run Every 10 Minutes

    Integration

  2. Step 2

    Setup

    Transform

  3. Step 3

    Now - 10 minutes

    Integration

  4. Step 4

    Get last 50 mentions

    Integration

  5. Step 5

    Created since last run?

    Decision

  6. Step 6

    Filter Tweet Data

    Transform

  7. Outcome

    Post to Slack

    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