Incorporating Clay for Efficient Recruiter Workflow: Job Postings and Contact Identification

We have a saas product that scores candidate backgrounds on Linkedin to help with recruiter efficiency and we would like to incorporate Clay to help our recruiters workflow to identify job postings that are relevant to the types of roles they recruit for and serve up the contact name/title with the ability to get the contact information based on titles they would generally prospect to to sell recruiting services. Our ideal workflow would be: 1. User inputs the job posting info they’re interested in. Whether we do that in our saas product or Clay I’m not sure that matters if we can link out to the Clay interface somehow 2. User inputs the job titles they’re interested in selling recruiting services to 3. Our saas product pulls from Clay which job postings and contacts would be relevant to selling recruiting services to 4. Our saas product serves this up to the users in the form of a feed 5. Our saas product users watch the feed and determine if they want to conduct outreach to a contact. Our saas product uses Clay to find the contact data thus consuming credits and re-billing our saas product customers for those credits. Is this doable? If so, how would we go about setting this up.