Description
Summary I run a small automation agency. I need a developer who knows CRM integrations to scope, and then build, a sync between AccuLynx (a roofing CRM) and GoHighLevel. THE PROBLEM A contractor sends an estimate. The customer says "let me think about it." Nobody chases. The deal dies of silence. I want follow-up sequences in GoHighLevel to start automatically from CRM state — with no human having to move, tag or flag anything. The hard part: webhooks fire when something happens. My problem is that nothing happens. The system needs to hold its own clock and act on elapsed time with no qualifying event, while still reacting immediately when a real status change arrives (a signed job must never receive a chase). PHASE 1 — THIS CONTRACT A paid discovery spike, roughly 4–8 hours. Deliverable is a short written technical assessment covering: · The actual AccuLynx webhook event list and API capability, evidenced against official vendor documentation — not marketing or directory pages. · Whether job status / milestone data is granular enough to isolate a "quoted, awaiting customer decision" state from all other states. · Whether a free-text note field is readable via API, or whether a structured custom field is required. · Recommended approach to inactivity detection: polling versus event ingestion with state held our side. · How an inbound status change reliably suppresses or exits an in-flight GoHighLevel sequence, and worst-case latency. · Rate limits, auth model, and anything that would block or complicate the build. · Your phase 2 build estimate, in hours. PHASE 2 — SEPARATE CONTRACT, IF PHASE 1 GOES WELL Build the integration. The GoHighLevel side already exists — workflows and sequences are built. I need the pipe and the trigger logic, not the marketing automation. WHO I AM LOOKING FOR · Demonstrable REST API integration work — auth, webhooks, retries, idempotency, error handling. · GoHighLevel / LeadConnector API experience is a strong plus. AccuLynx experience is a bonus, not a requirement. · Comfortable reading vendor documentation and telling me plainly when something is not possible. · Written English good enough to produce a clear technical document I can act on. TERMS · White-label. You work behind me. No contact with my end client at any point. · NDA before any client-specific detail is shared. · All code and IP assigned to me. · Testing in my environments only. No live client credentials during phase 1. TO APPLY — answer these three briefly. Applications that do not will not be read: 1. In one paragraph: how would you detect that a CRM record has had no activity for 14 days, when the CRM emits no "inactivity" event? 2. Name one integration you built where the vendor API could not do what the client wanted. What did you do? 3. What would make you tell me this project should not be built as specified?