Website Leads Into AccuLynx: Six Roofing Forms and the Order of Operations Behind Each

The shared inbox that everyone calls the integration

On many roofing sites the form does one thing: it emails an address three people can read. Somebody copies the name into AccuLynx when they get a minute, picks a lead source from memory and types "from website" in the notes. On a quiet Tuesday this works. In a storm week the inbox becomes a job board nobody owns, and a lead source report that says Website for half the year cannot tell you which page, ad or postcard earned the call. The AccuLynx integration hub covers everything a site can connect; this page is about forms.

A roofing site usually carries six forms, and each deserves its own route into AccuLynx.

No single create-lead call, and why AccuLynx's sequence is the right one

AccuLynx removed its V1 documentation and recommends V2, where leads are created with the Create Job endpoint. A lead is simply a job in the Lead milestone. AccuLynx publishes a guide, Create a Lead/Job from a Third-Party System, that sets the order, and we follow it closely, because each step exists to prevent a specific mess.

1. 1.Search before creating. The server searches AccuLynx's contacts for a match and creates a contact only when nothing turns up. Skip this and every repeat visitor becomes a second copy of herself.
2. 2.Set the contact type. If none is sent, AccuLynx defaults to Customer. That suits homeowners and may not suit a property manager your office files differently.
3. 3.Look up the IDs. Lead source, job category, work type and trade type are each sent as an ID fetched from your account, never as typed text. AccuLynx's guide is blunt about it: "Do not pass configured values as free text."
4. 4.Create the job. It lands in the Lead milestone with no assigned rep, linked to the contact as its primary contact, with the property address, priority and notes.
5. 5.Add what comes after. An initial appointment if the form booked one, a job message for anything over 1,000 characters, a sales rep if you route by rule, and custom fields if you track ad clicks.

The guide also tells integrators to store the contact ID, the job ID, their own lead ID, the lead source ID and sync timestamps. We keep all five in the site's log, which is how anyone in your office can trace a submission to its job months later without filing a support ticket.

The field map, from form question to AccuLynx field

Before any code, we agree a field map with your office: each question on each form, the AccuLynx field it fills and the rule that decides the value. This is the map we start from. It uses only fields AccuLynx documents on its Create Contact and Create Job references and its lead source endpoint.

Two notes on that map. Lead sources must already exist in AccuLynx, and only active ones come back from the API, so the office creates them first, including child sources under a parent for each campaign you want to tell apart. And ad click IDs have no standard home: we store the Google click ID in a job custom field or the notes, as our marketing attribution guide explains. Texting consent and AccuLynx's opt-out data are covered on the SMS page.

Repeat visitors, junk submissions and the double-clicked submit button

A connected form takes on a new duty: whatever it sends lands in the Lead milestone, where people triage it every morning. Spam an inbox once absorbed now eats a coordinator's morning and teaches the office to distrust the website. So the cleaning happens on our server first.

• Server checks, every time. The browser's checks are a courtesy that bots skip. The server checks again: a ten-digit phone, a street address, a message that is not a list of links.
• Quiet bot traps. An invisible field only bots fill, and a minimum time on the page before submit. No puzzles for a homeowner reading the form on a ladder.
• One submission, one job. Each submission gets an ID on the site before it is sent. A double-clicked button or a retried send finds the ID already used and stops, so AccuLynx never receives two jobs from one form.
• Returning homeowners. When the contact search finds her, the new job hangs on her existing contact. Whether a second form inside a week becomes another job or a message on the first is your office's rule, written into the field map.
• A holding pen for the doubtful. A submission that fails a soft check waits in a review list on the site, out of AccuLynx and out of the trash.

AccuLynx's in-app lead form now shows possible matching records as staff type, per its Spring 2026 update; the website should be just as careful. Forms that have stopped sending entirely are a job for our form repair service.

Rate limits, timeouts and a lead that waits its turn

AccuLynx publishes rate limits in two places, and the numbers do not match. Its Rate Limits guide describes an IP-based limit of 30 requests per second, a ban "on the order of 30 seconds to a few minutes, typically" for exceeding it, and 10 requests per second per key afterward. A changelog entry instead puts POST, PUT and DELETE endpoints at 6000 requests per hour and 12000 per day, answering 429 Too Many Requests over the limit and recommending exponential backoff. We respect both and assume neither replaced the other. One form needs only a handful of calls, so an ordinary week never comes close; a storm week might. That is why every send runs from a queue.

1. 1

   Saved before it is sent

   The submission is written to the site's database under its own ID before any call to AccuLynx, so a lead never exists only in transit.

2. 2

   Sent from the server

   The key lives in server settings. AccuLynx's docs warn that anyone holding a key can expose or change company data and say to treat it like a password. It never reaches the browser.

3. 3

   Backed off on a 429

   If AccuLynx answers Too Many Requests or times out, the queue waits longer before each retry, as AccuLynx recommends.

4. 4

   Logged in plain words

   Each attempt is recorded with the contact and job IDs AccuLynx returned, in a log someone who is not a developer can read.

5. 5

   Handed to a person

   After repeated failures, an alert names the form, the error and the homeowner's phone, so the office can call her while the fix happens.

AccuLynx's built-in capture, its partners, and when a zap will do

Check whether you need a custom connection before paying for one. As of October 2026, AccuLynx's plan page lists "Embedded web forms" as an Elite-only feature. The only public description we found is a 2021 AccuLynx post saying you can embed a custom form on your website that creates a lead once a visitor fills it out. No setup article is public, so we cannot tell you how it embeds or what it collects; your AccuLynx rep can.

Other documented routes, as of October 2026: AccuLynx's native Zapier app has a Create Lead action and uses an AccuLynx API key. The CallRail AppConnection turns tracked calls and form submissions into unassigned leads, writing the lead source, form name, tracking number and campaign into the notes. RoofQuote PRO by Roofle captures website quote requests as unassigned leads. AccuLynx also lists Angi Leads, SalesRabbit and Spotio as lead partners, and Jotform says its own integration turns each submission into an AccuLynx lead.

The plugin and Zapier trade-offs get a full page in WordPress vs custom for AccuLynx. If the site itself is the obstacle, moving from WordPress to Next.js covers the rebuild, and the AccuLynx API guide covers what else the connection can read and write.

Which form to connect first, and what the connection costs

Connect the form with the most money behind it first. For most roofers that is the free inspection form on paid landing pages, because it carries the click IDs that conversion tracking setup and PPC advertising depend on. Then the storm form, before the season rather than during it.

For American Roofing & Waterproofing in Phoenix we built a multi-step estimate form and a custom instant-quote tool, and our own LeadBolt software answers website, Google, Meta, Angi, Yelp and phone leads in under a minute. Both are in our work. Neither is an AccuLynx integration, and we do not claim the Phoenix client uses AccuLynx.

Connecting forms on an existing site is quoted after a free review, and our API integrations page puts a typical two-system connection at one to three weeks. A new site is a fixed price from $1,500 with booking included, and a custom estimate flow is from $575, depending on complexity, on the web design pricing page, with 0% financing at 25% down. Start with a free site audit of your current forms, hold them against the launch checklist, or call (210) 346-0848.