LiteLog

Use this to cancel one planned shift without check-ins (see list_shifts); its people get a push message and it is not generated again. Returns a preview + confirm_token; repeat with it once the user agrees. May notify people according to the company's automation rules.

cancel_shift

Call first for how-to questions and where things are in the portal. control_points: chips, QR codes, beacons, GPS; property_settings: wizard, menu, dashboard, Unterlagen, Nachweise, settings page, deviations, modules; places: Orte, pin, area, zones, plans, app; time_tracking: clock-in, web, tablet.

get_catalog

Use this to acknowledge, close or reopen an incident report (incident_id from list_incidents). closed also acknowledges; open only takes back the closing. May notify people according to the company's automation rules.

set_incident_status

Use this to rename, re-icon, re-colour, hide or show ONE rail point of the company main menu; the rest of the menu stays. null restores the default. The answer lists before and after. Does not notify anyone.

update_nav_rail_item

Use this to move a task to another status, e.g. done; task_uuid from list_tasks, state_id from list_task_states. Proof-bound completion and "not feasible" (reason, photo) happen in the LiteLog app only; get_task_activity shows them. May notify people according to the company's automation rules.

set_task_state

Use this to check 1 to 20 people into a shift that is running now ("Anna and Ben are on site"). Only live: not before the start, not after the end (use create_time_entry then). May notify people according to the company's automation rules.

checkin_shift

Use this before planning: for given people and a time (ISO 8601 with offset) it lists double bookings, absences and working-time limits (rest period, daily or weekly hours). Pass exclude_shift_uuid when moving an existing shift.

check_shift_conflicts

Use this to choose the template of the portal main menu for the company (see preset). It applies only while no company menu is saved; company_menu_saved tells whether reset_nav_layout is needed. Rights and modules still decide what is shown. Does not notify anyone.

set_nav_preset

Use this when someone starts work now ("clock me in at …"): opens a running time entry at the property, like the app or a terminal. Always now, never backdated; for past times use create_time_entry. May notify people according to the company's automation rules.

clock_in

Use this when someone stops work now ("clock me out"): ends the running time entry at the property with the pause rules of the company. Always now; to correct a past end use update_time_entry. May notify people according to the company's automation rules.

clock_out

Use this to see what changed between two submitted forms, e.g. a move-in and a move-out protocol: per field both values with a verdict (new, preexisting, fixed, changed, unchanged, not_rated). The older response is always left.

compare_form_responses

Use this first to learn who the connection acts as: the account, the company, the module access levels, the available tools and whether the licence has expired. get_catalog topic permissions explains modules, ai_connection the connection itself (setup, log, disconnecting, cost).

get_connection_info

Use this to see which control points (scan points) lie where on one floor plan: position (x, y as 0–1), name, type, area, chip-missing hint. Default: points not archived; include_archived adds archived ones. Tasks on the plan: get_floor_plan_pins.

get_floor_plan_control_points

Use this to plan a tour: one drive across several properties with stops in order, each with an arrival offset and a tolerance window, and optional schedules; runs are generated like in the portal. Does not notify anyone.

create_tour

Use this to add a control point: area (only if named), position, GPS radius, plan_pin; unique name per property. Its patrol QR (not the clock-in QR) exists at once. New NFC chip only in the app: Mehr → Einstellungen → NFC anbinden. May notify people according to the company's automation rules.

create_control_point

Use this to add an area (floor, wing) to a property once the user confirmed it; points join it via create_control_point/update_control_point (area_id). Name unique per property. Not a floor plan (Grundriss): plans are uploaded in the portal only, as are order and deletion. Does not notify anyone.

create_control_point_area

Use this to create a form or checklist template as a draft (a person publishes it in the portal); get_form_template shows a model. Repeat with the same idempotency_key (UUID). A change_reason is optional and audited.

create_form_template

Use this to report an incident at a property: a ticket with reporter, source and time; create_task_from_incident makes it a task. property_id from list_properties. A repeated call creates a second report; check list_incidents first. May notify people according to the company's automation rules.

create_incident

Use this to create single units (keys, devices) of a serialized item, up to 50 serial numbers at once; existing numbers come back as conflicts. May notify people according to the company's automation rules.

create_material_units

Use this to create a material item (without item_id: name and unit required) or to change name, unit, category or size of one (with item_id; null clears). No prices. May notify people according to the company's automation rules.

save_material_item

