> ## Documentation Index
> Fetch the complete documentation index at: https://docs.conduit.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Triggers

> Decide what starts an agent: an inbox, a team channel, a schedule, a webhook, or a workspace event.

Customer agents can be attached to an inbox trigger. The agent sidebar shows the current inbox trigger and warns if another agent is already listening to that inbox.

Internal agents can be connected to team channels. Slack is available in the internal-agent channel area. Other channel trigger rows may appear disabled until they are enabled for your workspace.

Internal agents also support these trigger types:

| Trigger | Runs when |
| - | - |
| **Manual** | A teammate or Operator runs the agent directly. |
| **Schedule** | A cron-style interval you configure (for example, every morning, or 14 days before an arrival date). |
| **Webhook** | An external system calls Conduit's API to start a run. |
| **Workflow** | A workspace event happens — the same events that power Workflow automations elsewhere in Conduit. |

> [!TIP]
>
> When you are still writing a scheduled agent's skills, create the schedule but leave it inactive. You can then build and test without the agent running against live data, and activate the schedule once the behaviour is right.

A **Workflow trigger** doesn't require you to build a companion workflow. Pick the event the agent should react to — a new reservation, a label being added, a PMS reporting that a unit's cleaning status changed, and so on — and the agent runs automatically whenever that event fires, anywhere in the workspace. Workflows and agents share the same underlying events, so the same trigger that starts a Workflow can start an agent instead.

> [!TIP]
>
> **Workflow or agent?** If something should happen the same way every time, build a Workflow — treat it like code, deterministic and consistent. If the right action depends on judgment, or there are too many conditions to enumerate in advance, build an agent instead. A useful test: if a human would be inconsistent deciding what to do (say, right only half the time), that's a sign the task needs an agent's reasoning, not a fixed set of rules.

See [Internal Agent Use Cases](https://docs.conduit.ai/build-your-agent/internal-agent-use-cases.md) for worked examples, including a cleaning-status agent that reacts to a live PMS webhook today.

Treat disabled trigger controls as unavailable until the product surface enables them in your workspace.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.