well_create_project_folder

io.github.WellApp-ai/well-mcp · Verify this server

Gather a client project's files into one Google Drive folder. The person confirms on a card first. The folder is "<client> · <project>", inside Well's own Google Drive folder. A folder with that exact name is reused, so a project has one folder. Each item is placed once: - a Drive file goes in as a shortcut to the original (the original is not copied). When Google Drive refuses the shortcut, Well copies the file instead (outcome "copied"). - a mail attachment is uploaded. Then Well writes one note on the client company with the folder link, the files placed and `requested_files`; a repeated call writes no second note. Well reads and places only the asking person's own Drive and mail connections, never a teammate's. Call well_list_project_files first, tell the person which files you chose, and call this tool only after the person agrees. Pass the chosen `items` exactly as it returned them (with each Drive file's `name`). The card lists each file by the `name` you pass, so never change it: a Drive file whose current name in Drive differs from the `name` you pass is not placed (outcome "name_mismatch"). Each returned item has the Drive name of the file as `name`: use that name when you tell the person what was placed. Pass `requested_files` for the files you will ask the client for. Returns `outcome` ("prepared", or a refusal: "company_not_found", "not_connected", "connection_choice_needed" with `connection_ids`, "needs_reconnect", "no_root_folder", "failed"; "not_connected" and "needs_reconnect" name the Google Drive export connection, which the chat connect card does not connect), `folder` (`id`, `name`, `web_view_link`, `status` "created" or "reused"), `items` (each with its `outcome`: "shortcut_added", "copied", "uploaded", "already_present", "not_found", "name_mismatch", "not_copyable", "too_large", "drive_read_not_connected" (the asking person's own Drive reading connection is missing or needs a reconnect: the item carries a `message`, and the chat connect card connects Google Drive for reading, so offer it, never the export connections), "mail_not_connected", "ambiguous_attachment" (the mail holds several attachments with that file name: pass `size` as returned), "connection_not_yours" (the item names a Drive or mail connection that another person connected: Well reads only the asking person's own, so nothing was read or placed; drop the item) or "failed") and `note` (`status` "created", "existing", "limit_reached" when the plan's record limit refused the note, so none was written while the folder stands, or "failed"). Report only the items whose outcome places them in the folder as placed, and name the others with their reason. To share the folder, call well_create_drive_folder_share with `folder.id` and `folder.name`. When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass `workspace_id` on the call.