The Start Automation<\/strong> step triggers another automation for the current contact from within the flow you are building. It\u2019s a clean way to reuse existing automations (e.g., onboarding, re-engagement, surveys) without duplicating steps.<\/p>\n Think of it as: "Run that other automation now for this same contact." The current automation continues after this step unless you explicitly design an early exit.<\/p>\n \u2705 Reusability<\/strong> – Centralize common sequences in dedicated automations After adding the step, you\u2019ll see a searchable dropdown with your automations:<\/p>\n When selected, the step becomes valid and can be saved.<\/p>\n When the flow reaches a Start Automation step:<\/p>\n Key points:<\/p>\n Use a \u201cmaster\u201d automation that starts specialized sub\u2011automations:<\/p>\n Overview The Start Automation step triggers another automation for the current contact from within the flow you are building. It\u2019s […]<\/p>\n","protected":false},"author":30,"featured_media":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"footnotes":""},"doc_category":[4],"doc_tag":[],"class_list":["post-9593","docs","type-docs","status-publish","hentry","doc_category-integrazioni"],"year_month":"2026-04","word_count":743,"total_views":0,"reactions":{"happy":0,"normal":0,"sad":0},"author_info":{"name":"Alireza Javaheri","author_nicename":"alireza-javaheri","author_url":"https:\/\/support.spoki.com\/en\/author\/alireza-javaheri\/"},"doc_category_info":[{"term_name":"Integrazioni","term_url":"https:\/\/support.spoki.com\/docs-category\/integrazioni\/"}],"doc_tag_info":[],"yoast_head":"\nWhy Use Start Automation?<\/h2>\n
\u2705 Composability<\/strong> – Build flows from smaller, maintainable building blocks
\u2705 Consistency<\/strong> – Ensure the same logic is applied everywhere
\u2705 Separation of concerns<\/strong> – Keep main flow lean; offload sub\u2011journeys
\u2705 Faster iteration<\/strong> – Update a single automation to improve all callers<\/p>\n
\nHow to Add a Start Automation Step<\/h2>\n
Step 1: Select the Action Type<\/h3>\n
\n
Step 2: Choose the Automation<\/h3>\n
\n
\nHow It Works<\/h2>\n
\n
\n
\nPractical Examples<\/h2>\n
Example 1: Multilingual Onboarding<\/h3>\n
If\/Else: Check language\n IF Italian \u2192 Start Automation: Onboarding (IT)\n IF Spanish \u2192 Start Automation: Onboarding (ES)\n ELSE \u2192 Start Automation: Onboarding (EN)\nContinue current flow \u2192 Tag "onboarding_dispatched"\n<\/code><\/pre>\nExample 2: Survey After Issue Resolution<\/h3>\n
Resolve ticket \u2192 Start Automation: CSAT Survey \u2192 Continue\n<\/code><\/pre>\nExample 3: Payment Flow Composition<\/h3>\n
Start Automation: Payment Request\nDelay: 24h\nIf\/Else: If paid \u2192 Continue\n Else \u2192 Start Automation: Payment Reminder\n<\/code><\/pre>\n
\nBest Practices<\/h2>\n
\n
\nLimitations & Considerations<\/h2>\n
\n
\nTroubleshooting<\/h2>\n
The automation doesn\u2019t appear in the dropdown<\/h3>\n
\n
It started, but messages didn\u2019t send<\/h3>\n
\n
Conflicting updates between automations<\/h3>\n
\n
\nDesign Patterns<\/h2>\n
Pattern 1: Orchestrator + Workers<\/h3>\n
Orchestrator \u2192 Start Automation: Lead Enrichment\n \u2192 Start Automation: Qualification\n \u2192 Start Automation: Nurture (EN\/IT\/ES via Branching)\n<\/code><\/pre>\nPattern 2: Re\u2011usable Surveys<\/h3>\n
After any service completion \u2192 Start Automation: CSAT Survey\n<\/code><\/pre>\nPattern 3: Multi\u2011Step Recovery<\/h3>\n
Start Automation: Payment Request\nIf unpaid after delay \u2192 Start Automation: Payment Reminder\nIf still unpaid \u2192 Start Automation: Assistance Handoff\n<\/code><\/pre>\nPattern 4: Conditional Handoff<\/h3>\n
If\/Else: High LTV AND VIP tag \u2192 Start Automation: VIP Concierge\nElse \u2192 Continue standard flow\n<\/code><\/pre>\n
\n","protected":false},"excerpt":{"rendered":"