Overview

An integration is a connected third-party app, either an action target usable from a journey node (Slack, Jira, Google Calendar) or a data source kept in sync with your contacts (Zoho Books, Google Sheets). See the Integrations guide for what each provider does and how connecting looks from the dashboard.

Most of these endpoints exist to back the dashboard's Integrations page and the journey node config panels, but they're ordinary authenticated API endpoints — anything below works the same way with an X-API-Key header as it does from the dashboard's own session.

List integrations#

curl https://app.lemuai.com/api/v1/integration/ \
  -H "X-API-Key: lemu_your_api_key"

[
  {
    "id": 5,
    "integration_id": "conn_abc123",
    "organisation_id": 7,
    "created_by": 3,
    "provider": "slack",
    "is_active": true,
    "created_at": "2026-08-01T12:00:00Z",
    "action": "connected",
    "provider_data": { "channel": "#general" }
  }
]

provider_data carries a little provider-specific context: the default channel for slack, and sheet_url / sheet_name / contact_list_name once a sheet has been picked for google-sheet.

Connect a provider#

Starts the OAuth flow. Most providers need no connection_params; Jira requires a subdomain (the part before .atlassian.net).

curl -X POST https://app.lemuai.com/api/v1/integration/connect \
  -H "X-API-Key: lemu_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{ "provider": "jira", "connection_params": { "subdomain": "acme" } }'

{
  "request_id": "conn_req_xyz789",
  "redirect_url": "https://backend.composio.dev/connect/conn_req_xyz789"
}

Open redirect_url in a browser to complete the provider's consent screen — this step is inherently interactive and can't be done as a plain API call. redirect_url is null if the organization already has an active connection for this provider; in that case, skip straight to finalize with request_id as the connected_account_id.

Once the user completes the popup, confirm and persist the connection:

curl -X POST https://app.lemuai.com/api/v1/integration/connect/finalize \
  -H "X-API-Key: lemu_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{ "connected_account_id": "conn_req_xyz789", "provider": "jira" }'

This re-checks the connection's status directly against Composio rather than trusting client-supplied OAuth callback params, and is idempotent — calling it twice for the same connected_account_id returns the existing integration rather than erroring.

Disconnect a provider#

curl -X POST https://app.lemuai.com/api/v1/integration/5/disconnect \
  -H "X-API-Key: lemu_your_api_key"

{ "status": "disconnected" }

This revokes the underlying Composio connection, not just the row in Lemu's database — reconnecting afterward always shows a fresh consent screen, which is what lets you grant additional scopes that an earlier connection was missing.

Field mapping (data-source integrations)#

For zoho_books, each entry has a direction (inbound, outbound, or bidirectional); for google-sheet, it's a flat { lemu_field: sheet_column_header } map instead, since a spreadsheet has no separate concept of direction per column.

curl -X PUT https://app.lemuai.com/api/v1/integration/5/field-mapping \
  -H "X-API-Key: lemu_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "field_mapping": {
      "email": { "external_field": "email", "direction": "bidirectional" },
      "phone": { "external_field": "mobile", "direction": "inbound" }
    }
  }'

Errors#