calendar:schedule-meeting

Sends a scheduling email to a contact and returns status

Effect: signal; Fire-and-forget — the call returns once accepted, not once done.
Caller: session; The class of authority the caller must already hold, decided from the attested context with no round trip.
Reversible: no; This cannot be undone. Dry-run it first where the contract allows.

Send it with your agent

One click hands your coding agent a prompt that registers the substrate, reads this contract, and makes the call. Launch opens the app; the others copy the prompt.

Claude Code

Codex

Cursor

Gemini CLI

Claude Desktop

ChatGPT

curl -X POST https://one.ie/api/signal/calendar:schedule-meeting \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "amountLabel": <any>, "email": <any>, "name": <any>, "stepName": <any> }}'

The key is never in a link. npx -y @oneie/cli login writes it to ~/.config/oneie/key on your machine.

Request

Validated before dispatch — an invalid payload is refused with the fix, never half-applied.

amountLabel any optional
email any optional
name any optional
stepName any optional

Response

The acknowledgement shape — the work itself completes after the call returns.

No declared fields.

Traffic

Every call to calendar:schedule-meeting, counted where it is dispatched — over HTTP or in-process alike. Aggregate only — no actor, no payload, no workspace.

Counting…

Wiring

Every place in the open source that names calendar:schedule-meeting, and the file that answers it. Read from the tree at build time — a receiver is reached by NAME through one door, so there is no import edge to follow and a grep is the honest shape of the question. Structure, not volume — the count is in Traffic above.

Called from

UI 1

one.ie/web/src/components/in/detail/ActorContent.tsx:598

API route 1

one.ie/web/src/lib/receiver-index.generated.ts:60

→

Answered by

calendar:schedule-meeting one.ie/web/src/lib/resolvers/messaging.ts:1240 Dispatched through POST /api/signal/calendar:schedule-meeting, after the envelope validates the payload.

JSON Schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "amountLabel": {},
    "email": {},
    "name": {},
    "stepName": {}
  },
  "additionalProperties": {}
}

{
  "$schema": "https://json-schema.org/draft/2020-12/schema"
}