Luma: Post V1 Calendars Events Add

Add or submit an existing event, on Luma or elsewhere, to a Luma calendar.

Tool ID: luma_post_v1_calendars_events_add

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'luma_post_v1_calendars_events_add',
  {
    "platform": "external",
    "url": "https://example.com",
    "name": "Example",
    "start_at": "2026-01-15T12:00:00Z",
    "duration_interval": "example",
    "timezone": "America/New_York"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute luma_post_v1_calendars_events_add --input '{
  "platform": "external",
  "url": "https://example.com",
  "name": "Example",
  "start_at": "2026-01-15T12:00:00Z",
  "duration_interval": "example",
  "timezone": "America/New_York"
}' --json

Example response

The SDK returns this shape at result.toolResponse.raw. The example values illustrate the response.

{
  "data": {
    "id": "id_123",
    "status": "approved"
  }
}

Use deepline describe luma_post_v1_calendars_events_add --json for the latest machine-readable contract.

Input reference

Add or submit an existing event (on Luma or on an external platform) to the Luma calendar. By default, events added by a calendar manager are approved immediately. Use submission_mode: "pending" to keep the submission pending. On calendars with require-manage-access, submitting a Luma event you manage can also grant the target calendar manage access once the submission is approved.

Name	Type	Required	Default	Details
`payload.platform`	`"external" \| "luma"`	Yes	—	Allowed: `external`, `luma`.
`payload.submission_mode`	`"auto" \| "pending"`	No	`"auto"`	`auto` approves the event immediately. `pending` keeps the event pending for calendar admin approval. Allowed: `auto`, `pending`.
`payload.url`	`string`	No	—	—
`payload.name`	`string`	No	—	—
`payload.start_at`	`string`	No	—	ISO 8601 Datetime. For example, 2022-10-19T03:27:13.673Z Format: `date-time`.
`payload.duration_interval`	`string`	No	—	ISO 8601 Duration. For example, PT2H
`payload.timezone`	`string`	No	—	IANA Timezone, e.g. America/New_York. https://en.wikipedia.org/wiki/List_of_tz_database_time_zones
`payload.geo_address_json`	`object \| null`	No	—	—
`payload.host`	`string`	No	—	—
`payload.geo_longitude`	`number`	No	—	—
`payload.geo_latitude`	`number`	No	—	—
`payload.coordinate`	`object`	No	—	—
`payload.event_id`	`string`	No	—	Event ID, this usually starts with evt-
`payload.event_api_id`	`string`	No	—	Use `event_id` instead.

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`object`	Yes	—	Provider response payload.
`result.data.id`	`string`	Yes	—	—
`result.data.status`	`"approved" \| "pending"`	Yes	—	Allowed: `approved`, `pending`.
`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.

​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