Attention: List Recorder Meetings

List Recorder Meetings.

Tool ID: attention_list_recorder_meetings

Run this action

Use the TypeScript SDK for a single call. Put ctx.tools.execute(...) inside a Play when the call should be durable, scheduled, or run across a CSV.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'attention_list_recorder_meetings',
  {
    "fromDateTime": "2026-01-15T12:00:00Z",
    "toDateTime": "2026-01-15T12:00:00Z"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute attention_list_recorder_meetings --input '{
  "fromDateTime": "2026-01-15T12:00:00Z",
  "toDateTime": "2026-01-15T12:00:00Z"
}' --json

Example response

The static output schema is not detailed enough to generate a reliable example. Use deepline tools get attention_list_recorder_meetings --json for the complete live contract.

Input reference

Returns a cursor-paginated, deduplicated list of calendar meetings for the authenticated organization with the recording status of each meeting and each org participant. One row per calendar event. Intended for bulk export to data warehouses and analytics pipelines. Requires an organization-level API key — user-scoped keys are rejected. ### Window * fromDateTime and toDateTime are required and must define a window of at most 90 days. * When upcoming=true, results are ordered ascending by date; otherwise descending. UUID is used as a stable tiebreaker for same-date meetings. ### Pagination * Cursor-based. The first page is requested with no cursor. The response’s nextCursor is passed back unchanged on the next call. * When the response has no nextCursor, the iteration has reached the end of the dataset. * size is clamped to a server-side maximum of 200 (default 50). * See the live schema below for the complete notes.

Name	Type	Required	Default	Details
`payload.fromDateTime`	`string`	Yes	—	Window start (inclusive), ISO 8601 date-time, e.g. `2026-04-01T00:00:00Z`. Format: `date-time`.
`payload.toDateTime`	`string`	Yes	—	Window end (inclusive), ISO 8601 date-time. Must be after `fromDateTime` and within 90 days of it. Format: `date-time`.
`payload.cursor`	`string`	No	—	Opaque cursor returned by a previous call. Omit on the first page.
`payload.size`	`integer`	No	—	Items per page. Defaults to 50. Server-side maximum is 200; values above are clamped.
`payload.upcoming`	`boolean`	No	—	When `true`, returns meetings whose start time is in the future (ascending order). Defaults to `false` (past meetings, descending order).
`payload.filter`	`object`	No	—	Restrict the dedup pass to meetings involving any of the given user UUIDs. UUIDs not belonging to the authenticated organization are silently dropped; if none survive, an empty page is returned to avoid cross-tenant membership probing.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.items`	`array`	Yes	—	Page of meetings ordered by date (ascending when upcoming=true, descending otherwise) with UUID as tiebreaker.
`result.data.items[].uuid`	`string`	Yes	—	Calendar event UUID. Acts as the deduplication key.
`result.data.items[].conversationUuid`	`string`	No	—	Conversation UUID. Populated only when a recording exists (status=recorded).
`result.data.items[].summary`	`string`	Yes	—	Meeting title.
`result.data.items[].date`	`string`	Yes	—	Meeting start time, ISO 8601. Format: `date-time`.
`result.data.items[].userUuid`	`string`	Yes	—	UUID of the user attributed as the recorder. Falls back to the first event participant when no recording exists.
`result.data.items[].userName`	`string`	Yes	—	Display name for userUuid.
`result.data.items[].status`	`string`	Yes	—	Attention’s native status code. Clients map this to their own taxonomy. See the endpoint description for the current set of values.
`result.data.items[].statusLabel`	`string`	Yes	—	Human-readable label for the status, resolved server-side.
`result.data.items[].participants`	`array`	Yes	—	Every org user invited to the event with their per-user recording status.
`result.data.items[].participants[].userUuid`	`string`	Yes	—	—
`result.data.items[].participants[].userName`	`string`	Yes	—	—
`result.data.items[].participants[].status`	`string`	Yes	—	Per-user status. Same code space as the meeting-level status; can differ from it (e.g. a meeting may be `recorded` while a particular user is `not_join_when_alone`).
`result.data.items[].participants[].statusLabel`	`string`	Yes	—	—
`result.data.items[].consentLinkUsed`	`boolean`	No	—	Whether the meeting used an Attention consent link.
`result.data.items[].consentStatus`	`string`	No	—	consented \| declined \| no_response, when consentLinkUsed is true (no_response = a consent link was used but no attendee acted). Null when consentLinkUsed is false (no consent link).
`result.data.nextCursor`	`string`	No	—	Opaque cursor for the next page. Absent (or empty) when the iteration has reached the end of the dataset.
`result.meta`	`object`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

Get started

Build and automate

Common workflows

Data and integrations

Reference

Attention: List Recorder Meetings

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation