Worknano

How to call the Worknano API

Updated 2026-10-15

This lives in the docs hub, not as a Config tab and not as a separate menu item. Every module uses the same HTTP shape: task, deal, contact, or a model you add later.

Daily product work still happens in the app. Use this when another system must read or write a record. Inside the workspace, a workflow step calls an endpoint. Store keys in Secrets.

How to read and list

  1. Read one record: GET /api/v1/object/task/123. Swap task for the model name and 123 for the id.
  2. List records: GET /api/v1/objects/task?status=ACTIVE&_limit=50. Filter with query fields the model already has.
  3. Do the same for deal, contact, or any other model. You do not learn a new path per module.

How to create, update, and delete

  1. Create: POST /api/v1/object/task with a JSON body of the fields you want to set.
  2. Update: PATCH /api/v1/object/task with the id and the fields that changed.
  3. Delete: DELETE /api/v1/object/task/123.

You do not invent a new verb or a new path for tickets, ideas, or a model you added in Config. Swap the model name. Prefer existing fields. See Models.

How this ties to the app

  1. Open Config → Integrations. Add the URL, method, and auth. Mapping of the body and the reply sits on the workflow step.
  2. On a record, click the ⋮ action that runs that workflow. You do not write a one-off page handler.
  3. If the step fails, open the API log on that same Integrations screen. You see request, response, status, and duration.
  4. Keep API keys in Secrets, not in the page.

Back to Config or the docs map.

To let AI apps such as Claude, Cursor or Codex work in the workspace, see MCP.