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

# Scheduling and triggers

> Automate and control your data workflows with precision.

### What is a Trigger?

A **trigger** defines the conditions under which a pipeline should start running, giving you full control over when and how your data workflows are executed. Triggers determine the timing for extracting data from sources, running queries, notebooks, or histories, or delivering data to destinations, depending on the pipeline's purpose.

When configuring a trigger, consider how frequently you need your data to be updated or processed — whether it’s daily, hourly, or even less. Triggers ensure your data stays up-to-date and aligned with your operational needs.

***

### Types of Triggers

Nekt provides three flexible types of triggers to accommodate various workflow requirements:

#### Schedule Trigger

Automate your pipeline execution on a set schedule. Define specific week days and times for the pipeline to run, ensuring data updates occur precisely when needed.

* **Best for:** Periodic updates like daily reports, weekly aggregations, or monthly data refreshes.

#### Event-Based Trigger

Chain your workflows by setting one pipeline as a reference for another. When the reference pipeline completes a successful run, the next pipeline automatically starts.

* **Best for:** Creating dependent workflows, such as running a query or notebook immediately after a data extraction finishes.

#### Manual Trigger

Take full control by manually starting the pipeline whenever you decide. This option is perfect for ad-hoc updates or when you want to validate changes before running the pipeline.

* **Best for:** Testing, troubleshooting, or running one-off data updates.

***

### Choosing the right Trigger

The type of trigger you choose depends on your workflow’s specific needs:

* **Need regular, predictable updates?** Use a **Schedule Trigger**.
* **Want workflows to run automatically in sequence?** Opt for an **Event-Based Trigger**.
* **Prefer control over execution?** Go with a **Manual Trigger**.

By selecting the appropriate trigger type, you can ensure your data pipelines align with your operational priorities and deliver data precisely when needed.

***

### Edit a trigger on an existing resource

You can change the trigger on an existing Source, Query, or Notebook without recreating the resource. The updated trigger applies to future runs only; past runs are unchanged.

<Steps>
  <Step title="Open the resource">
    Open the Source, Query, or Notebook you want to update.
  </Step>

  <Step title="Go to Details">
    Open the **Details** page for that resource.
  </Step>

  <Step title="Edit the trigger">
    In the **Trigger** section, click **Edit trigger**.
  </Step>

  <Step title="Choose a trigger type">
    Select the trigger type you want:

    * **Schedule** — Runs automatically on a defined schedule.
    * **Event** — Runs when another pipeline completes or emits a triggering event.
    * **Manual** — Runs only when you start it manually.
  </Step>

  <Step title="Save">
    Save your changes. The new trigger configuration is used for all future executions.
  </Step>
</Steps>

Sources, Queries, and Notebooks expose **Edit trigger** on their Details page.

***

### Why Triggers matter

Triggers are a key part of making your data workflows efficient and reliable. They minimize manual intervention, reduce latency, and ensure your data is always available when you need it—whether for analysis, reporting, or decision-making. With Nekt, triggers empower you to streamline and automate your data operations, saving time and ensuring accuracy.

Here's an example of a common trigger configuration for a complete data workflow:

* Source `pipedrive-123` has a schedule-based trigger: runs every day at 6am.
* Query `query-456` has an event-based trigger: runs as soon as `pipedrive-123` finishes the extraction.
* Destination `destination-789` has an event-based trigger: runs as soon as `query-456` finishes running.