Integrations and configured workflows available in OLT

Google Workspace

Personal email and calendar connections for day-to-day customer work.

• Google Workspace

  Gmail

  Connection scope Personal account Send customer email from your own connected Google account inside OLT.
  • Inbound attachment retention is best-effort up to 25 MB OLT attempts to retain inbound Gmail attachments of 25 MB or less. Oversized files, or attachment download, storage, or persistence failures, leave the CRM email activity intact without guaranteeing that file is available.
• Google Workspace

  Google Calendar

  Connection scope Personal account Only scheduled CRM meetings assigned to a linked member who has connected their own Google Calendar are mirrored to that member's primary calendar; inbound synchronization covers date-time events on that primary calendar. A newly imported Google Calendar event can create a CRM meeting and associate recognized attendee records, but OLT does not infer the meeting's opportunity, company, or primary-contact context. An authorized CRM editor must attach that context. See Sales CRM workflows
  • Public one-to-one booking links An active Sales CRM seller can publish a shareable one-to-one booking link only with their own Google Calendar connected. The personalized URL stays noindex and nofollow and exposes only open times after OLT applies working hours, the chosen duration, before-and-after buffers, minimum notice, CRM meetings, and busy intervals from the seller's primary calendar. If OLT cannot verify current Calendar availability, it stops availability and booking. A successful booking sends the guest a Google invitation, records the CRM meeting, and either reuses the matching CRM contact or creates a lead contact.

Accounting

Company accounting records and confirmed payment workflows.

• Intuit

  QuickBooks Online

  Connection scope Company-wide Pull 11 supported QuickBooks entity types, then control ten QuickBooks-to-OLT pulls separately from OLT-to-QuickBooks creates or updates. Used in OLT: Accounting

Telematics

MyGeotab vehicle positions, kilometre odometers, route history, driving state, and driver duty status, plus verified freight and parcel provider credentials.

• MyGeotab · GPS & ELD telematics

  Geotab

  Connection scope Company-wide Vehicle positions, kilometre odometers, and route playback for mapped MyGeotab equipment in the TMS. Used in OLT: TMS
• Project44 · MacroPoint · EasyPost · ShipEngine

  Freight and parcel providers

  Connection scope Company-wide Compare freight-provider verification and implemented parcel workflows without promising provider-fed positions, ETAs, or proof of delivery. Used in OLT: TMS
  • TMS module Access to freight-provider setup requires the TMS module.
  • TMS administrator Saving credentials, running a verification, and disconnecting a provider require TMS administrator access.
  • Inventory Tracking read access Parcel-rate previews require Inventory Tracking read access.
  • Inventory Tracking write access Attended ShipEngine label purchases require Inventory Tracking write access.
  • Destination classification Every parcel-rate preview requires a Residential or Commercial destination selection.
  • Connected means verified A provider counts as connected only while its stored organization-wide credentials are active and its most recent verification succeeded; saving credentials again returns it to untested until it is verified.
  • Project44 Project44 setup verifies an OAuth client-credentials token against the approved endpoint; no Project44 position, ETA, or proof-of-delivery consumer is implemented.
  • MacroPoint · Descartes MacroPoint verification requires an account-specific Descartes API contract, so its credentials remain stored but inactive until that contract can be verified; no MacroPoint tracking, ETA, or proof-of-delivery ingestion is implemented.
  • EasyPost and ShipEngine The setup screen verifies and stores EasyPost and ShipEngine API keys; it does not itself create shipments, buy labels, or start tracking. Verified keys can be used by separate supported fulfillment actions.

Communications

Company calling, call history, and customer messaging only where supported by the selected connection.

• Phone & SMS

  Quo (formerly OpenPhone)

  Connection scope Company-wide Click-to-call opens Quo's web dialer, and outbound SMS uses the Quo API. Call logs and provider recordings depend on configured call-event webhooks; inbound SMS needs a separate webhook that the current guided setup does not expose. See Customer Service workflows
  • Connection setup Customer Service / Support Tickets must be enabled, and a module administrator needs a Quo account and API key to create, test, and activate the company connection.
  • Click-to-call OLT records the outbound attempt and opens Quo's web dialer with the customer number. The call continues in Quo; OLT does not provide a native calling dialer or carry live call audio.
  • Outbound SMS Sales CRM sends outbound SMS through the Quo API for an active connection and stores the sent message and CRM activity in OLT.
  • Call-event webhooks Completed and inbound call logs and recording updates depend on a signed call-event webhook configured in Quo for call.completed and call.recording.completed.
  • Inbound SMS setup Inbound messages and delivery statuses require a separate signed SMS-event webhook. The current guided phone setup displays only the call-event webhook and does not expose SMS webhook setup.
  • Provider media OLT does not create recordings or transcripts. Recording links and transcription fields appear only when the configured provider supplies them.
