Apps

POST /v1/tools/tape/listApps

List all accessible Tape apps, optionally filtered by workspace. Returns app_id, name, and workspace_id for each app. Use workspace_id to scope results to a single workspace. Use summary_only for the most compact response (just app_id, workspace_id, name). Call tape_getApp with a specific app_id to get full field definitions.

Parameters

Flags

POST /v1/tools/tape/getApp

Get a Tape app schema including field IDs, field types, category option IDs, and relation targets. IMPORTANT: Always call this before creating or updating records — you need field_id values, field_types, and category option_ids from the response to construct valid field values. Use field_id or field_label to look up a single specific field without fetching the whole app. Prefer minimal output: use include_fields: false for app metadata only, or field_type_filter: "basic" to exclude read-only calculation fields. Key response fields per field: field_id (number — use as key in createRecord/updateRecord), external_id (string — alternative key), field_type (determines value format), config.settings.options (category/status option_ids with text), config.settings.referenced_apps (linked app_ids for relation fields).

Parameters

Flags

POST /v1/tools/tape/getField

Get a single field definition from a Tape app by label, field_id, or external_id. Returns the full field config including settings (category options, relation targets, calculation script, etc.). If the field is not found, returns a list of all available fields in the app to help identify the correct one. More efficient than getApp when you only need one field. Provide app_id plus one identifier (label, field_id, or external_id).

Parameters

POST /v1/tools/tape/createApp

Create a new Tape app in a workspace with optional fields. Returns the created app with app_id and all fields (including generated field_ids). Calculation fields are automatically separated and added after app creation (they need field_ids to reference). Field config format: {field_type: "single_text", config: {label: "Name", settings: {}}, external_id: "name"}. Common field types: single_text, multi_text, number (settings: decimals, unit, unit_location), single_date (settings: time "disabled"/"enabled"/"required"), single_category/multi_category (settings: {options: [{text, color}]}), status (settings: {options: [{text, color, means_completed}]}), single_relation/multi_relation (settings: {referenced_apps: [{app_id}]}), single_user/multi_user, multi_email, multi_phone, multi_link, checklist, single_attachment/multi_attachment, single_location, calculation (settings: {script, return_type, decimals, unit, unit_location}). For calculation fields with script validation, prefer tape_calculationField — it validates scripts before sending to the API.

Parameters

POST /v1/tools/tape/createFields

Add one or more new fields to an existing Tape app. Additive-only: never updates or removes existing fields — use updateFields for that. Each field requires field_type and config.label; settings depend on the type. For calculation fields, config.settings may include trigger_webhooks and trigger_automations (booleans) to control whether recalculations fire the app's webhooks/automations; omit them to inherit Tape's default. Returns a summary (field count added + server response).

Parameters

POST /v1/tools/tape/updateApp

Update Tape app-level properties (name, item_name, description, icon, item_icon). For field changes use createFields, updateFields, updateAppFieldOrder, or calculationField.

Parameters

POST /v1/tools/tape/updateFields

Safely update fields on a Tape app. Validates every proposed change against the current app state and applies only the safe ones — unsafe operations are reported in the "skipped" bucket with explanations and alternatives. Does NOT accept settings.options directly for category or status fields; use option_ops instead — removal of options is intentionally not available because it causes irreversible data loss. Each option_ops entry is a SINGLE op object. Shapes: {op:"add", options:[{text:"5", color?:"DCEBD8"}, ...]} to add one or more new options; {op:"rename", option_id:123, text:"New name"} to rename one option; {op:"recolor", option_id:123, color:"E8F0F8"} to recolor one option; {op:"reorder", option_ids:[3,1,2]} to reorder by id. Do NOT put `text` at the op level for "add" — text belongs inside each options[] entry. Do NOT pass the full options list (that would be settings.options, which is refused). Does NOT accept settings.* changes on date fields (stored values depend on settings). For calculation fields, prefer the dedicated calculationField tool; you may also set trigger_webhooks / trigger_automations (booleans) in a calculation field's config.settings to control whether recalculations fire the app's webhooks/automations. PREREQUISITE: call getApp first to collect field_ids and current option IDs.

Parameters

POST /v1/tools/tape/updateAppFieldOrder

Reorder fields in a Tape app. Pass ALL field_ids in the desired display order — every field must be included. PREREQUISITE: Call tape_getApp first to get all current field_ids. The order determines how fields appear in the app UI and record forms.

Parameters

Flags

POST /v1/tools/tape/calculationField

