> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/technical-reference/triggers-and-webhooks/trigger-activation-and-execution-context.md).

# Trigger Activation and Execution Context

A trigger starts a workflow after an event or schedule. Configure both the event source and the workflow inputs before enabling it.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2Fs8PzCopMjQ8q7WRps7dj%2FG054.mp4?alt=media&token=d10f8f3a-4b01-4fe9-b3ec-50cedde84f3a>" %}

## Before you begin

Permission to configure the trigger and any required provider connection or release.

## Key concepts

| Term              | Definition                                                                                                                                          |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| Trigger           | A schedule or event source that starts a workflow. It must be configured and activated; discovering it in the catalog does not activate it.         |
| Activation        | The state in which a configured trigger can start work. Saving or listing a trigger does not establish that it is active.                           |
| Event payload     | The data delivered by an event source. Map its actual fields and types to the receiving workflow inputs.                                            |
| Input field       | A value collected from a user or client for execution. Map its displayed label to the correct workflow input key.                                   |
| Published release | The selected project version made available through a published execution path. Confirm the active release after a publication or promotion action. |

## Activate a trigger

1. Select the trigger type and configure its event or schedule.

![Check the trigger status and linked project in Settings → Triggers.](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/7iA5jFr58vss4Xt6TqD1/assets/g054-g054-01-inventory.png)

Check the trigger status and linked project in Settings → Triggers.

2. Map the event fields to the workflow inputs.
3. Enable the trigger through the supported release controls and inspect the next triggered run.

The expected event starts the intended workflow with the required input.

## Behavior and limitations

Saving trigger settings is not the same as activating them. The selected release and environment affect execution. A provider event can omit fields present in another event type. Verify activation and input mapping before diagnosing downstream nodes.

## Related resources

[Manage configured triggers](https://docs.stackai.com/guides-and-quickstarts/using-tools-and-actions/manage-configured-triggers.md)

[Schedules, Time Zones, and Calendar Edge Cases](https://docs.stackai.com/technical-reference/triggers-and-webhooks/schedules-time-zones-and-calendar-edge-cases.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/technical-reference/triggers-and-webhooks/trigger-activation-and-execution-context.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
