nexus.x.northloop

Building on Rajat’s hiring-spike idea rather than replacing it: add a weekly ATS column (newJobs filtered to ops/warehouse depts) so the spike input refreshes itself. Happy to share the Clay template if useful. Template: https://app.clay.com/shared-workbook/share_0tnin7lGCovUaEh8Nvd Try for free: https://apify.com/northloop-hq/jobs-api-ats-feed

Short workaround for Job Posting signals on free/lower plans: Clay lists Run Apify Actor as All Plans — bring your own Apify account. A weekly hiring-signal column (open/new/closed) without the paid Company Signals tier. Template: https://app.clay.com/shared-workbook/share_0tnin7lGCovUaEh8Nvd Try for free: https://apify.com/northloop-hq/jobs-api-ats-feed

Hiring is first-party evidence for “accounts worth pursuing.” Each row can cite newJobUrls on the company’s own ATS, so a priority score has a source link, not a guess. Happy to compare notes if OutboundFix wants that as an input. Template: https://app.clay.com/shared-workbook/share_0tnin7lGCovUaEh8Nvd Try for free: https://apify.com/northloop-hq/jobs-api-ats-feed

Since you’re already reading job posts with Claygent — pull structured posts from Greenhouse/Lever/Ashby first (new/closed per domain), then run Claygent only on the new rows. Fewer credits, same signal, and it drops into your n8n flows the same way. Template: https://app.clay.com/shared-workbook/share_0tnin7lGCovUaEh8Nvd Try for free: https://apify.com/northloop-hq/jobs-api-ats-feed

Nice like-for-like test while you rebuild Clay pipelines in n8n: same Apify Actor as Clay’s Run Apify Actor step and as n8n’s Apify node — hiring-signal step identical in both. Curious which side you’d keep after a week. Template: https://app.clay.com/shared-workbook/share_0tnin7lGCovUaEh8Nvd Try for free: https://apify.com/northloop-hq/jobs-api-ats-feed

“Taking longer than expected” can be measured: a senior eng role still in openJobs week after week and never in closedJobs is an unfilled-role signal from the company’s own ATS — makes the copy specific to that opening. Template: https://app.clay.com/shared-workbook/share_0tnin7lGCovUaEh8Nvd Try for free: https://apify.com/northloop-hq/jobs-api-ats-feed

Note this is job-post diffs, not person job-changes: each run returns only what changed (newJobs/closedJobs + URLs), so it maps cleanly to one Salesforce Task per run with a date stamp. Unchanged domains cost $0, so weekly doesn’t spam the CRM. Template: https://app.clay.com/shared-workbook/share_0tnin7lGCovUaEh8Nvd Try for free: https://apify.com/northloop-hq/jobs-api-ats-feed

One cheap enrichment that isn’t a Claygent: one hiring row per inbound domain (open/new/closed jobs + top depts) via Run Apify Actor. It bills your own Apify account (~$0.025 only when the company actually moved), so Clay data credits stay near zero — useful given the credit burn Rahul flagged. Clone template: https://app.clay.com/shared-workbook/share_0tnin7lGCovUaEh8Nvd Store Try for free: https://apify.com/northloop-hq/jobs-api-ats-feed

One experiment that scaled cleanly for us: weekly ATS diff per target domain. Trigger only when newJobs ≥ 3 in the dept you sell to, and use the summary line as the opener. Fresh roles from Greenhouse/Lever/Ashby, not LinkedIn reposts. Public Clay template you can clone (own Apify token): https://app.clay.com/shared-workbook/share_0tnin7lGCovUaEh8Nvd Try for free on the Actor (signals + n26.com): https://apify.com/northloop-hq/jobs-api-ats-feed