Stephanie H.

You can also try the look up and send table data options, depending on the format of your data and use case

And new market entrants like https://0.email/ could help avoid called email altogether

This was an experiment restricted to certain accounts that overflowed by accident. They’ve ended the experiment and have apologised for the inconvenience as well as refunded people who were incorrectly charged. There’s a longer post and update on the creators channel.

Favikon and Influencers Club

Not sure on this round, but make a note for next time to import it as a an additional column in your CSV already

Hey Nat A.your first workbook 'prototype' will likely be messy, but as Satiesh S. said in a Linkedin comment this week, your ROI = wisdom!!! Head of GTM Engineering at Clay said in an interview a while back to deploy one signal per table, and I love this suggestion. I'm developing prompts to help me think through these kinds of questions, here's the response for your query, which is how I'd approach it initially:

Once you've built the workflow and seen how 10 rows cascade across the tables, you'll get a better idea of how the workflow should be designed. It always comes back to "what is my end goal" and what do I want it to look like.

Define the intent signals and then build agent prompts to find them.

Product roundups in the clay-announcements channel, and - just as you did - following others who share the features they use/ discover (I shared sandbox yesterday, clay navigator 2x weeks ago etc)

woah those are some amazing product updates!!