Atwork

Give a team or a member a role on a space (its folders and sheets follow) or on one sheet. The caller needs Admin access there. Always asks the user first.

Who can use a space or a sheet, and with which role. Each entry's aclId is what access.update and access.revoke take.

Remove one access entry (a team, a member or everyone) from a space or a sheet. Read the entries with access.read first. On a space, its folders and sheets lose that access too. Always asks the user first; afterwards tell the user which role was removed.

Change the role of one access entry on a space or a sheet. Read the entries with access.read first. The caller needs Admin access there. Always asks the user first.

Create a custom app: a named page holding existing views, forms, pages and dashboards, in order. It starts as a draft; app.publish (asks first) makes it live.

Publish a custom app so the people it is shared with can open it. Always asks the user first.

Take a custom app offline: it goes back to draft and the people it is shared with can no longer open it. app.publish puts it back. Always asks the user first.

Add the user's own time off (type ooo: whole days, shown in the calendar, on the profile and in Settings → Availability; booking pages offer no slots) or a focus block (type focus: a day or a time range, shown in the calendar). Dates and times are in the user's profile timezone.

Remove one of the user's own time off or focus blocks by id (from availability.read). Time off is removed from the calendar, the profile and Settings → Availability. The removal is permanent; the output holds the input to re-create it.

List the user's own time off and focus blocks between two days (default: the next 30), with their ids, shown in the user's profile timezone. Read before availability.delete.

Create a booking link (a public page where people book a meeting with the user; guests fill in its form, and each booking becomes a row in the user's Bookings sheet). Slots follow the user's working hours. Pass hours when the user named the hours the link should offer; when they differ from the working hours the result says so, and only working_hours.update can change them.

Change one of the user's booking links: its title, meeting length, how many days ahead people can book, or turn it off (active: false) and on again. Name the link by its title or id.

Add a personal calendar for the user (My Calendars in the calendar sidebar) with a name, an optional #RRGGBB colour and free/busy-only visibility. A calendar with the same name is returned instead of a second one.

Return a structured meeting prep brief — linked work, attendees, context, open threads — plus an optional 1-paragraph summary. Retrieval is deterministic graph traversal from Schedulable.itemRef outward via internal *-agent libs. The LLM is a renderer only — it never decides what to fetch. Read-only.

Propose ranked meeting time slots given duration, window, attendees and ranking strategy. Returns deterministic free-busy-derived slots; the top 3 carry a short LLM-written 'why' string when includeWhy is true. Each slot lists teammates by attendeeUserId and external attendees by externalIndex, their position in externalAttendeeEmails. Read-only — never creates an event.

List the user's calendar events in an inclusive date range. Optionally restrict to one calendar by id. Returns up to limit event objects with id, summary, startDate/endDate (and times if present), dueDate, assigneeId + assigneeName, calendarId + calendarName, location, and an optional truncated content. Prefer the *Name fields in user-facing prose; the *Id fields are FKs for follow-up tools.

Rename one of the user's own personal calendars, or change its #RRGGBB colour or free/busy-only visibility; by id or name. Connected (Google) and shared calendars are not changed here.

Post a comment on an item, named by its sheetId and item id (uuid). The comment is attributed to the agent (visible as 'AI commented'). The user can delete the comment from the item's activity log.

Create a custom agent: a teammate with its own instructions, capabilities and, with sheetIds / spaceIds / pageIds, a limited view of the workspace. Owner or an Admin only. Always asks the user first.

Add an empty dashboard to a sheet; it shows as a Charts view. Then add charts and numbers with widget.create. To build a sheet together with its dashboards, use steps.draft instead.

Delete a dashboard with its widgets and its Charts view. This always asks the user first: say which dashboard goes before you call it. dashboard.restore brings it back.

Read a dashboard's structure: returns dashboard (id, title, description, sheetId + sheetName when bound to a sheet) and widgets[] (each id, title, type, optional summary). Set includeWidgetData=true to also fetch each widget's current rendered numbers — slower, only needed when answering questions ABOUT the numbers (totals, trends, breakdowns) rather than the layout. Without it you save a fetch per widget.

Bring back a deleted dashboard with its widgets and its Charts view, by the sheetId and dashboardId dashboard.delete (or view.delete) returned.

Change a dashboard's name, icon, description or filter (the sheet.read filter form; every widget counts only those rows; null clears it). Only what you pass changes; its widgets stay.

Finish a file upload started with file.request_upload, after the bytes have been PUT to the presigned URL. Returns the stored filename — add that value to a File List field or set it as a Cover.

Start a file upload. Returns a presigned URL — you must then PUT the file's bytes to that URL yourself, with Content-Type set to the mime you gave (upload_headers), and finally call file.confirm_upload with the returned key. Images (image/png, image/jpeg, image/webp), a PDF (application/pdf, private only — e.g. a LinkedIn document post) or an MP4 (video/mp4, private only — e.g. a social video), max 10MB. Use visibility: "public" for anything that must load on a website.

Create an empty folder in a space, at the top or inside parentFolderId. Ids come from workspace.structure.

Delete a folder with its subfolders and the sheets and pages inside them. This always asks the user first: say what is inside before you call it. folder.restore brings it all back.

Bring back a deleted folder with the subfolders, sheets and pages its delete removed. Restore the folder it was in first when that one is deleted too.

Rename a folder, change its icon or description, or move it inside another folder of the same space. Only the settings you name change. Ids come from workspace.structure.

Add a form (a peek of kind form) to an existing sheet: each submission becomes a row. fields are field names or codes in order, or { field, required, label, help, placeholder, width } (width 25, 50, 75 or 100 percent of the row in the classic layout). layout: classic (default; fields side by side by width) or steps (one question at a time). Optional submitLabel, description above the questions and successMessage after sending. Fields must already exist on the sheet (add them with sheet.add_attribute first). Theme, accent and header: peek.update_options. Publishing it and its public link stay in the form builder.

Delete a form (a peek of kind form) from a sheet; the rows it collected stay; a record layout is refused. This always asks the user first: say which form goes before you call it. form.restore brings it back with its questions and settings.

Bring back a deleted form with its questions and settings, by the sheetId and formId form.delete returned. A record layout (how a row opens) is refused.

How a form is doing: views (public page loads), starts (first field typed), submissions (rows the form added), the same three for the previous equal period, the median time to finish, submissions per day for the last 14 days, and how many who started reached each question with the question that loses the most people. Use for questions like 'how is my inquiry form doing?' or 'where do people drop off my form?'. Pass the form's peekId (sheet.schema lists a sheet's forms).

