LealUp Docs
Integrations

Integrations

Connect LealUp with the tools you already use — email, calendar, chat, CRM, support, product analytics.

LealUp feeds on the tools where the CSM's work already happens. This section explains each available integration, how to connect it, and what data syncs.

Why integrations matter

Without integrations, LealUp is just another customer database. With integrations, the health score feeds on real signals, the timeline builds itself, and playbooks fire on real-world events.

Minimum recommendation to get productive: Gmail + Calendar + at least one support or product integration.

Available today

Email and Calendar

Chat

  • WhatsApp Business — via the official WhatsApp Business API (Kapso), customer context.
  • Slack — notifications and the /lealup command.

CRMs and support

Bulk data

  • Import CSV — initial bulk import, useful for migration.

Your own system

  • Ingestion API: send usage and billing events from your backend, authenticated with your API key.

On the roadmap

No committed dates; we prioritize by demand:

  • Salesforce.
  • HubSpot bidirectional.
  • Native product analytics connectors (PostHog, Mixpanel, Amplitude, Segment).
  • Freshdesk, Help Scout, Front (based on demand).

Request a specific integration at [email protected].

How an integration works in LealUp

Most follow the same pattern:

  1. OAuth by user or by workspace — we don't ask for passwords, we use the provider's standard.
  2. Minimum scopes — we only request permissions strictly needed (e.g., readonly for Gmail, not send).
  3. Initial sync — a bounded backfill of recent days. It does not bring your full history.
  4. Incremental sync — webhooks or polling every 5–15 minutes.
  5. Normalization — we translate the data into our Timeline event and Health signal model.
  6. Respect for the source of truth — if you edit something in Gmail, that's where the canonical copy lives; LealUp just reflects.

Integration security

  • Encrypted tokens at rest.
  • Automatic rotation of refresh tokens.
  • Revocation — on disconnect, we revoke the provider token and delete our copy.
  • Scope transparency — each integration shows exactly what it reads and what it writes.
  • No sending on your behalf without confirmation — no integration sends emails or messages proactively without a human hitting "send".

Permissions to connect

Who can connect what:

TypeWho can connect
Personal integration (CSM's Gmail, Calendar)each user connects their own
Workspace-wide integration (Zendesk, Pipedrive, Slack workspace)admin only
CSV importadmin or director

General troubleshooting

If an integration fails:

  1. Admin → Integrations → [name] → view status.
  2. Sync logs — last 50 runs with success/error/duration.
  3. Reconnect — the most common step. Tokens expire, users revoke access from the provider, etc.
  4. Contact support — with the trace_id of the last error.

Each specific integration page has a "Common issues" block with concrete fixes.

On this page