LemuAI

Overview

Connect Slack, Jira, Google Calendar, Zoho Books, and Google Sheets to your journeys and contacts

Integrations connect a third-party app to your organization so it can be used from journeys and, for two providers, kept in sync with your contacts. Manage them from Settings → Integrations in the dashboard.

Connecting is OAuth-based — clicking Connect opens a popup where you sign in to the provider and grant access. Lemu never sees or stores your provider password.

Integrations page showing Slack connected and Jira, Google Calendar, Zoho Books, and Google Sheets available to connect

Available integrations#

Two kinds of integration#

KindProvidersWhat it's for
ActionSlack, Jira, Google CalendarAdds a node to the journey canvas — send a Slack message, create a Jira issue, or book a Google Calendar event as one step in a journey
Data sourceZoho Books, Google SheetsSyncs contacts into Lemu (new/changed rows become contacts) and can push a contact's updates back out to the connected sheet or CRM

An action integration doesn't touch your contacts — it's purely something a journey can do. A data-source integration is the reverse: it's about keeping your contact list current, not about acting inside a call or journey.

Connecting#

  1. On Settings → Integrations, find the provider under Add an integration and click Connect.
  2. Jira asks for your site's subdomain first (e.g. enter acme if your Jira URL is acme.atlassian.net) before continuing to OAuth. Every other provider goes straight to the OAuth popup.
  3. Complete the provider's sign-in and consent screen in the popup. Lemu polls in the background and closes the popup automatically once the connection is confirmed active — you don't need to do anything else in the main window.
  4. Zoho Books additionally asks you to pick which Zoho organization to sync, if your account has more than one (skipped automatically if you only have one).
  5. Google Sheets additionally asks you to search for and pick a spreadsheet, then confirm how its columns map to contact fields — see Google Sheets for that step in detail.

Integrations are a plan entitlement — your plan caps how many you can have connected at once. If you're at the limit, connecting a new one prompts you to upgrade or disconnect another first.

Disconnecting and reconnecting#

Click Disconnect on a connected provider's card to remove it. This fully revokes the underlying connection, not just hides it in Lemu — so if a journey node or data sync depended on it, that stops working until you reconnect.

If Lemu reports an integration doesn't have enough access (for example, a Google Sheets scope was denied at connect time), disconnect and reconnect it: connecting again after a full disconnect always shows a fresh consent screen, so you can grant the missing permission. Reconnecting without disconnecting first can silently reuse the old, insufficient connection instead of prompting for new consent.

Next steps#

© 2026 LemuAI. Built with our own docs platform.