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

# Triggers overview

> How workflow runs start in NoClick: manual runs, schedules, webhooks, forms, inbound email, app events, and the API/SDK.

Every workflow run starts with a trigger. A trigger is the entry point of your workflow: when it fires, NoClick executes the nodes connected downstream of it. A workflow can hold more than one trigger, and each fires independently.

## Trigger types

| Trigger                            | Starts a run when...                                                                                    |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------- |
| Manual                             | You click **Run** on the canvas. See [Running and testing](/editor/running-and-testing).                |
| [Schedule](/triggers/schedules)    | A recurring schedule fires (every N minutes, daily at 9:00 AM, weekly, monthly).                        |
| [Webhook](/triggers/webhooks)      | An HTTP request hits the node's unique URL on `noclick.run`.                                            |
| [Form](/triggers/forms)            | Someone submits the node's hosted form, or a published app passes inputs.                               |
| [Email](/triggers/email)           | An email arrives at the node's reserved `name@noclick.app` address.                                     |
| [App events](/triggers/app-events) | An event happens in a connected service, like a Slack message, a new HubSpot contact, or a GitHub push. |
| API / SDK                          | Your code calls `workflow.execute()` through the [NoClick SDK](/sdk/overview).                          |

## Where to see what triggered a run

Every run records its trigger source. Open the **Logs** tab in the canvas top bar: each row shows the source (Manual, Schedule, Webhook, Email, Form, or API) along with status, duration, and any error message. See [Execution logs](/editor/execution-logs).

<Tip>
  To pause a trigger without deleting it, disable the trigger node. Incoming events are acknowledged but the workflow does not run until you re-enable it.
</Tip>

## Triggers and AI agents

A trigger wired directly into an AI agent delivers the fired event as part of the agent's turn, so the agent can read a Slack message or an email and act on it. See [Channel agents](/agents/channel-agents).