{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/b58eed5cb9b142d0ae1659f362adc450\" frameborder=\"0\" width=\"1012\" height=\"759\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":759,"width":1012,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":759,"thumbnail_width":1012,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/b58eed5cb9b142d0ae1659f362adc450-c5eed3638f7a8bc1.gif","duration":443.667,"title":"What are Clay Workflows?","description":"This Loom explains what Clay Workflows are, when to use them instead of tables, and how to understand the triggers and nodes. It defines a workflow as a visual GTM pipeline with a trigger that starts runs, followed by nodes that enrich and reason about records, with branching, code or agent logic, and writing back to audiences. It emphasizes that workflows are best for actions that must run repeatedly without babysitting, such as lead routing and scheduled enrichment, while tables are better for experimenting and spot-checking provider outputs, and workflows do not yet handle waterfalls directly. The walkthrough covers key triggers including new member and segment, segment on a schedule, on a signal via webhook, on a schedule without attached records, run manually for testing, and CSV upload, plus nodes like enrichment, function, claygent, update audience members, conditional branching, and run code with deterministic logic."}