• Phone · generic callData webhook

  Custom call webhook

  Connection scope Company-wide The generic custom-phone path imports call records only when a provider can POST OLT’s expected callData envelope to the configured webhook. OLT does not automatically normalize vendor-specific payloads or offer a live connection test for this path. It does not provide generic outbound SMS or click-to-call. See Customer Service workflows
• Meta Cloud API

  WhatsApp Business

  Connection scope Company-wide Keep customer WhatsApp text conversations in Sales CRM threads and activity timelines.

Social channels

Supported business channels for publishing, scheduling, and the reporting each provider returns.

• Social channel

  Facebook

  Connection scope Company-wide Publish and schedule to your Facebook page from OLT. Used in OLT: Marketing
  • Buyer value Keep Facebook Page updates in the same reviewed composer and destination-level result history as the other implemented social channels.
  • Publishing workflow Authorize a Meta login, choose an eligible Facebook Page, then publish immediately or schedule that Page as a destination; OLT records its delivery result separately.
  • Provider setup Meta developer app; Facebook Page admin access; Approved Pages permissions.
  • Business resource A Facebook Page available to the authorized login.
  • Media and links OLT publishes text-only Page updates with an optional HTTPS campaign link, or a photo post using the first public HTTPS image URL. When an image is present, the campaign link is not attached.
  • Scheduling and character limit Publish now or schedule at least 1 minute in the future. OLT rejects entered post text above 63,206 characters for this destination.
  • Measurement availability OLT requests Facebook account statistics and recent Page posts, and can refresh likes, comments, and shares for an OLT-published post. Provider-denied or failed responses are shown as unavailable.
• Social channel

  Instagram

  Connection scope Company-wide Publish and schedule Instagram posts from OLT. Used in OLT: Marketing
  • Buyer value Prepare Instagram professional-account media posts alongside the other implemented channels while retaining a separate result for the selected destination.
  • Publishing workflow Authorize a Meta login, choose an eligible linked Instagram professional account, then publish immediately or schedule that account as a destination; OLT records its delivery result separately.
  • Provider setup Instagram Business or Creator account; Linked Facebook Page; Approved Instagram permissions.
  • Business resource An Instagram professional account linked to an accessible Facebook Page.
  • Media and links Every post requires at least one public HTTPS image or video URL. OLT accepts up to 10 media URLs for the post, and the optional campaign link is not attached.
  • Scheduling and character limit Publish now or schedule at least 1 minute in the future. OLT rejects entered post text above 2,200 characters for this destination.
  • Measurement availability OLT requests Instagram account statistics and recent posts, and can refresh likes and comments for an OLT-published post. Provider-denied or failed responses are shown as unavailable.
• Social channel · formerly Twitter

  X

  Connection scope Company-wide Post and schedule to X from OLT. Used in OLT: Marketing
  • Buyer value Publish short X updates from the shared composer and keep the profile result visible beside the other selected destinations.
  • Publishing workflow Authorize an X login, use the returned X profile, then publish immediately or schedule that profile as a destination; OLT records its delivery result separately.
  • Provider setup X developer project; OAuth 2.0 enabled; API plan with read/write access.
  • Business resource The X profile returned for the authorized login.
  • Media and links OLT posts text plus the campaign link when present; otherwise it appends the first media URL as a link. OLT does not upload media directly to X.
  • Scheduling and character limit Publish now or schedule at least 1 minute in the future. OLT rejects entered post text above 280 characters for this destination.
  • Measurement availability OLT requests X account and recent-post public metrics, and can refresh likes, replies, reposts, and impressions for an OLT-published post. Provider-denied or failed responses are shown as unavailable.