Create or update a Tape calculation field with script validation. Tape calculations use JavaScript with globally available libraries (NO import/require needed): - _ (lodash): _.sum(), _.groupBy(), _.uniq(), _.flatten(), etc. - moment: moment(date).format("DD/MM/YYYY"), .add(), .subtract(), .diff() - dateFns: format(), parseISO(), differenceInDays(), etc. - dateFnsTz: formatInTimeZone(), utcToZonedTime(), etc. - uuid: uuid.v4() - striptags: striptags(html) - jsonata: jsonata(expression).evaluate(data) FIELD REFERENCE SYNTAX — @[Label](variable): Same-app: @[Field Label](field_NUMBER) e.g. @[Status](field_702438) Metadata: @[Record ID](meta_recordId) e.g. @[Record ID](meta_recordId) @[App ID](meta_appId) Related-app: @[All of Label](DIRECTION_TARGETFIELDID_RELFIELDID) DIRECTION: in (incoming, drops nulls), out (outgoing, drops nulls), inn (incoming with nulls), outn (outgoing with nulls) ALWAYS use inn_/outn_ (with nulls) when pulling multiple parallel arrays — without nulls, missing values cause arrays to shrink and indexes misalign. TARGETFIELDID: the field_id of the field you want to READ in the RELATED app RELFIELDID: the field_id of the relationship field in THIS app HOW TO FIND THE RIGHT IDs: 1. Call getApp on THIS app — find the relationship field (single_relation/multi_relation) → its field_id is the RELFIELDID (last number) 2. Call getApp on the RELATED app — find each field you want to read → their field_ids are the TARGETFIELDIDs (first number) The variable MUST be: field_N, meta_recordId, meta_appId, in_N_N, out_N_N, inn_N_N, or outn_N_N. NO words like "contacts" or "my_field". UNSUPPORTED IN CALC CONTEXT (will error): - import/require — libraries are global, no importing needed - async/await — calculations must be synchronous - return statements at top level — the final expression is returned implicitly; helper functions CAN use return internally SUPPORTED (unlike Podio, Tape supports modern JS): - .map(), .filter(), .reduce(), .forEach(), .find(), .some(), .every() - for...of loops, arrow functions, template literals, destructuring, spread - lodash, moment, date-fns, jsonata (all global) FIELD TYPES THAT CANNOT BE REFERENCED: multi_image, multi_attachment, single_attachment, created_by, last_modified_by, created_on, last_modified_on, single_relation, multi_relation COMMON MISTAKE: Do not try to reference single_relation or multi_relation fields directly with @[Label](field_N) syntax. Instead, use the cross-app reference syntax: @[All of TargetField](in_TARGETFIELDID_RELFIELDID) to pull values from related records through the relation. RETURN TYPES: "number" (set decimals 0-4, optional unit with prefix/suffix) or "text" (supports markdown/HTML) WEBHOOK & AUTOMATION TRIGGERS (optional booleans in settings): - trigger_webhooks: when this field recalculates, fire the app's webhooks. - trigger_automations: when this field recalculates, fire the app's automations. Both inherit Tape's default (currently on) when omitted on create, and are preserved when omitted on update. Set either to false to stop this field's recalculations from firing that channel. PATTERNS: Simple math: @[Qty](field_1) * @[Price](field_2) Conditional: const t = @[Type](field_1); t === "A" ? @[Amount](field_2) : 0 Count related: @[All of Title](inn_fieldId_relId).length Lodash sum: _.sum(@[All of Hours](in_fieldId_relId)) Date format: moment(@[Date](field_1)).format("YYYY/MM/DD") Markdown table: const names = @[All of Name](inn_F1_R); const emails = @[All of Email](inn_F2_R); names.map((n, i) => `${n || ""} | ${emails[i] || ""}`).join("\n") UUID generation: uuid.v4() Record ID: @[Record ID](meta_recordId) HEADING / DIVIDER / SECTION LABEL (common pattern): Tape requires at least one field reference even for static/decorative content. Use a dummy reference that won't affect display: var dummy = @[Status](field_123); '<a href="#"><img src="https://dummyimage.com/690x40/40188e/edf0bd.png&text=SECTION+TITLE"></a>' Or simpler HTML: var dummy = @[Record ID](meta_recordId); '<div style="border-top:2px solid #40188e;padding:8px 0;font-weight:bold;font-size:14px;color:#40188e">SECTION TITLE</div>' The dummy variable absorbs the required field reference. The final expression (the HTML string) is what gets displayed. IMPORTANT: The script MUST contain at least one @[Label](field_N) or @[...](meta_recordId) reference or the API will reject it.

Parameters

POST /v1/tools/tape/cloneApp

Create an exact duplicate of a Tape app with all fields, settings, and field order preserved. Calculation fields are excluded (they must be re-added manually with tape_calculationField after cloning because they reference field_ids that change). Relationship/relation fields are copied as-is — if cloning to a different workspace, you may need to update their referenced_apps. Returns the new app_id and a summary of cloned vs skipped fields.

Parameters

POST /v1/tools/tape/deleteApp

Permanently delete a Tape app and ALL its records. This action CANNOT be undone. Use tape_getApp first to verify you have the correct app. Consider the impact on relation fields in other apps that reference this app.

Parameters

POST /v1/tools/tape/deleteFields

Delete one or more fields from a Tape app. DESTRUCTIVE — every value stored in the deleted fields across every record is lost irreversibly. REST API only; not exposed to the agent or MCP.

Parameters