Benjamin L.

Will there be a recording?

Saw Weston C. say

no more need to send table data between tables in a workbook since you can combine sources in workflows

Was wondering how we do this?

Workflows: Drag and drop Clay tables accessible and editable via CLI Functions: Tables that can be ran within tables or workflows, also accessable via API, but only if pre-created

Gotcha! But as I say, only plan is to keep Workflows a CLI product?

Giving this a try now to see what UI looks like! But no plans for each Clay integration (Like Claygent) to be available via API, right? Orchestration like that should be done via CLI via Workflows so people essentially don't dupe Clay using lots of APIs haha?

From my understanding of the docs, Workflows is CLI/Plugin only? No plans to add to the UI? Conceptually, the solution to using Clay at scale instead of the native MVP or exposing every Clay enrichment as an API endpoint. Talk to the agent, tell it to add nodes (enrichments/agents/code) and it'll run it on your list through Clay, but it never appears in UI as a table, that'd be the Enterprise table function. Is that right? Weston C.

Are workflows available now? I thought they were to be released in future weeks Also, do they literally build Functions, or they act the same way Functions do but in a theoretical sense through the CLI/MCP as opposed to a physical build inside of Clay? If theoretical, is the plan to make it physical? If so, what's the difference between that and a Function? Lots of questions haha Bruno E.

Are all features on new plans only or legacy?

Looking forward to it! What's Workflows going to be?

DMd