Job Change Signal: Row-by-Row Processing in Main Clay Table
Can I run job change signal row by row on a clay table, I don't want the signal intent to create a new table, I want the results in the main table.
Can I run job change signal row by row on a clay table, I don't want the signal intent to create a new table, I want the results in the main table.
Job Change Signals automatically create a new table with job change data - this is how the feature is designed to work. The signal monitors your existing table and when job changes are detected, it creates a separate table with the job movers, their LinkedIn profile URLs, new company, previous company, and start date. To get job change data into your main table, you can use our "write to table" feature to send the job change results back to your original table after the signal runs. This allows you to append the job change data to your existing records rather than keeping it in a separate table. Are you looking to update existing rows in your main table when job changes are detected, or add new rows with the job change information?
Sources: Monitor for job changes | Documentation | Clay University Monitor for job changes | Documentation | Clay University Monitor for job changes | Documentation | Clay University Claybooks: Signals: Monitor job movers across the entire market | Clay.com Claybooks: Signals: Monitor job changes at target accounts | Clay.com Write to Table [Clay 101] - Clay University
How can i get this data back into the main table?
Job Change Signals always create a new table by design - this cannot be changed. However, you can enable "Update outdated rows" when setting up the signal, which will add new rows to your original table if a contact's current company no longer matches your records. To get job change data back into your main table after the signal runs, use our "write to table" feature to send the results from the job change signal table back to your original table.
I dont want to write it to table, I want it to update the existing row data
Job Change Signals are designed to create a new table by default and cannot update existing rows in your main table directly. However, you can enable "Update outdated rows" when setting up the signal, which will add new rows to your original table if a contact's current company no longer matches your records. This is the only way to get job change data back into your main table automatically - the signal will add new rows when it detects company mismatches, but it cannot modify existing row data.
Hey Jamie, results from signals will always show up in a new table as a separate event. So there's no direct way to keep them in the same table (like in a new column). Can you tell me more about the need / use case here?