Signal Created Trigger

The Signal Created Trigger fires when another workflow creates a signal. This lets you chain workflows together, building multi-step automation pipelines where one workflow's output becomes another workflow's input.

When to Use It

  • Chain workflows together for complex, multi-stage automation

  • React to signals created by other workflows (e.g., a signal flagging a high-priority lead)

  • Separate detection logic from action logic across different workflows

  • Build modular workflow architectures that are easier to maintain

How to Set It Up

  1. Create a new workflow and select Signal Created Trigger as your trigger node

  2. The trigger will fire whenever any workflow in your account creates a signal

  3. Use a Filter node after the trigger to react only to specific signal types or severities

Note: Signals are created by the "Create Signal" action node in other workflows. Make sure you have at least one workflow that creates signals before using this trigger.

Output Variables

Variable

Description

signalId

Unique identifier of the created signal

signal.name

Name of the signal

signal.description

Description of the signal

signal.severity

Severity level: low, medium, high, or critical

The trigger also passes through data from the original workflow that created the signal, including prospect and post data.

Variable Syntax

Reference signal variables in downstream nodes:

{{ !ref($.trigger.outputs.signalId) }}{{ !ref($.trigger.outputs.signal.name) }}{{ !ref($.trigger.outputs.signal.description) }}{{ !ref($.trigger.outputs.signal.severity) }}

Example Workflow

Pro tip: Use signals to separate "detection" workflows from "action" workflows. For example, one workflow detects buying intent and creates a signal, while a second workflow picks up that signal and triggers personalized outreach. This modular approach makes workflows easier to debug and maintain.