Triggered Automations That Don't Duplicate
Give the trigger a unique key and a lookup before it writes, so a record that fires twice never becomes two rows.
به چه درد می‌خورد
تریگر بیشتر از آنچه فکر می‌کنی فعال می‌شود و گاهی روی یک رکورد دو بار. اینجا می‌گوید پیش از روشن کردن خودکارسازی کلید یکتای رکورد را مشخص کن، کل زنجیره را دستی روی یک رکورد بیازما، و هرگز نگذار خودکارسازی داخل همان منبعی بنویسد که تریگر تماشایش می‌کند. جلوی شیتی را می‌گیرد که دوشنبه صبح همان دوازده لید را سی بار تکرار کرده.
خود اسکیل
Assume the trigger will run more often than you expect, and sometimes twice on the same record. Design for that before you turn it on. Set it up: - Write down the one field that makes a record unique: profile URL, order id, email. If you cannot name one, you are not ready to automate this. - Build and test the whole chain as a manual run first, with the trigger not yet attached. A broken step is cheap to find on one record and expensive to find on four hundred. - Point the first test at a scratch sheet or scratch database, never the live one. Make it safe to run twice: - Look up the unique key in the destination before you write. Update when it exists; create only when it does not. - Where the destination cannot look up, read the existing keys into a list first and skip anything already there. - Never let the automation write into the same source its trigger watches. That is a loop, and it runs all night. Before you walk away: - Run it once and confirm exactly one new row appeared. - Wait for one real trigger cycle and check again. Two rows for one record means the dedupe is not working. Fix it now, not after the weekend. - Add a step that notifies you on every run for the first day, then remove it. A runaway you can see on day one costs nothing. The failure this prevents: Monday morning, the same twelve leads repeated thirty times, and a night of billable runs you cannot get back.
نصبش چطور است
1. Open the tool and start a new conversation, project or template. 2. Paste the text below wherever the tool keeps standing instructions — usually called system prompt, instructions, or persona. 3. Save it so it applies to every run rather than a single message.