/
Automate your workflows by responding instantly to key events across your connected systems. Event triggers let you set up powerful automations that launch whenever a specific event takes place, saving time and reducing manual effort.
Event triggers empower your organization to move from reactive to proactive operations. By automating responses to key events, you reduce manual work, minimize errors, and ensure that critical processes happen exactly when needed. This leads to faster response times, improved accuracy, and a seamless experience for both your team and your customers.
What are triggers in Stacksync and how do they work?
Triggers in Stacksync are automated workflows that activate when specific data events, such as record creation, updates, or deletions occur in your sync. When the conditions you define are met, Stacksync can send an HTTP request (webhook) or execute a database query, enabling real-time integrations and custom automations across your connected apps.
How do I set up a trigger in Stacksync?
To set up a trigger, go to your Stacksync dashboard, open a sync, and click "Create trigger." You can then configure the trigger by selecting the source app, defining event types (insert, update, delete), and setting custom filters using the no-code editor. The trigger can send data to any HTTP endpoint or run a query in supported databases like Postgres, Snowflake, or BigQuery.
Can I create complex or multiple triggers in Stacksync?
Yes, Stacksync allows you to create unlimited triggers with deep, nested conditions for highly customized workflows. The no-code editor supports advanced logic, and you can add as many triggers as your business needs, there are no system-imposed limits.
What kind of actions can a Stacksync trigger perform?
A Stacksync trigger can perform actions such as sending a webhook to external services (like AWS Lambda, Zapier, or Make), or executing database queries in real time. The payload is fully customizable, and you can map fields between different systems to ensure compatibility, even if column names differ.
How do I prevent unwanted trigger executions in Stacksync?
You can specify a list of fields to ignore when configuring your trigger. If all changes in a record are limited to these ignored fields, the trigger will not fire. This prevents unnecessary executions due to irrelevant system field updates, helping you fine-tune when your automations run.
