[{"data":1,"prerenderedAt":78},["ShallowReactive",2],{"integration-fieldpulse":3},{"id":4,"category":5,"dataDelivered":6,"extension":17,"faq":18,"hero":37,"howItWorks":41,"meta":58,"seo":59,"setup":61,"slug":70,"stem":71,"tagline":72,"tier":73,"tool":74,"whoItsFor":75,"whyItMatters":76,"__hash__":77},"integrations\u002Fintegrations\u002Ffieldpulse.yaml","Field Service Management",{"intro":7,"fields":8,"toolMapping":16},"Every webhook payload from Leaddi carries the full qualified-lead context:",[9,10,11,12,13,14,15],"Customer name and phone number","Issue description and urgency level","Service address","Preferred appointment time","Photos the caller shared (linkable URLs)","Full SMS conversation transcript","Source tag: Leaddi","FieldPulse users typically land Leaddi leads as a new customer + job pair, with source=Leaddi in the notes. Field mapping is flexible — if you prefer leads as estimates or recurring service records, we can match that during setup.","yaml",[19,22,25,28,31,34],{"question":20,"answer":21},"Is the FieldPulse integration included in all Leaddi plans?","Yes. The webhook connector is included on Essential ($229\u002Fmo), Growth ($399\u002Fmo), and Scale ($629\u002Fmo) — no add-on fee.",{"question":23,"answer":24},"Does Leaddi overwrite anything in FieldPulse?","No. Leaddi only creates new records via webhook — never updates or deletes existing customers, jobs, or estimates. If a caller already exists in FieldPulse, the new lead lands as a separate record tagged source=Leaddi.",{"question":26,"answer":27},"What if our FieldPulse setup uses custom fields or job types?","The webhook payload is flexible. During setup we can map Leaddi fields (name, issue, urgency, address, photos) to your FieldPulse field names. A Zapier step between Leaddi and FieldPulse gives you full control for complex mapping.",{"question":29,"answer":30},"How long does setup take?","5 minutes for the standard mapping. Custom mappings or a Zapier middleman may add 10-20 minutes depending on the shaping required.",{"question":32,"answer":33},"Can we turn off the FieldPulse integration if we don't want it?","Yes. Toggle the webhook off in Leaddi's Settings → Integrations. Leads keep flowing to your Leaddi dashboard; they just don't land in FieldPulse.",{"question":35,"answer":36},"Does Leaddi respect FieldPulse's service-area and tag setup?","Leaddi qualifies every missed caller regardless of zone. You can filter inside FieldPulse by address, or use a Zapier step between Leaddi and FieldPulse to drop out-of-area leads before they're created.",{"eyebrow":38,"headline":39,"subheadline":40},"Leaddi + FieldPulse Integration","Leaddi + FieldPulse — Never Lose a Lead to a Missed Call","Leaddi connects to FieldPulse via outbound webhook, so every qualified lead from a missed call lands in your FieldPulse pipeline the same moment it hits your phone. No duplicate entry, no copy-paste — your team schedules, quotes, and invoices from where they already work.",[42,46,50,54],{"title":43,"description":44,"icon":45},"Missed call detected","Leaddi catches the missed call within seconds and the AI texts back from your business number.","i-lucide-phone-missed",{"title":47,"description":48,"icon":49},"AI qualifies over SMS","In about 30 seconds, the AI captures name, issue, urgency, address, preferred time, and photos where relevant.","i-lucide-message-square",{"title":51,"description":52,"icon":53},"Lead delivered via webhook","When the lead is qualified, Leaddi fires an outbound webhook with the full lead payload to your FieldPulse endpoint.","i-lucide-zap",{"title":55,"description":56,"icon":57},"Your team works the lead in FieldPulse","The lead lands as a new customer or job in FieldPulse tagged source=Leaddi. Your team dispatches and quotes in their normal flow.","i-lucide-clipboard-check",{},{"title":38,"description":60},"Leaddi connects to FieldPulse via webhook — qualified missed-call leads land as new customers and jobs with source=Leaddi. Included on every plan.",{"timeEstimate":62,"steps":63,"docsHref":69},"5 minutes",[64,65,66,67,68],"In FieldPulse, identify the endpoint you want new leads to land at (FieldPulse API or a Zapier middleman)","In Leaddi, go to Settings → Integrations → Webhooks → Add FieldPulse","Paste your FieldPulse endpoint URL and any required auth headers","Pick your payload shape: customer-only, customer+job, or estimate","Send a test webhook from Leaddi to confirm the lead lands in FieldPulse","#","fieldpulse","integrations\u002Ffieldpulse","Leaddi connects to FieldPulse via outbound webhook — qualified leads land as new customers the same moment they're delivered to your phone.","webhook","FieldPulse","SMB home-service operators running on FieldPulse — trades with 1-10 technicians across plumbing, HVAC, electrical, garage-door, appliance repair, and similar. Especially useful for shops growing through word-of-mouth where every missed call is a potential referral lost. If FieldPulse is your operational hub, Leaddi fills the gap it can't cover: answering the phone.","FieldPulse handles the ops work beautifully — scheduling, dispatch, invoicing, payments. But FieldPulse can't answer the phone while you're on a job. The average SMB contractor loses $2,000-$6,000\u002Fmonth to missed calls; Leaddi recovers those calls, qualifies the lead, and hands it to FieldPulse so your team doesn't have to check a second dashboard. No new muscle memory, no missed hand-offs.","nV2tdU_dBrKLJoL9fWGmdIucwwWAc6quzkYRM9fLwtU",1776888301172]