BasicOps

Add a file to a project's files, the ones on its Files tab. Pass the project ID as 'projectId' and the file as 'attachment'. 'attachment' is either the attachmentId of a new upload, which can be used once, or the id of a file already in the workspace - a file someone attached to a chat message, or one on another task. A file already in the workspace is copied, so the original stays where it is. The file is not read, so its size and kind do not matter.

add_file_to_project

Add a file to a task's files. Pass the task ID as 'taskId' and the file as 'attachment'. 'attachment' is either the attachmentId of a new upload, which can be used once, or the id of a file already in the workspace - a file someone attached to a chat message, or one on another task. A file already in the workspace is copied, so the original stays where it is. The file is not read, so its size and kind do not matter.

add_file_to_task

Create or update note in bulk. If the item ID is present, the item will be updated, otherwise a new item will be created. The whole batch is validated before anything is written, so a response that is a bare "Error: ..." string means the call failed as a unit and nothing was created or updated: fix the offending item and send the batch again. Once the write begins the response is a list of results, positional, the nth result being what became of the nth item, and a row that failed there comes back as {"index", "error"} in its own slot while the others still land. Read them: that kind of call can partly succeed, and the rows that failed are the ones to report or redo. Write the content in Markdown — it is converted to HTML on save, so a task named in a note can be written as '[Title](url)' with the 'url' from a tool response and will link to that task. That is the only form that links: the '#' reference is inserted by a picker in the editor and is stored as literal text when written through this tool.

bulk_create_or_update_note

Create or update project in bulk. If the item ID is present, the item will be updated, otherwise a new item will be created. The whole batch is validated before anything is written, so a response that is a bare "Error: ..." string means the call failed as a unit and nothing was created or updated: fix the offending item and send the batch again. Once the write begins the response is a list of results, positional, the nth result being what became of the nth item, and a row that failed there comes back as {"index", "error"} in its own slot while the others still land. Read them: that kind of call can partly succeed, and the rows that failed are the ones to report or redo.

bulk_create_or_update_project

Create or update section in bulk. If the item ID is present, the item will be updated, otherwise a new item will be created. The whole batch is validated before anything is written, so a response that is a bare "Error: ..." string means the call failed as a unit and nothing was created or updated: fix the offending item and send the batch again. Once the write begins the response is a list of results, positional, the nth result being what became of the nth item, and a row that failed there comes back as {"index", "error"} in its own slot while the others still land. Read them: that kind of call can partly succeed, and the rows that failed are the ones to report or redo.

bulk_create_or_update_section

Create or update task in bulk. If the item ID is present, the item will be updated, otherwise a new item will be created. The whole batch is validated before anything is written, so a response that is a bare "Error: ..." string means the call failed as a unit and nothing was created or updated: fix the offending item and send the batch again. Once the write begins the response is a list of results, positional, the nth result being what became of the nth item, and a row that failed there comes back as {"index", "error"} in its own slot while the others still land. Read them: that kind of call can partly succeed, and the rows that failed are the ones to report or redo.

bulk_create_or_update_task

Create or update template in bulk. If the item ID is present, the item will be updated, otherwise a new item will be created. The whole batch is validated before anything is written, so a response that is a bare "Error: ..." string means the call failed as a unit and nothing was created or updated: fix the offending item and send the batch again. Once the write begins the response is a list of results, positional, the nth result being what became of the nth item, and a row that failed there comes back as {"index", "error"} in its own slot while the others still land. Read them: that kind of call can partly succeed, and the rows that failed are the ones to report or redo.

bulk_create_or_update_template

Add a channel

create_channel

Add a direct chat with a user

create_chat

Add a group chat

create_groupchat