> For the complete documentation index, see [llms.txt](https://docs.stacksync.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacksync.com/agentic-workflows/triggers/app-triggers.md).

# App Triggers

Stacksync continuously watches the connected app for changes using **Change Data Capture (CDC)**. The moment a record changes, Stacksync captures the event and starts your workflow with that record's data typically within seconds.

### Set it up

1. In your workflow, add a trigger and choose the **App Trigger** you want from the trigger catalog.

   <figure><img src="/files/iYX09NnizVjZpG2HimuO" alt=""><figcaption></figcaption></figure>
2. Select an existing connection or create a new connection and click next

   <figure><img src="/files/CgUSzMS65dGxzr7XRaQj" alt=""><figcaption></figcaption></figure>
3. Choose the table(s) you want to capture the changes from.

   <figure><img src="/files/9OvTyS8D6A7bZ1YiXp3N" alt=""><figcaption></figcaption></figure>
4. Choose the columns you want to track. By default, all the columns are selected, you can edit them as required.

   <figure><img src="/files/tRfP8W1Jp101L5je8xuf" alt=""><figcaption></figcaption></figure>
5. Configure the Trigger

   <figure><img src="/files/vpiV3vQNxCqZMZAmvKnO" alt=""><figcaption></figcaption></figure>
6. Pick the **event types** (Created, Updated, Deleted).

   <figure><img src="/files/1yJp3mTSHmT7KzlH6zh5" alt=""><figcaption></figcaption></figure>
7. Add **filter conditions** so it fires only on relevant changes.

   <figure><img src="/files/CDeBIszrm6oVn6h0WE6L" alt=""><figcaption></figcaption></figure>
8. (Optional) Enable **historic backfill** to include existing records.

   <figure><img src="/files/W6rhqCKJunuExWm2q2n6" alt=""><figcaption></figcaption></figure>
9. Save and turn the workflow on.&#x20;

***

App Triggers fire on three event types:

| Event       | Fires when…                           |
| ----------- | ------------------------------------- |
| **Created** | A new record is added                 |
| **Updated** | One or more fields on a record change |
| **Deleted** | A record is removed                   |

You can pick **any** combination of the three.

### What your workflow receives

Each time the trigger fires, it passes the event into your workflow so downstream modules can use it:

* **`record`** - the full record, with all its fields.
* **`changes`** - only the fields that changed (on update events).

Reference these anywhere in the workflow to route, transform, or write the data into another system.

### Filter conditions

You usually don't want the workflow to run on *every* change. Add **filter conditions** so it only fires when the change actually matters. For example, you can trigger the Salesforce trigger only when `status` becomes `Closed Won`, or only when `amount` is above a threshold.

* Build conditions in the no-code editor using **AND / OR** logic.
* Nest conditions as deeply as you need for precise targeting.
* Only changes that match the filter start the workflow and everything else is ignored.

### Historic backfill

By default, an App Trigger only processes changes that happen **after** you turn it on. If you also want to run the workflow over records that already exist, enable **historic backfill**.

* **Go-forward (default):** only new changes from this point on.
* **Backfill:** Stacksync replays your existing records through the trigger once, so the workflow processes the back-catalog too.

{% hint style="warning" %}
Backfill can generate a large number of executions on objects with many existing records. Apply filter conditions first, and start on a smaller object if you want to validate behavior before backfilling everything.
{% endhint %}

Questions about setting up an App Trigger? Reach us in the Slack community or at <hello@stacksync.com>.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.stacksync.com/agentic-workflows/triggers/app-triggers.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.