Signals

Signals are the trigger events that initiate or advance an Agent's workflow. They represent the "pulse" of conversation and activity that Duster listens to.

How Signals Work

Every time something happens in a connected integration—like a user posting a message in Slack—a Signal is generated. This signal carries context: who sent it, what was said, and where it came from.

The Agent receives this signal and decides if it needs to act based on its active Workflow.

Types of Signals

Signals are generally categorized by their source:

User Signals (user)

These are inputs from humans.

• New Message: A user posts a bug report in #bugs.
• Reply: A user answers a clarifying question from the Agent.
• Feedback Submission: A user submits a form.

Machine Signals (machine / assistant)

These are actions or responses generated by the Agent itself or the system.

• Agent Reply: The Agent posts a response in a thread.
• Tool Output: A system tool completes an action (e.g., "Issue Created") and reports back to the context.

The Signal Loop

1. Event Occurs: A user sends a message "Login is broken".
2. Signal Created: Duster creates a User Signal.
3. Processing: The active Workflow processes the signal.
4. Response: The Workflow generates a Machine Signal (e.g., "Can you provide a screenshot?") or executes a tool.
5. Context: Both signals are now part of the Thread History, informing future decisions.