• Social channel

  LinkedIn

  Connection scope Company-wide Publish LinkedIn member updates from OLT, or company-page updates when LinkedIn has approved the organization scopes. Used in OLT: Marketing
  • Buyer value Coordinate LinkedIn member or approved organization updates with the other implemented destinations from one composer and result history.
  • Publishing workflow Authorize a LinkedIn login, choose the member profile or an eligible organization, then publish immediately or schedule that identity as a destination; OLT records its delivery result separately.
  • Provider setup LinkedIn developer app; Community Management API access for company Pages; Page admin role.
  • Business resource The authorized member profile or an approved LinkedIn organization.
  • Media and links OLT publishes the entered text and appends the HTTPS campaign link when present; otherwise it appends the first public HTTPS media URL as a link. Direct media upload is not implemented, and company posting requires approved organization scopes.
  • Scheduling and character limit Publish now or schedule at least 1 minute in the future. OLT rejects entered post text above 3,000 characters for this destination.
  • Measurement availability OLT can request recent posts and the follower count for an organization destination when LinkedIn access allows. Per-post engagement refresh is not available in the current LinkedIn workflow.
• Social channel

  TikTok

  Connection scope Company-wide Publish and schedule TikTok video or photo posts from OLT. Used in OLT: Marketing
  • Buyer value Prepare TikTok photo or video publishing with the same scheduling and destination-result workflow used for the other implemented channels.
  • Publishing workflow Authorize a TikTok login, use the returned creator profile, then publish immediately or schedule that profile as a destination; OLT records its delivery result separately.
  • Provider setup TikTok developer app; Content Posting API product; video.publish approval for public posts.
  • Business resource The TikTok creator profile returned for the authorized login.
  • Media and links Every post requires public HTTPS media. OLT sends the first public video URL, or up to 10 public photo URLs when the first URL is an image; the optional campaign link is not attached. Unaudited apps may be limited to private posts.
  • Scheduling and character limit Publish now or schedule at least 1 minute in the future. OLT rejects entered post text above 2,200 characters for this destination.
  • Measurement availability OLT can request TikTok account counts and recent-video metrics when provider access allows. Per-post engagement refresh is not available in the current TikTok workflow.
• Social channel

  Google Business Profile

  Connection scope Company-wide After a location manager connects a verified profile, OLT can publish or schedule standard text updates with one public image and an optional Learn More link. Used in OLT: Marketing
  • Buyer value Keep verified-location updates in the same publishing calendar and destination-result history as the implemented social channels.
  • Publishing workflow Authorize a Google manager login, choose an eligible verified business location, then publish immediately or schedule that location as a destination; OLT records its delivery result separately.
  • Provider setup Google Cloud OAuth app; Business Profile API access; Manager access to a verified location.
  • Business resource A verified business location available to the authorized manager login.
  • Media and links OLT publishes a standard text update with the first public HTTPS image URL as an optional photo and the HTTPS campaign link as an optional Learn More action; it does not create Offer posts.
  • Scheduling and character limit Publish now or schedule at least 1 minute in the future. OLT rejects entered post text above 1,500 characters for this destination.
  • Measurement availability OLT can request recent local posts and provider-returned search-view and call-to-action-click fields. Per-post engagement refresh is not available in the current Google Business Profile workflow.

Reviews

Configured Google review requests from verified payment, quote, and CRM events.

• Public review destination link

  Google Reviews

  Connection scope Company-wide In Marketing > Google Reviews, an organization owner or administrator enables the module and one or more verified events: Payment Received, Quote Accepted, and Deal Won. Dispatch also requires a saved supported public Google review destination URL, a recipient email address from the triggering workflow, and no request to that recipient address inside the configured cooldown; each generated feedback link uses the configured expiration. Every respondent receives the same configured public Google Business Profile link. Private issue details are optional; a customer service ticket is created only if the respondent submits those private details. Each customer decides whether to publish on Google; OLT does not publish public reviews automatically.

API

Organization-bound, rate-limited, revocable access for approved external tools.

• OLT Solutions

  OLT API access

  Connection scope Company-wide Let your own server integrations read supported records and submit the changes the mounted OLT API v1 routes expose.

Search measurement

Owned search evidence, exact CMS sitemap submission, and consented landing-page outcomes.

• Google

  Google Search Console

  Connection scope Company-wide Measure organization-owned Google search evidence and submit the connected CMS sitemap.
