{"id":30529,"plugin_id":"plugin_asdk_app_6ac2279f7a9c8191abc34801f091a7eb","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-09T06:04:52.229Z","digest":"a95e6e3ce6768095e2eb87fffb12dceaf677bab755cd8c02bda67b7ffe158bdc","against":null,"payload":{"description":"Design, preview and test-drive an event-triggered email automation in Send & Retain, and enable it only on the user's explicit go-ahead. Use when the user wants welcome emails, cart recovery, win-back or any automation that sends on an event.","included_files":[],"name":"design-an-automation","skill_md_contents":"---\nname: design-an-automation\ndescription: Design, preview and test-drive an event-triggered email automation in Send & Retain, and enable it only on the user's explicit go-ahead. Use when the user wants welcome emails, cart recovery, win-back or any automation that sends on an event.\n---\n\n# Design an automation\n\n1. Resolve the company (`email_list_projects`) and agree the design: the\n   trigger event, the exit event, who it is for (filters, and priority when\n   variants compete), the cadence (delays, send windows) and which template\n   each step sends. Author missing templates first (`author-a-template`).\n   Confirm the company's app actually emits the trigger event.\n2. `email_create_automation`. It is **always created paused** and returns a\n   readable timeline. `email_preview_automation` renders every send step, so\n   the user sees the real emails before anything is enabled.\n3. Test-drive: `email_upsert_contact` a test contact (the user's own address,\n   with realistic attributes including timezone), `email_emit_contact_event`\n   with the trigger, then `email_list_automation_runs` to confirm enrolment and\n   timing. Emitting an event can send real mail to that contact, so say so\n   before calling it.\n4. `email_pre_launch_check`, then walk the remaining items: every template\n   published, suppressions imported if the company is migrating, and volumes\n   sensible for the domain's age.\n5. Enable with `email_set_automation_status` only when the user explicitly\n   decides to, in this conversation. Then watch the first cohort with\n   `email_get_automation_metrics`.\n\nAdding steps to a live automation never disturbs contacts already in it; inserting,\nmoving or removing a step requires pausing first.\n\nFor each rendered email, open its `previewUrl` in the client browser panel when\navailable, or show a clickable link. Links expire after 15 minutes; anyone with\nthe link can view the sample. A preview does not send mail or enable a flow.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}