is there a way to easily send filtered rows of a table to a new table?

You can easily send filtered rows to a new table using our "write to table" feature. Here's how: 1. Apply filters to your current table to select the rows you want to send. 2. Use the "Write to Other Table" integration to transfer the filtered data. 3. Select your Clay account and choose a destination table within your current workbook. 4. Map the columns from your filtered table to the new table. 5. (Optional) Configure auto-update settings to keep the new table updated automatically. This process allows you to efficiently transfer specific data from one table to another based on your applied filters.

Sources: Customize your table view | Documentation | Clay University Write to Other Table | Documentation | Clay University

You can use our "write to table" feature to send all columns for a filtered subset to a new table. Here's how: 1. Apply filters to your current table to select the rows you want. 2. Use the "Write to Other Table" integration. 3. Select your Clay account and choose a destination table. 4. In the column mapping step, select all columns from your source table. 5. (Optional) Configure auto-update settings for automatic updates. This process allows you to transfer all columns for your filtered data to a new table efficiently. If you need to adjust which columns are visible in your new table, you can use the Columns view settings to show or hide specific columns as needed.

Sources: Customize your table view | Documentation | Clay University Write to Other Table | Documentation | Clay University

No, you don't have to manually map all columns when sending a filtered subset to a new table using our "write to table" feature. Here's a simpler approach: 1. Apply filters to your current table to select the rows you want. 2. Use the "Write to Other Table" integration. 3. Select your Clay account and choose a destination table. 4. In the column mapping step, enter "/" to skip list selection. 5. Select all the columns you want to copy from the source table. 6. Match these columns to the appropriate columns in the destination table. This process allows you to efficiently transfer all desired columns for your filtered data to a new table without manually mapping each column individually.

Sources: Write to Other Table | Documentation | Clay University Write to Other Table | Documentation | Clay University

When using the "write to table" feature to send all columns for a filtered subset, you should enter "/" in the "Select a list from a column" field. This tells the system to skip list selection, as you're not mapping a list in this case. After entering "/", you can then select all the columns you want to copy from the source table and match them to the appropriate columns in the destination table.

Sources: Write to Other Table | Documentation | Clay University Write to Other Table | Documentation | Clay University

Yes, there's a faster way to send all columns for a filtered subset to a new table using our "write to table" feature. Here's how: 1. Apply filters to your current table to select the rows you want. 2. Use the "Write to Other Table" integration. 3. Select your Clay account and choose a destination table. 4. In the "Select a list from a column" field, enter "/". This skips list selection. 5. You can then select all columns you want to copy from the source table at once. 6. Match these columns to the appropriate columns in the destination table. This method allows you to efficiently transfer all desired columns for your filtered data without mapping them one by one.

Sources: Write to Other Table | Documentation | Clay University Write to Other Table | Documentation | Clay University

Hi Stephane, thank you for reaching out! I understand it's frustrating to manually map each column to the new table. We're actively improving this feature to make it more user-friendly. In the meantime, you'll need to map the columns manually. One important note: the 'Select a list from a column' option is completely optional - you can skip it if you don't need it. I realize the interface doesn't indicate this clearly. Please let me know if I can help you with anything else :) - Smit