Guides › Integrations
Connect a CRM Send scored, tagged leads into your CRM on a schedule — each lead once, with no CSV exports. Find it: Settings > Scheduled Jobs. use “Connect a CRM”; you'll either approve access or paste a key into Automations → Secret Vault Before you start: An administrator role in LeadLogiX, and enough rights in the CRM to approve access or issue a key. Lead Tags set up first, if you want to send only some leads — a sync job picks the tags it covers. For a key-based CRM: the credential in Settings → Automations → Secret Vault before the job runs.
Pick your tab Salesforce and HubSpot : you approve access in their own sign-in window, the credential is stored for you encrypted, and two jobs are created — leads out, closed deals back in. Any other CRM: a webhook , with its key in the Secret Vault. Every sync job is created switched off, and each CRM connection can be limited to one line of business ( how ). Salesforce
Salesforce, start to finish Both routes end with leads landing on your Lead object. Press Connect Salesforce Settings → Scheduled Jobs → Connect a CRM . Approve access in the Salesforce window — with a user who can add fields; a System Administrator is the simple answer. Two jobs appear, both switched off: Salesforce Lead Sync (leads out) and Salesforce Insights (closed deals back). Open the Lead Sync job and press Add LeadLogiX fields to Salesforce The one step that is not automatic — Add LeadLogiX fields to Salesforce adds fields to your Lead object, so we ask first. Safe to press twice. Put the fields on your Lead page layout In Salesforce: Setup → Object Manager → Lead → Page Layouts , edit your layout, drag the LeadLogiX fields on, Save. Put LeadLogiX Lead URL near the top. Pick a cadence and enable one job or both The Lead Sync's last run reports how many leads it sent. Skip the layout step and a synced lead looks empty Salesforce does not add new fields to a layout. Every value is on the record — in reports and list views — but not on the Lead screen until you drag it there. Other Salesforce profiles may also need the fields made visible by your admin; they are made visible to the person who connected. Building the job yourself instead: New job → CRM Sync → provider Salesforce , then the job form's Connect button, then step 2 above. Use it for one direction only, a specific schedule, or a tag filter from the start.
Two ways leads reach Salesforce Chosen on the Lead Sync job. Option What happens Direct to Salesforce Recommended, and the default for new jobs. LeadLogiX writes Leads using the connection you approved — no Apex class, no middleware, no URL to find. Send to my own endpoint Each batch is posted to a URL you own — an Apex REST service or your middleware — for orgs that route all inbound data through something they control. Existing jobs keep whatever they were set to. Your own endpoint must be inside your own Salesforce org A destination outside Salesforce is refused: your Salesforce access would otherwise be handed to whatever service you named. Use an endpoint in your org, or switch the job to a credential that belongs to where you are sending. What LeadLogiX adds to your Lead object Add LeadLogiX fields to Salesforce creates 44 fields on your Lead object — the quality score and its label, the role and journey stage, the recommended channel and follow-up window, the vetting verdicts, consent, your line of business and its own facts, your tags, the customer's history across every conversation, a link back to the lead in LeadLogiX and one to the customer profile. It only ever adds: pressed twice, it reports what was already there. Every field is prefixed LeadVal_ and suffixed __c , so they sort together and never collide with a field your org had. LeadLogiX writes only these — never a standard field, another tool's field, or one you created. Group Count What it carries Identity 1 The key, LeadVal_Lead_ID__c — matched on every send so a repeated run updates the same Lead instead of creating a second. The sync will not start without it. Scoring 4 Quality index, quality label, suppression flag, billing status. Qualification verdicts 5 Intent, financial, geographic, authenticity and security — each the engine's own verdict. Working the lead 7 Role, journey stage, financing status, contact consent, contactability tier, recommended channel, follow-up window. Line of business 3 The line, the facts that line asks about, and what the budget figure means in it. Commercial 4 Lead price, budget amount, budget currency, service interests. Narrative 4 Business summary, AI brief, deficiencies, identity note. Links and tags 2 Lead URL — the conversation, how it was scored and the evidence — and tags. Customer Profile 14 The person behind the lead, including the profile URL — see Customer Profiles ride along . A field with no value is not written, so a lead with no profile leaves the profile fields blank — which is why a freshly connected org sees fields appear before it sees them populated. Your edits win. Correct a misheard name, fix a phone number or write notes in Description and the next sync will not write over them. A blank field still gets filled; what LeadLogiX works out itself — the score, the verdicts — keeps updating. The run notes name the fields it left alone. HubSpot
HubSpot, start to finish One connection, two jobs: leads out, closed deals back in. Press Connect HubSpot Settings → Scheduled Jobs → Connect a CRM . Approve in the HubSpot window, choosing the account leads should land in. Two jobs appear, both switched off: HubSpot Lead Sync and HubSpot Insights. Open the Lead Sync job and press Add LeadLogiX properties to HubSpot Add LeadLogiX properties to HubSpot is safe to press again; it only ever adds. Put the properties you care about on the contact record In HubSpot: Settings → Objects → Contacts → Record customization . They are grouped under LeadLogiX . Optionally turn on deals, then enable the jobs Deals are off by default; on, each lead also creates a deal linked to the person's contact. Skip step 3 and a synced contact looks empty The contact sidebar shows a handful of default properties. Everything LeadLogiX sent sits behind View all properties — present, and usable in lists, filters and reports. Deals are opt-in, and the choice is made at connect time Deal properties are only created if you asked for them when connecting. Turning them on later means running the connection step again so the properties exist before a send references them. What LeadLogiX writes into HubSpot Contacts — one per person , matched on email address: a second conversation updates the existing contact. A lead with no email gets its own contact, because guessing that two anonymous conversations are the same person is how CRMs fill with wrong merges. HubSpot records a person, not a conversation. Deals — one per conversation , optional, carrying the scoring and evidence that justify them. A new deal enters your pipeline's first stage and stays until someone moves it — sort on LeadLogiX LQI and LeadLogiX Quality Label instead of reading quality from the stage. The deal amount is left empty on purpose: LeadLogiX cannot know what the opportunity is worth, and filling it with what the lead cost would make your pipeline total read as your LeadLogiX spend — which Insights would then read back as revenue. Your edits win. A later conversation can fill a blank field but never replaces something you put right — and once a deal exists, its stage and amount are yours alone. Everything lands in a property group called leadval , so it is one collapsible block on the contact record rather than 44 fields scattered through the sidebar; every property is prefixed leadval_ . Contacts get 44 properties, keyed on leadval_lead_id — the same set as Salesforce, field for field. Deals get a deliberate subset of 28: the scoring and evidence, plus the profile id and URL so someone looking at an opportunity can reach the person, without the person-level fields that would be noise on every deal. HubSpot AI agents can read your leads directly Beyond the sync, LeadLogiX publishes a HubSpot app whose Model Context Protocol server lets an agent in Agent Builder query your workspace live — quality index, buying intent, qualification verdict and the journey summary — without the leads having been synced. The sync The MCP server What it does Writes LeadLogiX's fields onto HubSpot records on a schedule. Answers an agent's questions against LeadLogiX, when it asks. Direction LeadLogiX → HubSpot, one way. HubSpot agent → LeadLogiX, read-only. What it needs A connection and a sync job. The LeadLogiX app installed, and a workspace member to approve access. Scope granted Whatever the sync job is configured to send. Read leads without contact details ( leads:read ). LeadLogiX is not in HubSpot's own MCP Client connector list (Notion, Asana, Gong and others); it reaches Agent Builder as an installed app with its own MCP server component — same outcome, different route. The server is read-only and returns no contact details. Developers: MCP hosted server . Webhook (any CRM)
Any other CRM, over a webhook Zapier, Make, or an endpoint you built. Save the key your endpoint expects in the Secret Vault For example CRM_WEBHOOK_KEY — see Secret Vault . Create the job Settings → Scheduled Jobs → new job → CRM Sync , CRM Generic / Raw (full lead document) . Enter the Webhook URL and the Auth Header Secret Webhook URL is your endpoint; Auth Header Secret takes the vault name , not the value. Set batch size, minimum score and tag filters, then the schedule Each run posts qualifying leads to your endpoint; the raw payload includes the full customer-profile snapshot. Enable the job To post leads to an endpoint on a schedule outside CRM sync, use the Call my webhook job or the custom-webhook automation — see Automations & Jobs . Getting results out by API instead: Webhooks & polling . One account per CRM, per workspace Connect again and sign in to a different Salesforce or HubSpot account, and that becomes the account every job for that CRM uses — leads land there and closed-deal figures come from there. Nothing is deleted; reconnect the original account to switch back. LeadLogiX says so on screen and records it in your security log. Reconnecting the same account after an expiry or revocation only refreshes the credential.
What each lead cost is not sent unless you ask A lead's price is visible to admins and procurement only, and most people who open a CRM record are agents — so LeadLogiX Lead Price is created but left empty. Turn on Include what each lead cost you in the Lead Sync job if your whole team should know; it applies to Salesforce, HubSpot and a raw webhook alike. If you added the Salesforce fields before this setting existed, press Add LeadLogiX fields once more so the price field exists — otherwise the sync quietly has nowhere to put the number.
Customer Profiles ride along Your CRM gets the person, not just the lead. A synced lead that belongs to a customer profile carries it: conversation count, first and last seen, latest stage, top score, a compact summary, and a live link to the full profile. HubSpot and Salesforce get these as profile fields — Add LeadLogiX fields creates them at the right type and width, including the long-text summary — and the raw webhook gets the full snapshot object. How profile fields behave The fields are a labelled point-in-time snapshot and never blank while something is known. The AI-written summary is used once ready; until then stable facts, preferences and recent context carry what LeadLogiX assembled from the conversations, and a summary state field says which you are reading. The live link is the freshness channel — the record never needs re-sending to stay useful. Profile text is capped to fit a CRM field. When it does not fit, whole entries are kept and the field ends with … (+2 more) rather than stopping mid-sentence.
Insights: calibrate value from closed deals Read-only. It never writes to your CRM. The Insights job reads your closed deals daily and turns them into the expected-value figure on your leads. Set-up, line-of-business mapping and what to do when the figure is blank: CRM Insights .
Which of your people are in the CRM Read-only. It answers a question you can otherwise only check by hand. Once a day LeadLogiX reads the list of people in each connected CRM and matches them by email to your team. The result is the In CRM column in Organization → Workspaces & Users — one chip per connected CRM on each agent and procurement member. Hover a chip for the reason and when it was checked. What you see What it means What to do In CRM Found, their account is live, and work can be assigned to them. Nothing. Disabled Found, but the account is switched off or archived in the CRM. Re-enable them in the CRM, or expect anything routed there to go unread. Not a seat The matching entry isn't a person — an integration account, or a shared queue. Match them to their own CRM user instead. Ambiguous More than one CRM user has this email address. Tidy the duplicates in the CRM. LeadLogiX won't guess which one is them. Not in CRM We checked, and nobody in that CRM has their email address. Add them, if they're meant to be working leads there. Unverified We couldn't check — the CRM was unreachable, or the connection has no permission to read its people list. Usually a reconnect. Hover the chip for the reason. “Unverified” is not the same as “not in the CRM” Unverified means the last check did not complete and says nothing about the person; only Not in CRM means we looked and they are not there. HubSpot connections made before this feature lack the permission to read people, so they show Unverified until you reconnect HubSpot. Salesforce needs nothing extra. A dash instead of a chip means the member is an admin (admins are not checked) or no CRM is connected. Each CRM is shown separately — someone can be live in one and absent from another.
How duplicates are avoided Every lead is sent with a stable id, and a per-lead marker is written only after your CRM confirms it received it; the next run skips anything marked. So each lead reaches your CRM once , even across overlapping or retried runs, and your CRM matches on the id to update rather than duplicate. You'll know it worked: The sync job's last run reports how many leads it sent, and the records exist in the CRM with LeadLogiX's fields filled in. A run that reports zero sent and no error means the filter matched nothing — check the tags before suspecting the connection. Zero sent, no error The job's tag filter or minimum score matched nothing in its window. Check the tags first. Nothing is reaching the CRM at all The sync job is still switched off — both CRM jobs are created that way. Then check the connection has not expired (reconnect the same account), and the line-of-business scope on the job. A synced lead or contact looks empty Salesforce: the fields are not on your page layout. HubSpot: the properties are not on the record view. Add LeadLogiX fields fails The Salesforce user who connected cannot add fields. The connection still works, but the sync cannot run without the fields — reconnect as a System Administrator. Leads are landing in the wrong account Somebody connected a different account. Reconnect the original one. A rep is not getting leads in the CRM Check their In CRM chip: Not in CRM, Disabled, Not a seat or Ambiguous each explain it. The CRM is waiting for leads that exist If an AI-brief automation is on, CRM sync holds a lead until its brief is written, for up to six hours by default — see AI briefs .