← HefflCONTENT HISTORY

Update to Heffl

Snapshot Oct 24, 2026 · 13:45 UTC · version 1.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Heffl and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Create field-service jobs, contracts, recurring maintenance visits, and customer properties in Heffl, or report on scheduled service visits.",
  "included_files": [],
  "name": "heffl-field-service",
  "skill_md_contents": "---\nname: heffl-field-service\ndescription: \"Create field-service jobs, contracts, recurring maintenance visits, and customer properties in Heffl, or report on scheduled service visits.\"\n---\n\n# Field-service jobs and visits\n\nRead ../heffl-crm/references/operating-rules.md. Canonical objects: fs_jobs, fs_properties, fs_schedules, clients, products. Describe fs_jobs on its write/create surface once; resolve the named client and list the requested service in products. Use the actual returned product ID and price.\n\nList fs_properties filtered by the resolved clientId and inspect name, address and city to select the intended site. Do not search globally by customer name. Clarify only remaining ambiguity. If no site exists, describe fs_properties and collect required address data before creating one.\n\nCollect missing service date and price together. Do not invent dates or reuse historical pricing unless requested. A zero catalogue price does not imply the service is free. Create a normal one-off with records_create, object:\"fs_jobs\", values including type:\"ONEOFF\", fsPropertyId, startDate and requested service lineItems. The client is derived from the property; do not send clientId. Do not send generated numbers, totals or status. Use productId:null for a free-text service.\n\nOmit fsSchedules unless custom visits are explicitly requested; the server generates visits and IDs. Dates use YYYY-MM-DD. All-day visits omit startTime/endTime; timed visits supply both as ISO timestamps in the workspace timezone. Contracts use type:\"CONTRACT\" and require endDate. Supply frequencyRule only for requested recurrence; paymentsCount must be nonnegative and no greater than visit count. Resolve assignees only when named.\n\nFor reports describe unfamiliar read fields once. Filter jobs directly by clientId and preserve requested visit date versus completion date semantics. Do not add invoiceRequired or count parent job totals once per visit. Return the actual receipt and link; do not claim that a timeout proves creation failed.\n"
}

SHA-256 of public snapshot: c89e1b9065e8f70b594680e54079a554dd0ced2c6b84fd6e1705429828b68fd5