# Ably AI integration on Definable

> Ably is a real-time messaging platform helping developers build live features, including chat and data synchronization, with global scalability and robust reliability for modern applications

## What this connects

Ably is a real-time messaging platform helping developers build live features, including chat and data synchronization, with global scalability and robust reliability for modern applications

Vendor: https://ably.com

## Tools available

**25** tools available. First 12:

- `ABLY_BATCH_PRESENCE` — Query Batch Presence — This tool enables querying the presence states of multiple channels in a single API request. The API retrieves the member presence details of the specified channels in parallel.
- `ABLY_BATCH_PRESENCE_HISTORY` — Query Batch Presence History — This tool enables querying presence history for multiple channels in a single API request. It uses the GET endpoint at https://rest.ably.io/presence to retrieve the member presence history details of the specified channels in parallel.
- `ABLY_DELETE_CHANNEL_SUBSCRIPTION` — Delete Channel Subscription — This tool allows you to unsubscribe devices or clients from push notifications for specific channels. The operation is asynchronous, so immediate requests after deletion may briefly still return the subscription.
- `ABLY_GET_CHANNEL_DETAILS` — Get Channel Details — This tool retrieves metadata and details for a specific channel in Ably. It returns a ChannelDetails object containing information about the channel's status, occupancy, and other metadata. The endpoint provides visibility into channel activity, including metrics such as connections, presence, publishers, and subscribers, and requires appropriate permissions.
- `ABLY_GET_CHANNEL_HISTORY` — Get Channel History — This tool retrieves the message history for a specified Ably channel. It uses the GET /channels/{channelId}/messages endpoint to return a paginated list of messages in chronological order, subject to parameters such as 'channelId', 'limit', 'direction', 'start', and 'end'. The tool is useful for auditing, recovering missed messages, analyzing channel activity, and debugging message flows. Authentication is required via basic or token authentication.
- `ABLY_GET_CHANNEL_PRESENCE` — Get Channel Presence — Tool to obtain the set of members currently present for a channel. Use when you need to check which clients are currently connected and active on a specific Ably channel.
- `ABLY_GET_MESSAGE_VERSIONS` — Get Message Versions — Tool to retrieve all historical versions of a specific message from an Ably channel. Use when you need to track message history, including the original message and all subsequent updates or delete operations. Each version includes metadata such as timestamp, action type, and client ID.
- `ABLY_GET_PRESENCE_HISTORY` — Get Channel Presence History — This tool retrieves the history of presence messages for a specified channel in Ably. It allows you to query presence events on a channel within a given time period.
- `ABLY_GET_PUSH_DEVICE` — Get Push Device Registration — Tool to get the full details of a device registration for push notifications. Use when you need to retrieve information about a specific device registered for push notifications, including its platform, state, recipient details, and metadata. Requires the device ID.
- `ABLY_GET_SERVICE_TIME` — Get Ably Service Time — This tool retrieves the current server time from Ably's service in milliseconds since the epoch. It is particularly useful for time synchronization and generating valid TokenRequest timestamps to prevent replay attacks. The endpoint supports multiple content types, handles HTTP errors, network issues, and is a fundamental tool for ensuring accurate timing in Ably applications.
- `ABLY_GET_STATS` — Get Application Stats — This tool retrieves your application's usage statistics from Ably. The stats endpoint returns a paginated list of your application's usage statistics by minute, hour, day, or month. It supports optional parameters such as start, end, direction, limit, and unit to filter and format the returned data. The stats include metrics for: - Message counts and data transferred - Connection counts - Channel usage - API request counts - Push notification metrics - Token request counts
- `ABLY_LIST_CHANNELS` — List Channels — Tool to enumerate all active channels in the Ably application. Use when you need to discover available channels or monitor channel activity. Returns paginated results and is heavily rate-limited. Can return either channel names only or full channel details with occupancy data.

## Auth

Auth schemes: `API_KEY`.

## How agents use Ably

Inside a Definable workflow, Ably is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Ably** — the Researcher (GPT-5.5) pulls context from Ably (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Ably** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Ably (create record, post message, draft email).
- **Designer / Engineer → Distributor → Ably** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Ably (attach file, open PR comment, post status).

The Verifier checks every Ably call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- developer tools — https://definable.ai/apps/category/developer-tools/

## Related

- HTML page: https://definable.ai/apps/ably/
- Same category (developer tools): https://definable.ai/apps/category/developer-tools/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt