Hiring Clay Operator for Building Custom Data Engine and API Integration with FlowChat OS

Hey everyone, I’m the VP of Sales at FlowChat (a Smart Messaging OS built for scaling social media DM outreach). We recently launched a premium Done-For-You (DFY) service for our users, and we need a lethal Clay operator to build our backend data engine on a per-client basis. The Tech Stack: Clay \rightarrow HTTP API Webhook \rightarrow FlowChat OS (via JSON payload) What You Will Do (Per Client Setup): • Build Custom Tables: Take our client's ICP and build the initial lead list. • Construct the Waterfall: Optimize for cost and accuracy. • Social URL Enrichment (Crucial): Because FlowChat executes via social DMs, your waterfall must prioritize finding and verifying clean social media URLs (LinkedIn, FB, IG, X). Email is secondary for us. • The Payload: Configure Clay’s HTTP API column to webhook a perfectly formatted JSON payload directly into FlowChat’s open API. The Structure & Pay: • This is a part-time/freelance role to start. We pay a flat fee per client setup + a monthly maintenance retainer per client. We can discuss rates in the DMs based on your experience. • Long-Term: We are scaling fast. If you crush the freelance builds, there is a clear path to transition into a fractional "Head of Outbound Data" role to oversee the offshore operators we eventually bring in-house. How to Apply: Shoot me a DM with the following: 1. A brief overview of your experience building API/Webhook payloads out of Clay. 2. The answer to this technical filter: If a client's table has a "LinkedIn URL" column and an "Email" column, how do you natively configure the HTTP API webhook inside Clay to ONLY fire if the LinkedIn URL is present, preventing it from sending email-only leads to our OS? Looking forward to building with one of you!