Change a form (a peek of kind form: it collects new rows): name, description, addFields (names or codes, or { field, required, label, help, placeholder, width }, added at the end), removeFields, editFields (a question's label, required, help, placeholder or width: 25, 50, 75 or 100 percent of the row in the classic layout), order (every question in the new order), layout (classic, or steps: one question at a time), submitLabel (the Submit button's text), visibleWhen (per question: show it only when a sheet.read-style filter on the answers holds; when: null always shows it) successMessage, aiReply (the thank-you screen shows Dana's reply written from each person's answers: a plain-text prompt where {Field name} stands for an answer, and a fallback shown when it is slow; null goes back to the message) and redirect (send people to a web page after they submit; put answers in the link as {Field name}; null goes back to the message). onResponse turns the response emails on or off: notify emails the people you name (members; default you) one email per response with the answers, copy emails the respondent their answers at an Email field on the form (a form anyone with the link can fill needs Block spam first). Pass aiReply or redirect, not both. Only what you pass changes; the other questions and settings stay. Without formId it changes the form open in Form Studio. A record layout (how a row opens) is refused: change it with the peek.* tools. Theme, accent and header: peek.update_options. Publishing, and blocks (a heading, text, image, divider or section), stay in the form builder.

Create a goal on the Goals page: personal or for the organization, measured by completed tasks, by a sheet's rows (count, or sum / average of a number field), or not measured.

Replace a sheet's inbound email address with a new random one, e.g. when the old one gets spam. The old address stops working. Always asks the user first.

Rename a sheet's inbound email address (the address that turns emails into rows). The old address stops working. Always asks the user first.

