STACK PATTERN
HubSpot is the CRM and customer system of record: contacts, companies, deals, tickets, knowledge base, customer portal, marketing and sales automation. eLogii is the routing and field execution layer that takes a HubSpot ticket, deal or custom-object job and turns it into an optimized route, a live ETA, a mobile driver workflow and proof of delivery, then writes the completion data back. Two systems, two jobs. The integration runs over the HubSpot API on one side and eLogii’s REST API on the other, typically delivered in 3 to 5 weeks alongside the eLogii rollout.
TRUSTED BY HUNDREDS OF HAPPY CUSTOMERS
HubSpot and eLogii sit in different layers of the same stack. HubSpot is the CRM and customer-experience system of record: contacts, companies, deals, tickets, the marketing and sales automation surface, the help desk, the knowledge base and the customer portal. eLogii is the routing and field execution layer: the route plan, the driver app, the live ETAs, the proof of delivery, the branded customer tracking. Both products expose REST APIs and webhook events, and the integration between them is a normal API integration.
In the combined pattern, HubSpot stays the system of record for the customer relationship and the ticket / deal lifecycle. When a ticket reaches the field-job pipeline stage (or a deal is marked closed-won, or a Custom Object 'Job' record is created), the work flows into eLogii as a routable task. eLogii optimizes against vehicles, depots, time windows, capacities, skills and SLAs; the driver app captures POD, photos, signatures and any custom forms; completion writes back to HubSpot, closing the ticket or moving the deal to its next stage. The integration runs over both products’ REST APIs.
Three tables: where the customer relationship and ticket lifecycle live (HubSpot leads), where routing and field execution live (eLogii leads), and what the integration architecture looks like on both sides.
| HubSpot | eLogii | |
|---|---|---|
| Contact, Company, Deal master | Core. Standard CRM objects with custom properties and associations | Not in scope. References the HubSpot object ID via external_id |
| Tickets, SLAs, help desk pipeline | Core. Service Hub tickets, ticket pipelines, SLA settings, conversations inbox | Not in scope. Reads ticket state to spawn field jobs |
| Quotes, line items, deal stages | Sales Hub: quotes, deal pipelines, line items on deals or quotes | Not in scope |
| Customer portal, knowledge base | Service Hub customer portal and knowledge base (Pro+) | Not in scope |
| Marketing automation, forms, landing pages | Core. Marketing Hub forms, lists, workflows, email and ads | Not in scope |
| Service address, visit window, access notes | On the ticket or custom object as standard or custom properties | Reads via the HubSpot API to feed optimizer constraints |
| Custom Objects representing field Jobs / Visits | Available on Enterprise tier; models field work as a first-class CRM object | Maps Custom Object instances to eLogii tasks |
| Inventory, vehicle and depot master, capacity math | Not in scope. HubSpot is not an ERP / operations system of record | Native: vehicles, depots, capacities, skills, shifts modeled in eLogii |
| eLogii | HubSpot native | |
|---|---|---|
| Multi-stop route optimization with constraints | Two engines, six configurable modes; vehicles, depots, capacities, time windows, skills, SLAs | Not in scope. HubSpot is a CRM, not a routing engine |
| Multi-day, multi-depot routing | Plan a single day or an entire month in one run; multi-depot, multi-day, overnight stops | Not in scope |
| Driver mobile app for on-road execution | Native iOS and Android: navigation, POD, photos, signatures, conditional outcomes, custom forms | The HubSpot mobile app is a CRM app for reps; not an on-road driver surface |
| Live driver GPS, route ETAs, branded customer tracking | Live driver GPS stream, route ETA updates, multi-brand tracking pages with embedded content | Not in scope. The HubSpot Customer Portal shows ticket status, not live ETAs |
| Slot booking co-pilot – route-aware availability | Returns only slots that fit the current optimized plan; ~35% fewer failed visits | HubSpot meeting links and ticket scheduling don’t check route feasibility |
| Customer self-service rescheduling against route plan | ~70% of reschedule requests handled without coordinator involvement | Not in scope |
| Configurable POD forms and conditional outcomes | Configurable POD with photos, signatures, conditional steps, custom fields, custom forms | Not in scope |
| HubSpot | eLogii | |
|---|---|---|
| API style | HubSpot CRM API: REST, JSON, Private Apps for OAuth scopes | REST, JSON over SSL, ApiKey auth, predictable resource URLs |
| Authentication | OAuth 2.0 via Private Apps (recommended) or public OAuth apps for marketplace integrations | ApiKey header, generated in Dashboard > Configuration > API Keys |
| Sandbox environment | HubSpot sandboxes (Standard / Developer; full sandbox on Enterprise) | Full API parity at api-sandbox.elogii.com |
| Bulk operations | Batch endpoints for CRM objects: create, read, update, archive in batches | createOrUpdateMany endpoints handle hundreds of tasks per call |
| Workflows / outbound events | Workflows with webhook actions; Operations Hub custom-coded actions; CRM-level webhook subscriptions | Seven event types including Driver/Task Tracking Update with live GPS stream |
| Optimization callable via API | Not in scope; HubSpot has no route optimization engine | All six modes callable via REST; lock specific routes, manually reorder stops |
Sources: HubSpot Developer documentation, eLogii API documentation. Verified June 2026.
End to end, how a field job moves from a HubSpot ticket (or deal, or Custom Object) to a completed POD and back into HubSpot. The exact wiring depends on your portal and your tier, but the shape is the same in every deployment.
POST /tasks/createOrUpdateMany, with the HubSpot object ID held as external_id so every eLogii task can be traced back to its HubSpot source record (and vice versa).Variations on the same pattern: multi-day jobs modeled as one HubSpot Custom Object record with multiple associated eLogii tasks (one per visit); customer cancellations from HubSpot triggering eLogii re-optimization via webhook; SLA breach events in HubSpot listening to eLogii completion timestamps. None require special connector logic; they are normal mappings across two REST APIs.
HubSpot is a CRM, marketing and service platform. Several parts of it touch the field-job problem at the edge, but none of them are routing or on-road execution. Drawing the line clearly matters when scoping eLogii alongside HubSpot:
HubSpot was built to be a CRM, marketing and service platform; the point of mapping the seam is so the integration with eLogii is clean. HubSpot keeps the customer relationship and ticket lifecycle, eLogii owns the route, the driver app, the live ETA and the POD.
We’d never go back to the way we were planning before. eLogii is the backbone as well as the brain of our planning operations, translating actively to our bottom line.
Jord Van Dijk, IT Director, J-Club · 9,000+ stores routed on eLogii
Three shapes cover almost every HubSpot + eLogii deployment. The right one depends on what your HubSpot setup already looks like and which side of the seam you want the orchestration logic to live on.
api-sandbox.elogii.com and publicly documented endpoints.Two common shapes for customers running HubSpot alongside eLogii. Same underlying pattern, different surface.
Maintenance and repair, pest control, safety and compliance, installation, equipment service. HubSpot owns the customer relationship: inbound leads from forms and ads, the deal pipeline, the ticket queue, the customer portal, the knowledge base. Tickets land in a "Field Job" pipeline once a visit is scheduled; the eLogii Workflow fires when the ticket moves to "Ready to dispatch". eLogii owns route optimization, the driver / technician mobile app for POD and custom forms, the live tracking page and the dispatch desk. Completion writes back to the ticket so customer success can close it and the post-visit NPS Workflow can run.
Often paired with an upstream ERP that owns inventory, line items and invoicing (NetSuite, MS Dynamics 365 BC, Sage, Acumatica). HubSpot holds the customer relationship, the deal pipeline and post-sale tickets; the ERP holds the order book. eLogii reads the order book from the ERP, optimizes the route, dispatches the driver, captures POD and pushes completion back to both: to the ERP for invoicing, to HubSpot as a note / property update on the related Contact and Deal so sales sees the post-delivery state.
eLogii runs alongside HubSpot; nothing changes on the HubSpot side. eLogii pricing starts from $3,000 per month as a platform fee, banded by field staff, drivers, jobs per day and the modules required. Each band includes a quota; cost steps up when the operation crosses a band, not when you add an individual seat. Customers typically report 3 to 4× return on investment within 6 months, and combined HubSpot + eLogii rollouts (including the integration) complete in 3 to 5 weeks. HubSpot pricing is its own thing and is not affected by adding eLogii.
30-minute custom simulation with a sample of recent HubSpot tickets / deals, your depots and your vehicles. Projected savings in drive time, planner hours and SLA breaches from adding eLogii on top.
We have been extremely impressed with the results from eLogii so far. The solution is powerful and the team have found it extremely intuitive and easy to get going with. We signed a multi-year agreement with eLogii and are looking forward to deepening our relationship with them over the next years.
Anthony O’Keeffe, CEO, Bristow & Sutor · 200+ enforcement agents, 200,000+ case visits routed annually
Three steps for teams whose field operations have outgrown what the HubSpot ticket / deal layer covers on its own, and who want to keep HubSpot as the customer-relationship and ticket system of record while adding eLogii for routing and execution on top.
Pick the HubSpot object that represents the field job (Service Hub ticket, Custom Object Job, or Deal in a field pipeline). Mapping to eLogii task fields documented end to end. Custom properties on the HubSpot side surfaced as eLogii custom fields. A HubSpot Private App created with the right CRM scopes; eLogii ApiKey provisioned in the sandbox. Sandbox connectivity proven on both sides before any production data moves.
Weeks 1–2Custom data simulation against a recent sample of HubSpot tickets / deals so you can validate the modeling and project savings before go-live. Side by side: how the work gets dispatched today vs. how eLogii would route it with the same constraints. Approve the optimizer settings, the Workflow trigger, the write-back fields and the close-the-loop properties on the HubSpot object.
Weeks 2–3Start with one team, region or service line. Drivers and technicians onboarded onto the eLogii app. HubSpot Workflow live on the relevant pipeline. eLogii webhook stream wired to your Operations Hub custom-coded action (or iPaaS) for the write-back. Expand to the rest of the operation once the first cohort is steady. Most teams complete the transition in 3 to 5 weeks total.
Weeks 3–5Unimasters runs eLogii across a multi-country operation and achieved 50% less planning time and 49% fewer service calls. Multi-country rollouts deploy in weeks, not quarters.
Through both products’ REST APIs. HubSpot exposes the HubSpot CRM API with Private Apps for OAuth-scoped server-side access, CRM Objects and Custom Objects, Workflows, Operations Hub custom-coded actions, and webhook subscriptions. eLogii’s REST API has 70+ endpoints, ApiKey auth, a full-parity sandbox at api-sandbox.elogii.com and seven webhook event types including Driver/Task Tracking Update with live GPS. Typical pattern: a HubSpot Workflow fires on a ticket / deal / Custom Object stage change and calls eLogii; eLogii runs the optimization and dispatches the driver app; completion data writes back to HubSpot, closing the ticket or moving the deal. Most deployments are delivered in 3 to 5 weeks alongside the eLogii rollout.
No. HubSpot Service Hub is the ticketing, knowledge base, customer portal and SLA layer. Tickets capture the customer issue or the job request. eLogii is the routing and field execution layer that takes a ticket from acceptance to the customer’s door: optimized routes, the driver mobile app, proof of delivery, branded customer tracking. The two sit at different layers; the ticket lifecycle stays in HubSpot and execution data writes back as ticket updates, notes and custom property changes.
Three common patterns depending on your HubSpot tier and how field work shows up in your business: (1) Service Hub ticket, the most common, with custom properties for address, time window and SLA; (2) HubSpot Custom Object (Enterprise) representing ‘Job’ or ‘Visit’, with associations to the Contact and Company; (3) Deal in the Sales pipeline for installation or one-off projects, with stage transitions triggering eLogii. All three map cleanly to an eLogii task via the HubSpot API.
From the relevant HubSpot object (ticket, custom object or deal): the linked contact and company, the service address (and any geo), the requested visit window, the ticket pipeline stage, SLA target, custom properties carrying special-handling notes (gate codes, access notes, equipment serials, key handling). All of that is exposed via the HubSpot CRM API. The integration job either pulls on a schedule or, more commonly, pushes via a HubSpot Workflow that calls eLogii on a stage transition, or via an Operations Hub custom-coded action.
Typically: completion status (delivered, completed, partial, failed and the reason), proof-of-delivery references (photo URLs, signature image references), arrival and completion timestamps, any driver-collected payments, custom form data captured in the driver app, and the final status that closes the HubSpot ticket or moves the deal to Closed-Won. The write-back uses the HubSpot CRM API, typically as ticket property updates plus engagements (notes, attachments) from the integration layer.
Yes. eLogii has REST + JSON APIs, a sandbox at api-sandbox.elogii.com and publicly documented endpoints. Whichever iPaaS your team already uses can broker eLogii alongside HubSpot.
Typically 3 to 5 weeks from kickoff to a phased go-live, including the HubSpot integration. Most teams start with one team, region or service line, validate against a sample of recent tickets, then expand. The integration is straightforward: HubSpot Workflow fires on a ticket pipeline stage, calls eLogii to create a task, eLogii routes and dispatches; on completion, the eLogii webhook fires and the integration writes back to the ticket.
HubSpot pricing stays as-is; eLogii is added on top. eLogii pricing is a platform fee, banded by field staff, drivers, jobs per day and modules, from $3,000 per month. Customers typically report 3 to 4× return on investment within 6 months on eLogii.
The integration runs on any HubSpot tier that exposes Workflows or Operations Hub custom-coded actions. HubSpot Custom Objects (a clean way to model field jobs) require Enterprise. Most rollouts use Service Hub tickets, which work from Service Hub Starter / Professional upwards. The HubSpot sandbox used for integration testing is part of Enterprise.
Yes. eLogii runs operations at scale: J-Club (9,000+ stores), NHS, Belfast City Council, Vergo, Bristow & Sutor, Porcelanosa, Caldic and Berkmann Wine Cellars. ISO 27001 and SOC 2 Type 2 certified.
Last updated: June 2026. Information about HubSpot is drawn from HubSpot’s public documentation, including the HubSpot Developer documentation and HubSpot product pages. Information about eLogii is drawn from elogii.com and the eLogii API documentation.
Custom simulation
A 30-minute working session with our solutions team. We take a sample of your real HubSpot tickets / deals, your depots, vehicles and SLAs, run them through the eLogii engine, and show you the projected delta against how you dispatch today. No slides, no generic benchmarks.