Use this to set up a patrol route: the control points (ids from list_control_points) a person scans in one time window, and its repetition. Pass dry_run to preview the next runs without writing. The answer names the next runs. May notify people according to the company's automation rules.

create_route

Use this to create one property (site, building) with its settings groups (get_catalog explains them); omitted groups take company defaults. Refuses a name that exists unless allow_duplicate_name. Report missing, next_step to the user. May notify people according to the company's automation rules.

create_property

Use this to add a qualification (licence, training, certificate) to the catalogue of the company; assign it to people with set_account_qualifications. The name must be unique; update_qualification renames, deleting stays in the portal. Does not notify anyone.

create_qualification

Use this to add up to 200 control points to one property from a list; area only if the user names one (ask before new areas). Known or repeated names are skipped. Returns a preview + confirm_token; repeat with it once the user agrees. May notify people according to the company's automation rules.

create_control_points

Use this to create 1 to 20 properties (fields as create_property); checked first, one invalid = none created, known names skipped, rows name what is still missing. Returns a preview + confirm_token; repeat with it once the user agrees. May notify people according to the company's automation rules.

create_properties

Use this to plan 1 to 50 shifts in one call, each like create_shift with its own idempotency_key; all are checked first, one invalid = none created. Returns a preview + confirm_token; repeat with it once the user agrees. May notify people according to the company's automation rules.

create_shifts

Use this to plan one shift at a property, optionally with its people (list_people). Times are ISO 8601 with offset. Double bookings, absences and working-time rules are reported, not blocked. Repeat with the same idempotency_key (UUID). May notify people according to the company's automation rules.

create_shift

Use this to create a task: assignees (people and/or roles), checklist, photo requirement, control points (its place, see list_control_points), map_pin, schedule = routine task, none = one-off. Same idempotency_key = same task. May notify people according to the company's automation rules.

create_task

Use this to turn an incident report into a task (incident_id from list_incidents). One task per report: a repeated call returns the existing task with created false. Title, text and priority default to the report. May notify people according to the company's automation rules.

create_task_from_incident

Use this to record a finished working time for a person at a property, e.g. a forgotten clock-out. Needs a reason; at most 45 days back and 24 hours long. Overlaps and blocked times are refused, never overridden. May notify people according to the company's automation rules.

create_time_entry

Use this to approve, reject, deliver (fulfill: books the stock) or cancel your own material request (request_uuid from list_material_requests). Returns a preview + confirm_token; repeat with it once the user agrees. May notify people according to the company's automation rules.

decide_material_request

Use this to approve or reject an absence (see list_absences), also to take back an approval. Rejecting needs a decision_note. Returns a preview + confirm_token; repeat with it once the user agrees. May notify people according to the company's automation rules.

decide_absence

Use this to delete a finished time entry booked by mistake. Needs a reason, kept in its history. Entries older than 45 days or confirmed ones stay in the portal. Returns a preview + confirm_token; repeat with it once the user agrees. May notify people according to the company's automation rules.

delete_time_entry

Use this to end a patrol route: no runs after last_run (default today); past patrols stay. Uses the change approval of the company. Returns a preview + confirm_token; repeat with it once the user agrees. May notify people according to the company's automation rules.

archive_route

Use this to create the shifts of an existing series (series_id from list_shifts) for at most 92 days; filled or cancelled days and holidays are skipped. Returns a preview + confirm_token; repeat with it once the user agrees. May notify people according to the company's automation rules.

generate_shifts

Use this after list_floor_plans to read one floor plan: name, area, size, pin counters and signed URLs of the image and a preview that expire within 1–2 hours (url_expires_at). Also archived plans.

get_floor_plan

Use this to see the company default of the start screen in the LiteLog app: which widgets and quick-action tiles show and in which order. catalog lists the valid keys for set_app_dashboard_layout.

get_app_dashboard_layout

Use this after list_workflow_runs to see where one run delivered: channel (email, sms, call, push, in_app), masked recipient (j***@firma.de, +49 *** ** 12), status and time. Never the plain recipient or error text.

get_workflow_run

Use this to see which control points were scanned on which day and which were missed, per property. from and to are YYYY-MM-DD, at most 14 days. Returns scan counts per point and totals for the range.

get_checkpoint_coverage

Use this to see how each property is staffed right now: people present, running shifts, the staffing target and whether it is met. Returns numbers only, no names; use list_shifts for the people planned.

get_occupancy