Discover what the workspace's connected integrations can do. Call with no arguments for the connected providers and their operations. Pass provider to get that provider's operations WITH their field schemas. Each operation reports access: run read ones with integration.query, write and destructive ones with integration.execute (a destructive one deletes, archives or overwrites, and the user approves it every time). Fields marked dynamic need integration.list_options before use. Use the provider value exactly as returned here when calling the other integration tools. Connections marked mine: true belong to the current user; prefer those. When more than one applies, show the user the labels and let them choose — never ask which connection to use without listing the options.

Resolve the valid values for a dynamic field — one marked dynamic by integration.list_operations, e.g. the Slack channels you may post to. Returns [{value, label}]; pass the value in params.

Run a READ integration operation, e.g. list Slack channels or fetch channel history. Only operations integration.list_operations reports with access read are allowed — use integration.execute for write and destructive ones. credentialId is optional when the provider has exactly one connection.

Archive (archived: true) or unarchive (archived: false) up to 50 rows of a sheet. An archived row keeps all its data but leaves default reads and search, sends no reminders and fires no workflows; unarchiving brings it back. Read archived rows with sheet.read and archived: "only".

Create a row (item) in any sheet using HUMAN VALUES for its fields — you don't need ids. Provide sheetId and a fields map of attribute name→value; option/select/status/member/team/job values are resolved to the sheet's real values, and an unrecognised value returns an error listing the valid options rather than guessing. Document/Description fields accept MARKDOWN and are stored as rich text. Blocking / Blocked By take item titles, Index (#10) or ids from the same sheet. Returns {itemId}.

Create many rows (items) in one sheet in ONE call — use it instead of repeated item.create_humanized whenever you add more than one row (e.g. "add these 50 leads" from a pasted list). Each row is a fields map of attribute name → HUMAN VALUE, resolved exactly as item.create_humanized does. Up to 200 rows per call; for more, make several calls. A row whose value cannot be resolved, or that matches an existing row by a unique field, is skipped with a reason and the rest are created. Workflows on the sheet run for every created row, as for a row added by hand. The whole call is one batch: item.undo_batch with the returned batchId and sheetId removes every row it created. Returns { batchId, created, skipped, skippedCount, url } — tell the user the counts and the skip reasons.

Read the text of the files on one row: uploads in its File List fields, and Google Drive files the user linked themselves. Reads up to 5 files (10 MB each) in field and cell order until the text budget is spent; more counts the rest — pass attribute to read one field. PDF, DOCX, XLSX, PPTX, CSV, text, and Google Docs, Sheets and Slides are read. An audio upload is listed under unreadable to transcribe with audio.transcribe. A Drive file another member linked, an image, or a file that cannot be read is listed under unreadable with why (and the Drive link): tell the user, and never guess what it contains.

Copy a sheet (structure and rows), a page, or a folder with what is in it, into a space or folder. Ids come from workspace.structure.

Move a sheet or page to another space or folder, or a folder inside another folder of its space. Ids come from workspace.structure. Returns where it now sits, by name.

Undo a whole batch written by item.create_many, item.update_many or item.update_where, in one step, naming the batchId it returned and the sheetId it wrote: a create batch deletes the rows it created that still exist; an update batch restores each field's previous value unless it was changed since (those are reported as conflicts and kept). Only the user who ran the batch (or the org owner) can undo it, once, within 7 days. Use it when the user asks to undo a bulk change. Effects workflows already had (emails, external calls) are not reverted.

Update a row (item) using HUMAN VALUES. Provide sheetId, itemId, and a fields map of attribute name→value; only the given fields change. Option/member/etc. values are resolved to real ids (unrecognised → error listing valid options). Document/Description fields accept MARKDOWN and are stored as rich text. File List fields take the files the cell should hold: stored filenames from file.confirm_upload, or the entry objects sheet.read shows for this row; a replace drops the files it does not name. Blocking / Blocked By take item titles, Index (#10) or ids from the same sheet.

Update a LISTED set of rows (by id) in one sheet in ONE call — use it instead of repeated item.update_humanized whenever you change more than one row. Each row is { itemId, fields }; only the given fields change and values are HUMAN VALUES resolved as in item.update_humanized. Up to 200 rows per call. Rows that are not in the sheet, archived, read-only or have an unresolvable value are skipped with a reason and never changed; the rest are updated. Workflows on the sheet run for every updated row, as for an edit by hand. The whole call is one batch: item.undo_batch with the returned batchId and sheetId restores the previous values. Returns { batchId, updated, skipped, skippedCount, url } — tell the user the counts and the skip reasons.

Set the same field values on EVERY row of one sheet that matches a filter, in ONE call — e.g. "Country = Germany where Country is DE or Deutschland". Prefer it over reading rows and calling item.update_many whenever the rows to change are described by a condition. filter is { operator: AND|OR, conditions: [{ column, operator, value }] } (≤ 10 conditions, operators as in sheet.aggregate) and fields maps field name → ONE literal human value (≤ 30); columns take names or codes and option/member values are matched as in item.update_humanized. File List fields are set per row with item.update_many, not here. Rows already holding the values are left alone; archived and read-only rows are skipped. When more than 20 rows would change, the user confirms first: in a chat on a preview card (the call waits for it); over MCP the call is refused with ROWS_NEED_CONFIRM, the count and a sample, and nothing changes — show the user and call again with confirmRows set to that count only once they accept. At most 1,000 rows per call — narrow the filter otherwise. The change is one batch: item.undo_batch with the returned batchId and sheetId restores the previous values. Returns { batchId, updated, unchanged, skipped, skippedCount, url }.

Change the language the user's panel, emails and notifications are in: English or Farsi. Dana keeps answering in the language the user writes in.

Add a location (an office or branch) to the organization: its name and IANA timezone, with an optional address, city, state, country, zip code and phone number. main: true makes it the main location. The organization's Owner or an Admin only; always asks first.

Change one of the organization's locations, named by its current name or id: rename it, or change its timezone, address, city, state, country, zip code or phone number; main: true makes it the main location. Only the fields given change. The organization's Owner or an Admin only; always asks first.

List org members. Optionally filter by name prefix. Returns up to limit member objects (id, userId, fullName, teamId, teamName, jobId, jobName). teamName/jobName are the resolved display titles — use them in prose; the *Id fields are FKs for tools that need them. Note: AI-agent identities may appear in the list — exclude them when answering questions about people.

Owner only: change another member's profile (name, job title, @handle, pronouns, bio, phone number, status, timezone, out-of-office days). Always asks the user first. For the user's own profile use profile.update.

Read the user's notification switches: each category by in-app, push, email and Telegram. Categories: MENTION (@mentions), PAGE_COMMENT (page comment replies), TASK_ASSIGNEE (assigned to you), DUE_DATE, UPDATE_ITEM (changes to your items), MESSAGE (chat), REMINDER, DAILY_CLOSEOUT (end-of-day close-out), AGENT_DONE, AGENT_NEEDS_INPUT, BOOKING, SUPPORT_TICKET (replies to your support tickets). Also whether quiet hours are on.

Put every notification switch of the user back to the default: all on, Telegram off. Only when the user asks to reset them.

Turn the user's own quiet hours on or off: when on, push and email outside their working hours wait and arrive together when the day starts; in-app notifications still collect. Turning on needs working hours (working_hours.update). Turning off sends anything held. In Atwork's chat the user confirms the change on a card first.

Turn the user's notifications on or off per category and channel (inApp, push, email, telegram). Push is only the per-category switch; browser push itself is turned on in the browser. Telegram needs a linked chat first.

Change the organization's settings for everyone: its name, default language (en or fa), calendar (gregorian or jalali) and the day the week starts on. Only the fields given change. The organization's Owner or an Admin only; always asks first.

Save a draft as a real page in the workspace. markdown is the body — the server converts to BlockNote. Use AFTER drafting the prose in the conversation, when the user signals 'save it' / 'make this a page' / 'add it to ' — never speculatively. The page becomes live immediately; the user has 30 seconds to undo from the trace bubble. For a named destination pass its spaceId (find a space by name with workspace.structure); omit spaceId to save in the space the user is on.

Delete a page. This always asks the user first. page.restore brings it back with its content.

Patch an existing page with one of five targeted operations. append/prepend add markdown at end/start. append-to-section inserts at the end of a section (before the next heading) — use this when adding to a section, NOT replace-section. replace-section swaps a section's heading + body with new markdown; drops any non-text blocks (images/files) inside it. delete-section removes a section entirely. sectionHeading matches case-insensitive trim. Always call page.read FIRST so you know the actual heading text. The page changes immediately; the user has 30 seconds to undo.

Read a page's name, body (text, capped at 15,000 chars), cover, author, date and other metadata. Use when the user references a page by name ("the launch brief", "Sara's onboarding page") and you need the actual content to summarize, recap, translate, or quote. The bodyTruncated: true flag means content was clipped — for very long pages, ask the user which section they care about, or accept that you're working from the head of the page.

Bring back a deleted page with its content, in the place it was deleted from.

Rename a page, change its icon, set or clear its cover, author or date, or move it to another space or folder. Only what you name changes; edit the page's content with page.edit.

Append (or insert at index) an item into a record layout (how a row opens; a form is refused: change its questions with form.update). Types: 'attribute' (a field; pass attributeCode, one of the sheet's field codes from sheet.schema or peek.read), 'tabs' (a Tabs block; pass tabTitles, 1-8), 'related_rows' (the rows a Relation field links to; pass the Relation field's attributeCode and display list | table), 'history' (the row's change history), 'comments' (the row's comments). Pass tabId (from peek.read) to put any item inside that tab. Pass underTitle: true with type 'attribute' to show the field on the line under the record's title, at its end (at most 4 short fields: Status, Select, Date, Number, Email, Short Text, Modified at…; a field already on the layout moves there). 'header', 'welcome' and 'submit' are legacy form items and are refused on a record layout.

Read a peek and return its kind (form: it collects new rows; record: a record layout, how a row opens), its layoutStyle, its layout array and options. Items reference sheet attributes by code; a record layout also holds Tabs blocks (tabs, and tabId on the items inside a tab), Related rows (display), History and Comments, and marks the fields shown under the record's title underTitle: true. Use before changing a record layout with peek.add_layout_item, peek.remove_layout_item, peek.reorder_layout, peek.update_options or peek.update_field_options; a form is changed with form.update.

Remove an item from a record layout (how a row opens; a form is refused: take a question off it with form.update removeFields). Identify the item by layoutItemId (returned by peek.read) or by attributeCode (removes the first attribute item matching that code — useful for 'remove cover/icon'). Removing from the layout does NOT delete the underlying sheet attribute; use sheet.remove_attribute for that. Removing a field shown under the title takes it off the layout altogether; to move it back into the body instead, use peek.reorder_layout underTitle without it.

Reorder a record layout's (how a row opens) items by passing the full list of item ids in the desired order. Must be a permutation of the current layout (no missing or extra ids — call peek.read first to discover ids). For 'move X to top' or 'put Y after Z', read the layout, build the new id sequence yourself, and pass it here. Pass underTitle (item ids, in order, at most 4 short fields) to set exactly which fields show on the line under the record's title; fields left out go back into the body where they sit, and [] empties the line. orderedItemIds is optional with underTitle. A form is refused: reorder its questions with form.update order.

Patch per-field options on a single item of a record layout (how a row opens; a form is refused: change a question's label or required flag with form.update editFields): title override (the label for this field, separate from the sheet attribute name), isRequired flag, background, color, borderColor, borderSize, radiusSize, radius, align. Identify the item by layoutItemId (from peek.read) or attributeCode (matches first attribute item). Only included option keys are touched.

Patch a peek's options. A form (kind form): theme { preset workspace | paper | sand | ocean | forest | dusk, appearance auto | light | dark }, accent (a palette token color-N), header { logo, cover, width narrow | normal | wide, direction auto | ltr | rtl } and submit { label }; its questions and layout change with form.update. A record layout (how a row opens): color, accentColor, border, size, direction, rows, header text/background/size/align, and record — saving (auto | button), buttons { saveAndNew, discard, rowNav } (shown with a Save button), readOnly, openAs (panel | dialog | page), use { newRow (the layout + New uses; one per sheet, so true clears it on the sheet's other layouts), openAsMenu (listed in the Open as menu) }. record is merged key by key into the stored one. To make a layout the sheet's default when a row opens, use sheet.update defaultFormId. Pass only the keys you want to change — existing options are preserved. Booking-specific options are not exposed via this tool.

Set up the client portal (what customers see): title, welcome text, sign-in, and sections for an FAQ read from a sheet, a contact form and a contact card. Settings and sections not named are kept; a second FAQ or form on the same sheet updates the first. Owner or an Admin only. Always asks the user first.

Read the user's own preferences: language, theme, calendar, start page, sidebar, presence status, live-update toasts, chat history retention, pins and who sees each profile field.

Change the user's own preferences: theme, calendar (Gregorian or Jalali), start page, sidebar position and auto-hide, collapsed nav, presence status, live-update toasts, chat history retention, pins and who sees each profile field (profileVisibility). Only the keys given change. Language is not here: use language.update.

Change the user's own profile: first and last name, job title (from the organization's list), @handle, pronouns, bio, phone number, status line, timezone and out-of-office days. Only the fields given change. Who sees each field is a preference (preferences.update profileVisibility). Working hours: working_hours.update.

