{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/6795c4fde6904ec7967935e07fde52c8\" frameborder=\"0\" width=\"1920\" height=\"1440\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1440,"width":1920,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1440,"thumbnail_width":1920,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/6795c4fde6904ec7967935e07fde52c8-9ab0c56ddcd7a5e5.gif","duration":448.149,"title":"Page 1, Page 2 &amp; Brief Template Subscenarios (Walkthrough)","description":"This Loom explains how the Funnel Brief and Express Funnel automations use external scenario nodes and HTTP requests to create and run funnel brief tasks. It shows that a webhook is triggered using an Airtable funnel record ID, first fetching the funnel and account connection, then selecting one of about eight or nine document templates based on funnel shape types such as free resource, live event, new follower, and evergreen or direct purchase paid product (as of July 13). For the brief workflow, page one creates tasks using submission date anchors and page two quality checks copy and coordinates mini chat and integrations before launch, with due dates tied to submission date and launch date. The author notes the existing task system remains as a seamless handover between systems until it is no longer needed."}