Subject: Suggestions for Improving Job Change Tracking in Clay
Hi everyone,
We’ve been working on tracking job changes in Clay but found that the beta job change feature doesn’t fully meet our needs. To address this, we’ve built a custom Claygen table with prompts to verify job changes more accurately. While this works better, it requires manual updates (e.g., monthly) to refresh data.
We’re curious:
- 1.
Is there a way to implement live tracking of job changes instead of relying on periodic runs?
- 2.
Are there any tips to use Clay’s beta job change feature more effectively?
- 3.
Has anyone built or come across a better solution for tracking job changes within Clay?
We’d love to hear your suggestions and experiences!
Thanks in advance!
