Skip to content

skill: Knowify vendor bills (private API, replace semantics, QuickBooks trap) - #571

Open
axelclark wants to merge 1 commit into
browser-use:mainfrom
axelclark:skill/knowify-bills
Open

skill: Knowify vendor bills (private API, replace semantics, QuickBooks trap)#571
axelclark wants to merge 1 commit into
browser-use:mainfrom
axelclark:skill/knowify-bills

Conversation

@axelclark

@axelclark axelclark commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Adds domain-skills/knowify/bills.md from a real session driving a vendor-bill edit in Knowify (secure.knowify.com — construction accounting; AngularJS SPA over api.knowify.com).

What's in it, all verified against the live app rather than inferred:

  • Learn a request shape without a capture or a write — recipe for pulling the whole API registry and its call sites out of the main bundle. verb is the path prefix, the key is the endpoint name.
  • Stable selectors for the bill edit form, plus the fact that modals render inside <k-modal-target>, so a document-wide input[type=checkbox] scan misses them entirely.
  • A 0×0 checkbox trap. The "Send to QuickBooks" input is visually replaced by a styled <label for=…>, so getBoundingClientRect() on the input returns 0,0 and a coordinate click there does nothing. It also defaults to CHECKED — submitting without unticking pushes the bill to QuickBooks, which isn't reversible from the browser. Includes the label-click snippet and the assertion to make afterward.
  • Payables/updatePayable is replace-not-update. The old bill id stops existing, every line-item id changes, and NewId is populated only sometimes. Two things don't survive on their own: the attached PDF (echo SupportingDocuments verbatim) and the generated billable (regenerate with Payables/createBillablesBill; allocatePayable reports success without creating one).
  • Payables/updatePayableItem silently ignores Description while returning DidSucceed:true — it's allocation-only. Easy to waste time on.
  • Read endpoints worth starting from, including the non-obvious detail that already-invoiced billables drop out of GetBillablesForProject, so a lower count than expected on a billed job is normal.

No credentials, cookies, or account-specific data — selectors, endpoints, and payload shapes only, per the domain-skills guidance. No raw pixel coordinates.


Summary by cubic

Adds domain-skills/knowify/bills.md, a focused guide for editing Knowify vendor bills via the private API, with safe selectors and key traps to avoid. Helps prevent accidental QuickBooks sync and clarifies replace semantics in Payables/updatePayable.

  • New Features
    • How to pull the API registry and call sites from the main bundle; map to api.knowify.com/<verb>/<name>.
    • Stable edit-form selectors; modals render inside <k-modal-target>.
    • QuickBooks trap: the confirm dialog’s checkbox is 0×0; click its label instead. It defaults to checked—assert the state before saving.
    • Save flow: Payables/updatePayable replaces the bill (IDs change, NewId may be null). Echo SupportingDocuments and regenerate the billable via Payables/createBillablesBill; Indexing/allocatePayable won’t create one.
    • Payables/updatePayableItem ignores Description (allocation-only).
    • Useful reads to start from: Payables/Get, Payables/searchPayablesIds, Invoices/GetBillablesForProject (already invoiced items drop out).

Written for commit f173b3d. Summary will update on new commits.

Review in cubic

…oks trap

Knowify (secure.knowify.com) is an AngularJS SPA over api.knowify.com. Documents what cost
several steps to work out while driving a real bill edit:

- Recipe for pulling the whole API registry + call sites out of the main bundle, so the next
  agent can learn a request shape without a live capture or a write.
- Stable selectors for the bill edit form, and the fact that modals live in <k-modal-target>
  (a document-wide checkbox query misses them).
- The "Send to QuickBooks" checkbox is a 0x0 input replaced by a styled label, so
  getBoundingClientRect on the input returns 0,0 and clicking there silently does nothing.
  It also defaults to CHECKED — submitting without unticking pushes the bill to QuickBooks,
  which is not reversible from the browser.
- Payables/updatePayable is replace-not-update: the old bill id stops existing, every line
  item id changes, and NewId comes back only sometimes. Two things don't survive on their own
  (the attached PDF, and the generated billable).
- Payables/updatePayableItem returns DidSucceed:true but silently ignores Description — it's
  allocation-only. Worth knowing before using it to edit text.
- The read endpoints worth starting from, including which billables drop out of
  GetBillablesForProject once invoiced.

No credentials, cookies, or account-specific data — selectors, endpoints, and payload shapes
only, per the domain-skills guidance.
@browser-harness-review

Copy link
Copy Markdown

✅ Skill review passed

Reviewed 1 file(s) — no findings.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 1 file

Re-trigger cubic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant