Understanding Automation Tables vs. Workbooks for Webinar Leads

Léa H. · 2025-08-05T08:53:54.904Z

I’ve started to work on an automation table to aggregate data around my webinar leads before sending them into sales automation campaigns (lemlist). My problem is that I’ve done it on an automation table instead of a workbook, which means that now I can have multiple views but not multiple tab, for instance - What is the difference between workbook and table? Should I switch now?

Understanding Automation Tables vs. Workbooks for Webinar Leads | Clay

5 comments

· Sorted by Oldest

Clay
APP
·
·
A workbook is a centralized space where you can manage multiple tables together - think of it like a spreadsheet file containing multiple sheets. Key differences: ** Workbook: Contains multiple tables, allows you to organize related workflows together, and visualize relationships across tables ** Table: Individual dataset within a workbook - like a single sheet For your webinar lead automation, switching to a workbook would let you create multiple tables (tabs) for different stages of your workflow - one for lead aggregation, another for processed leads, etc. This gives you better organization for multi-step campaigns before sending to Lemlist. You can create a new workbook and use "write to table" to move your existing data.
Sources: Find Companies [Clay 101] - Clay University Find Companies [Clay 101] - Clay University New at Clay | Clay.com
Léa H.
·
·
should I do write to table or send table data ?
Clay
APP
·
·
Use "Send table data" - it's our newer, improved method for transferring data between tables. Send table data offers two options: ** Send row: Transfers each row as-is to another table ** Send row for each item in a list: Flattens lists by creating separate rows for each item The legacy "Write to Other Table" is still available but "Send table data" is the current recommended approach for routing records between tables.
Sources: Send table data | Documentation | Clay University Write to Other Table | Documentation | Clay University
Léa H.
·
·
can you show me an example of Send row for each item in a list?
Clay
APP
·
·
"Send row for each item in a list" flattens lists by creating separate rows for each item. Example scenario: You have a company table where one cell contains a list of multiple people found at that company. Instead of keeping all people in one cell, you want each person as their own row in a separate People table. What happens: ** Original table: Company ABC has [Person 1, Person 2, Person 3] in one cell ** After sending: Creates 3 separate rows in the destination table - one for Person 1, one for Person 2, one for Person 3 This is useful for flattening lists when you need to work with individual items rather than grouped data.
Sources: Send table data | Documentation | Clay University Send table data | Documentation | Clay University Send table data | Documentation | Clay University

Clay
APP
·
·
A workbook is a centralized space where you can manage multiple tables together - think of it like a spreadsheet file containing multiple sheets. Key differences: ** Workbook: Contains multiple tables, allows you to organize related workflows together, and visualize relationships across tables ** Table: Individual dataset within a workbook - like a single sheet For your webinar lead automation, switching to a workbook would let you create multiple tables (tabs) for different stages of your workflow - one for lead aggregation, another for processed leads, etc. This gives you better organization for multi-step campaigns before sending to Lemlist. You can create a new workbook and use "write to table" to move your existing data.
Sources: Find Companies [Clay 101] - Clay University Find Companies [Clay 101] - Clay University New at Clay | Clay.com
Léa H.
·
·
should I do write to table or send table data ?
Clay
APP
·
·
Use "Send table data" - it's our newer, improved method for transferring data between tables. Send table data offers two options: ** Send row: Transfers each row as-is to another table ** Send row for each item in a list: Flattens lists by creating separate rows for each item The legacy "Write to Other Table" is still available but "Send table data" is the current recommended approach for routing records between tables.
Sources: Send table data | Documentation | Clay University Write to Other Table | Documentation | Clay University
Léa H.
·
·
can you show me an example of Send row for each item in a list?
Clay
APP
·
·
"Send row for each item in a list" flattens lists by creating separate rows for each item. Example scenario: You have a company table where one cell contains a list of multiple people found at that company. Instead of keeping all people in one cell, you want each person as their own row in a separate People table. What happens: ** Original table: Company ABC has [Person 1, Person 2, Person 3] in one cell ** After sending: Creates 3 separate rows in the destination table - one for Person 1, one for Person 2, one for Person 3 This is useful for flattening lists when you need to work with individual items rather than grouped data.
Sources: Send table data | Documentation | Clay University Send table data | Documentation | Clay University Send table data | Documentation | Clay University