Find worked recipes for builds (a formula, rollup, rating or autofill field, dependencies, a board or filtered view, a CRM with a dashboard, a tracker with a page, a template, a booking link, the client portal, publishing a view, team access) and automations (email to a sheet, a scheduled item, notify on a new item or a status change, a daily digest, Slack or Telegram messages, Telegram notifications). Call it before drafting a build or an automation. Each recipe has the questions to ask when the request is ambiguous (ask), what must exist first (prerequisites), the tools to call, a template whose "<<name>>" strings you replace with values like the placeholders samples, and what to tell the user after (afterApply). A steps template is the doc for steps.draft (steps.apply over MCP); a tool template is the args of that tool; a setting template is a setting the user changes, not a workflow. A then call, when present, runs once the template is applied, with the ids of what it created.

Read the invoking user's working-hours schedule. Returns the work interval for a given date (today by default), the full workdays list (0=Sun … 6=Sat), and the user's timezone. When the user hasn't configured working hours the tool returns Mon–Fri 09:00–17:00 UTC with fallback: true — the agent should caveat its response accordingly.

Add a new attribute (field) to an existing sheet. Use during refinement (add a phone field). dataType MUST be a canonical Atwork name; for currency, pass dataType Number with description: "USD; whole numbers". Returns the new attributeId. For a Status/Select/Multi-Select field, pass the choices as options.items: [{title, color?, stage?}] — ids are generated server-side; on a Status field stage (Todo / InProgress / Complete) puts the choice in that stage, default Todo. Set isUnique: true on a field whose value identifies a row: item.create then dedupes on it. For a Relation to an existing sheet pass options.relatedSheetId (from workspace.structure) and twoWay: true to add the reverse field there too (default one-way). For a Code field (raw source with a language tag) pass options.language, one of: plain / html / json / typescript / javascript / sql / css / markdown. Computed fields name other fields, never ids: Formula takes options.formula with fields in braces ({Price} * {Quantity}); Mirror takes options.relation (a Relation field here) + options.field (on the related sheet); Rollup takes options.relation + options.function (COUNT / DISTINCT_COUNT / SUM / AVG / MIN / MAX) + options.field (a Number field there, not for COUNT); Rate takes options.stars; Pipeline takes options.stages; Summary takes options.template with fields in braces; Button takes options.workflow, the name of a manual-trigger workflow on this sheet. File List may take options.allowedFiles (any / images / documents / media / custom), options.allowedExtensions (with custom, e.g. ["pdf"]) and options.maxFiles (1–100). A name that does not exist is refused with the valid ones. Timer and DocX need nothing.

