---
title: "Ably integration for LuumenAI"
url: "https://www.luumen.ai/integrations/ably/"
entity: SoftwareIntegration
category: "Source control & CI/CD"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# Ably integration for LuumenAI

Read channel, presence, and push state in Ably, then publish with approval

## What LuumenAI can do with Ably

LuumenAI connects to Ably with an API token and exposes 25 tools (14 read-only · 8 write · 3 destructive). Reads answer immediately; writes are shown as a plan and require approval by default, configurable per tool by an administrator.

## Key facts

- Authentication: API token
- Tools available: 25 tools (14 read-only · 8 write · 3 destructive)
- Plan: available on all plans
- Category: Source control & CI/CD

## About Ably with LuumenAI

Connect Ably with an API key and Luumen can answer questions about your real-time layer directly in the terminal: which channels are active, who is present, what a channel's recent message history looks like, and which devices are registered for push. When you need to act, Luumen previews the publish or registration change and asks before sending it.

## Example tools

Read-only (14 in total):

- `ABLY_BATCH_PRESENCE` — This tool enables querying the presence states of multiple channels in a single API request.
- `ABLY_BATCH_PRESENCE_HISTORY` — This tool enables querying presence history for multiple channels in a single API request.
- `ABLY_GET_CHANNEL_DETAILS` — This tool retrieves metadata and details for a specific channel in Ably.
- `ABLY_GET_CHANNEL_HISTORY` — This tool retrieves the message history for a specified Ably channel.
- `ABLY_GET_CHANNEL_PRESENCE` — Obtain the set of members currently present for a channel.
- `ABLY_GET_MESSAGE_VERSIONS` — Retrieve all historical versions of a specific message from an Ably channel.
- `ABLY_GET_PRESENCE_HISTORY` — This tool retrieves the history of presence messages for a specified channel in Ably.
- `ABLY_GET_PUSH_DEVICE` — Get the full details of a device registration for push notifications.

Write and destructive (11 in total, approval required by default):

- `ABLY_DELETE_CHANNEL_SUBSCRIPTION` — This tool allows you to unsubscribe devices or clients from push notifications for specific channels.
- `ABLY_PATCH_PUSH_DEVICE_REGISTRATION` — Partially update specific attributes of an existing device registration in Ably's push notification system.
- `ABLY_PUBLISH_BATCH_MESSAGES` — Batch publish messages to multiple channels in parallel.
- `ABLY_PUBLISH_MESSAGE_TO_CHANNEL` — Allow users to publish a message to a specified Ably channel using a POST request.
- `ABLY_PUBLISH_PUSH_NOTIFICATION` — Publish a push notification directly to device(s) via Ably's Push Notifications API.
- `ABLY_PUBLISH_PUSH_NOTIFICATIONS_BATCH` — Batch publish push notifications directly to specific recipients.
- `ABLY_REGISTER_PUSH_DEVICE` — Register a device for receiving push notifications in Ably.
- `ABLY_REQUEST_ACCESS_TOKEN` — Request an access token for Ably authentication.

## Frequently asked questions

### How does LuumenAI connect to Ably?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

### Can LuumenAI change things in Ably on its own?

Read actions answer immediately. Anything that writes is shown as a plan and requires approval by default, including the 3 actions classified as destructive. Administrators configure that per tool.

### Is there an audit trail?

Every call to Ably — read or write, approved or declined — is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/ably/