# Event triggers

<figure><img src="/files/rkwb9XduK6c0xykMLvR6" alt=""><figcaption></figcaption></figure>

## Guides

Check our setup guide at

{% content-ref url="/pages/qMzCFYgOuwrPm6lOZeip" %}
[Configure Event Triggers](/two-way-sync/guides/event-triggers.md)
{% endcontent-ref %}

## FAQ

<details>

<summary>How many triggers can I create?</summary>

You can create as many triggers as you want, there are **no limits** as per how many triggers you can create. 🚀

</details>

<details>

<summary>Is there a maximum number of nested conditions for filtering?</summary>

No, there are **no limits**. You can create deep nested conditions as you please. Feel free to use the no-code editor as you please!

Even if there are no limits, a good practice is to keep the number of nested levels below 5 for readability and maintainability. However, going deeper than 5 nested levels will not negatively impact the system performance, so rest assured and feel free to proceed!

</details>

<details>

<summary>What data can I access from the changes in a trigger?</summary>

We provide the <mark style="color:orange;"><\<record>></mark> placeholder which will be replaced by a JSON string containing the columns of the record that was changed. Depending on the operation done to the record, certain columns will be available.

**INSERTS:** Only the columns which were added during the creation of the record will be available.

**UPDATES:** All columns which have a value will be available. Even if a single column was updated for the record, all other non-null columns will appear in the <mark style="color:orange;"><\<record>></mark> JSON string.

**DELETES:** Only the primary key of the table from where the record was deleted will be available. For example, in a sync between Salesforce and Postgres, if a record is deleted in Salesforce, the <mark style="color:orange;">Id</mark> column will be available in the <mark style="color:orange;"><\<record>></mark> JSON string. If the record is deleted in Postgres, the primary key of that table, for instance <mark style="color:orange;">stacksync\_record\_id\_Aokoxe</mark> will be available in the <mark style="color:orange;"><\<record>></mark> JSON string.

</details>

## Need help?

We are happy to give you a helping hand! Contact us directly in our [Slack community chat](/two-way-sync/start-here/community.md) or via email at <hello@stacksync.com>

Feel free to drop us any feedback or feature request if you need something, we're glad to make it happen 😉


---

# Agent Instructions: 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:

```
GET https://docs.stacksync.com/two-way-sync/features/event-triggers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.