• Google

  Google Analytics 4

  Connection scope Company-wide Measure consented landing-page outcomes from the connected GA4 property.
• Microsoft Bing

  Bing Webmaster Tools

  Connection scope Company-wide Measure organization-owned Bing search evidence for the verified website.

Marketplaces

Registered WMS marketplace adapters with their exact prerequisites, supported workflows, and limitations.

• Amazon · Selling Partner API

  Amazon

  Connection scope Company-wide Preview or pull orders and run configured automatic basic-order sync on verified credentials; inventory and fulfillment sync are not supported. See WMS workflows

  Prerequisites: An Amazon seller account connected with Selling Partner API credentials for the selected marketplace, verified in the WMS marketplace workspace.

  Supported workflows: Order preview on verified credentials; Manual order pull; Configured automatic basic-order sync

  Limitations: Inventory sync is not supported; Fulfillment sync is not supported

• Shopify · Admin API

  Shopify WMS

  Connection scope Company-wide Preview and import reviewed orders, then preview up to 100 active SKU mappings at one Shopify location and confirm every ready difference by hand; automatic order, inventory, and fulfillment sync are unavailable. See WMS workflows

  Prerequisites: A canonical *.myshopify.com shop domain and Admin API access token, remotely verified in the WMS marketplace workspace.

  Supported workflows: Attended order preview and import on verified credentials; Inventory preview for up to 100 active SKU mappings at one selected Shopify location; Failure-free preview confirmation that publishes every ready difference with compare-quantity protection

  Limitations: Automatic order sync is unavailable; Automatic inventory sync is unavailable; Fulfillment sync is unavailable

• Walmart · Marketplace APIs

  Walmart

  Connection scope Company-wide Verify regional credentials and preview read-only inventory; order sync, inventory publishing, automatic sync, and fulfillment sync are not supported. See WMS workflows

  Prerequisites: Walmart Marketplace client credentials for a supported region (US, CA, MX, or CL), verified in the WMS marketplace workspace.

  Supported workflows: Read-only inventory preview against a mapped warehouse and ship node

  Limitations: Order sync is not supported; Inventory publishing is not supported; Automatic sync is not supported; Fulfillment sync is not supported

Connection and mapping requirements

• Choose a supported Walmart region Select the United States, Canada, Mexico, or Chile and save the Walmart Marketplace client ID and client secret for that region; add a consumer channel type only when Walmart provided one during onboarding.
• Verify inventory read access first OLT requires the Walmart connection to pass its remote verification before setup, mapping, or preview, and the saved credentials must permit inventory reads.
• Map one warehouse to one observed ship node Map one active, organization-owned WMS warehouse to one Walmart ship node observed on the first bounded provider page; ship-node choices come from that page's first 50 items and may be partial when Walmart has more pages.

Read-only SKU comparison

• Equal and Different show the quantity result For one active, unambiguous marketplace SKU mapping, OLT compares Walmart available-to-sell quantity with available-to-promise stock at the mapped warehouse and marks the row Equal or Different.
• Unmapped keeps unresolved SKUs visible A Walmart SKU with no active marketplace mapping is marked Unmapped instead of being matched or assigned automatically.
• Unavailable never becomes an assumed zero Missing ship-node quantities, malformed records, inactive products, duplicate provider SKUs, ambiguous mappings, and other unresolvable rows remain Unavailable instead of being treated as zero.

Paging, recovery, and read-only boundaries

• Provider pages contain at most 50 rows Each attended request reads at most one official Walmart inventory page of 50 items and continues only through opaque cursors bound to the connection, warehouse, and ship node.
• Traversal stops after five pages Results explicitly report Partial when more than one page is involved or Walmart has more data, and report Truncated when the five-page ceiling stops further traversal.
• Throttling and timeouts stay recoverable Walmart throttling returns wait-and-retry guidance, while a provider call that exceeds the 12-second route deadline returns an explicit read-only preview timeout without changing inventory.
• Order synchronization is unavailable The Walmart adapter does not preview or import Walmart orders and does not run automatic order synchronization.
• Inventory publication and automatic sync are unavailable The preview calls no Walmart inventory update endpoint, publishes no quantities, and enables no automatic inventory synchronization.
• Fulfillment sync and WMS stock mutation are unavailable The workflow sends no fulfillment updates to Walmart and never reserves, adjusts, or otherwise changes WMS stock.