Compute one or more aggregations (COUNT, DISTINCT_COUNT, SUM, AVG, MIN, MAX, FIRST, LAST) over a sheet's rows, with optional filter and groupBy. Use for analytical questions like 'total revenue by stage', 'count of leads created this month', 'average response time per assignee'. Multiple functions in one call share the same column/filter/groupBy — pass ["SUM", "AVG"] together to get both for free. For date columns, group with timeBucket: 'month' (or 'quarter', etc.). Filter operators include the usual comparison ops plus date shortcuts (THIS_MONTH, BEFORE_TODAY, etc.) — see the schema. Filter values on Status, Select, Multi-Select, Pipeline, person, team, job and relation columns may be the names you see in sheet.read (e.g. 'Done'); grouped rows carry label = the name and labelId = the raw id. Read sheet.read once first to discover attribute codes; aggregate is the right tool when raw rows would exceed your context.

Turn a worksheet into a tasksheet in place: it gains Status, Assignee, Due Date and Priority, and its rows become tasks. Rows and fields stay.

Create a new sheet with optional initial attributes. intent: 'form' is for public-facing data-collection forms; intent: 'sheet' is for internal data tables. Pass the user's full proposed schema in attributes — this is the first-turn fat call. dataType values must be canonical Atwork names; if the user asks for currency, use Number with description: "USD; whole numbers". Every sheet gets a primary column that is a literal Title: do not add a separate name field in attributes; rename the Title to fit the sheet (Company, Task) with sheet.update_attribute. Returns the new sheetId. Call this exactly once per conversation; refinements use sheet.add_attribute / sheet.update_attribute / sheet.remove_attribute. Pass spaceId and folderId to say where the sheet goes — list them with workspace.structure. Without folderId the sheet goes in the space's root folder. (Panel-invoked calls may omit both; the invocation's placement is then used.) For a Status/Select/Multi-Select field, pass its choices as options.items: [{title, color?, stage?}]; on a Status field stage (Todo / InProgress / Complete) puts the choice in that stage, default Todo — give the done choices Complete. Set isUnique: true on a field whose value identifies a row (an external id, an email): item.create then dedupes on it.

Delete a sheet with its rows, views, forms, dashboards and workflows. This always asks the user first: say what goes before you call it. sheet.restore brings it back, except the files in its File List fields: those are deleted for good, and the approval card says so.

Read rows from a sheet the user has access to. Returns the sheet's title and up to limit row objects. ID-typed cells are pre-resolved to display names: single-value (Member, Team, Job, Status, Select, Pipeline, Actor, CreatedBy, ModifiedBy) become the resolved name; list-valued (Employee List, Team List, Job List, Multi-Select, Relation) become a comma-joined string. Original FK ids are preserved on each row under _ids[code] (string for single-valued, string[] for list-valued) when you need them for follow-up tools. Mirror and File List cells pass through as raw values. filters values on those columns may be the names you see (e.g. Status EQ 'Done', Assignee EQ 'Sara'); an unknown or ambiguous name is an error that lists the choices. Document and Description cells are returned IN FULL as markdown by default — headings, lists, links and code preserved — so you never need a second call to read a description. All other cells are clipped to 80 characters with a trailing '…'. Rows come in a stable order. Each call returns as many whole rows as fit (up to limit), with total (rows matching the filters), hasMore and nextOffset: to read every row, call again with offset = nextOffset until hasMore is false. To count rows that match a condition, pass filters and read total instead of paging. Use a tighter limit when you only need a sample. Archived rows are left out unless archived is shown or only; then each row carries Archived and ArchivedAt. Contact cells (email, phone, address, location; on the employee sheet also handle and bio) come back as null unless includeContactFields is true — set it only when the user explicitly asks for contact details. Password cells are always null. sort orders the rows by up to three fields (name or code, asc or desc); for latest, recent or newest questions sort by ModifiedAt desc (recently changed) or CreatedAt desc (recently added), for the oldest use asc. Without sort rows keep the sheet's board order. Empty cells come first in a descending sort, and a sort field edited between calls can shift rows across pages. fields returns only the named attributes plus id; documents = preview clips Document and Description cells to 80 characters and omit leaves them out — use either to scan many rows in one call, then read one row (e.g. filter Index EQ) for its documents in full.

Remove an attribute from a sheet. The server may reject removing the primary Title column (PRIMARY_TITLE_PROTECTED). Removed attributes go to a deleted-attributes pool and can be restored if needed; this is therefore mutating_reversible. The files of a File List field are the exception: they are deleted for good. Removing a File List field that holds files is refused with FILE_LIST_FILES_LOST, naming the field and how many rows hold files, and nothing is removed; tell the user and call again with confirmFileLoss: true only once they accept. In a chat the user accepts on a card instead: the call waits for it.