cancel_signature_request
ChatGPTCancel a draft or pending signature request; signers can no longer sign it. Also used to replace a draft that needs changes. confirm: true records that the user confirmed the cancellation. A completed request can't be cancelled.
change_member_role
ChatGPTMake a workspace member an admin, or an admin a member again. Identify the person by the email list_team shows. Admins can invite and remove people and change the workspace's settings, so confirm the change with the user first. Only owners and admins can do this; the owner's role can't be changed, and only the owner can turn an admin back into a member. Tell the user what changed.
claim_anonymous_document
ChatGPTMove a document that was published without an account (a 24-hour link) into the user's workspace so it stays. Needs its claim link (…/claim/<token>) or token.
create_project
ChatGPTCreate a project in a workspace. Check list_projects first and reuse a matching project instead of creating a near-duplicate ("Acme" rather than a new "Acme Corp"). In organise mode "ask", get the user's OK first.
create_signature_draft
ChatGPTCreate a draft signature request with DocuSeal. Nothing is emailed yet. Returns a summary of the draft (document and version, signers in signing order with name, email and role, subject, message, expiry, filing folder and any warnings) and a link to the exact PDF the signers will receive. Signer names and emails are used exactly as given, from the user or from the document's signature block. When the document has a signature block, each role in it needs exactly one signer with a matching role. Without one, a signature box per signer is added at the end of the document. Sending is a separate step: send_signature_request. Needs DocuSeal connected in the workspace (get_account shows it).
create_workspace
ChatGPTCreate a new workspace, with the user as owner. Most people need only one workspace and should use projects to organise documents; create one only when the user asks for a separate workspace (another company or team). Confirm the name with the user first. The slug is the workspace's part of every document link; leave it out to derive it from the name. The user's plan can limit how many workspaces they own. This doesn't change where new documents go; use set_defaults if the user wants that.
delete_document
ChatGPTPermanently delete a document with every version. This can't be undone; unpublish_document takes a document offline and keeps it. confirm: true records that the user asked for permanent deletion.
delete_project
ChatGPTDelete a project. Only empty projects can be deleted; move or delete its documents first. confirm: true records that the user confirmed the deletion.
edit_document
ChatGPTMake targeted changes to a document without resending all of it: each edit replaces exact text (find) with new text (replace). find must match the current Markdown exactly, including punctuation and line breaks, and appear once unless replace_all is true; include enough surrounding words to make it unique. All edits apply together as one new version. Read the document with get_document first.
export_document
ChatGPTTurn one or more documents (up to 10) into PDF or Word files with the workspace's branding, and get a download link for each. Links work for an hour; give them to the user as links, one per line. Word (docx) isn't available in every workspace; if it's refused, offer PDF instead. Depending on the workspace, PDFs can carry a small "Made with OpenDocs" footer.
file_signed_documents
ChatGPTSave a completed signature request's signed PDF and audit log (signing certificate) in one of the workspace's Google Drive folders. Only when the user asks, and only once everyone has signed. Use a folder name exactly as get_account lists it; never guess one. (Requests created with file_to are filed automatically.) Give the user each Drive link on its own line.
get_account
ChatGPTWho the user is in OpenDocs: their workspaces (with role), the plan and document quota of the default workspace, where new documents go by default (workspace, project, organise mode), pending invitations, connected integrations (Google Drive folder names, e-signature) and what this app is allowed to do. Call it once at the start of a conversation about documents, and whenever you need a workspace or Drive folder name.
get_document
ChatGPTOpen a document: its title, link, project, who can open it, who it's shared with, current version number, and its Markdown (or an older version's). Long documents come back in pages; pass offset to read further. Use the version number as base_version when you change it.
get_document_history
ChatGPTEvery published version of a document, newest first, with when and from which app it was published. Read an old version with get_document (version), or bring it back with restore_document_version.
get_export_theme
ChatGPTThe look of the workspace's PDF and Word exports: brand colour, font, preset, logo and footer, whether the user may change them, plus the curated presets (with what each suits), the available fonts and the contrast rules. Call it before proposing a theme change with update_export_theme.
get_signature_request
ChatGPTWhere a signature request stands: its status, each signer's status (not sent, email sent, opened, signed, declined) and the details read back before sending. Once everyone has signed, it includes download links for the signed PDF and the audit log (signing certificate); for a draft, a link to the PDF that will be sent. Check only when the user asks; don't poll.
invite_people
ChatGPTInvite people to a workspace by email. Each person gets an invitation email and is only added once they accept it. This sends email, so first confirm the exact addresses and the role with the user (member by default; admin only if they asked). Afterwards tell them each person has to accept the email. The workspace's plan can limit how many members it holds, pending invitations included. The result lists who was invited and why any address failed.
leave_workspace
ChatGPTLeave a workspace the user belongs to. They lose access to its documents, and getting back in needs a new invitation (or the email-domain auto-join). Owners can't leave their own workspace. confirm: true records that the user confirmed leaving this workspace.
list_documents
ChatGPTList the user's documents, newest first, or search them by words in the title or summary (query). By default it covers every project in the default workspace; pass project to narrow it, or workspace to look elsewhere. Returns each document's title, link, project, who can open it and its ID.
list_projects
ChatGPTThe projects in a workspace with how many documents each has and their recent titles. Projects group related documents, like folders or git branches: one per client, matter, product or topic. Call it before publishing to pick the right project.
list_signature_requests
ChatGPTThe workspace's signature requests, newest first (up to 50), with status and how many have signed. Filter by document or by status (draft, pending, completed, declined, expired, cancelled, failed). Use get_signature_request for one request's details.
list_team
ChatGPTWho is in a workspace: members with their name, email and role, plus pending invitations and auto-join email domains. Pending invitations are only visible to owners and admins. Use it before changing roles, resending or revoking invitations, or removing someone, so you use their exact email.
move_document
ChatGPTMove a document to another project in the same workspace (by project name, slug or ID; a new name creates the project). Its link changes and the old link stops working, so tell the user before moving and update documents that link to it afterwards.
publish_document
ChatGPTPublish Markdown as a new OpenDocs document and get its link. The first heading becomes the title unless you pass one. Visibility defaults to workspace (only workspace members). Public visibility also needs confirm_public: true, which records that the user chose to make it public; to reach specific people, publish it and use share_document instead. project picks where it goes (by name, slug or ID; a new name creates the project, so check list_projects first and follow the organise mode). To change an existing document use update_document or edit_document, not this. A document that will be signed marks where people sign with a ```signature block (see the server instructions), not hand-drawn Signature/Name/Date lines.
publish_documents
ChatGPTPublish up to 25 related documents in one call (one call, never a loop of publish_document). They share a project, visibility and tags; give the batch a tag so it can be found again. Some documents can fail while others succeed; the result lists each one.
remove_team_member
ChatGPTRemove a member from a workspace. They lose access to its workspace-only documents right away; documents they published stay. confirm: true records that the user confirmed removing this person. The owner can't be removed, and only the owner can remove an admin. To cancel an invitation that wasn't accepted yet, use revoke_invitation instead.
rename_project
ChatGPTRename a project, and optionally change its slug. Changing the slug changes the links of every document in it, so only do that when the user asks.
resend_invitation
ChatGPTEmail a pending workspace invitation to the person again, for example when they can't find it. Identify the invitation by the email list_team shows. This sends email, so check with the user first. Only owners and admins can do this. The person still has to accept it.
respond_to_invitation
ChatGPTAccept an invitation to a workspace, join a workspace that's open to the user's email domain, or decline an invitation. get_account lists both under "Waiting for the user". Only call it after the user said yes (or no) to that specific workspace. Joining doesn't change where new documents go; offer set_defaults if they want to work in the new workspace.
restore_document_version
ChatGPTBring back an older version of a document by publishing its content as a new version at the same link. Nothing is lost: the version being replaced stays in the history, so this can be undone. Find version numbers with get_document_history.
revoke_invitation
ChatGPTCancel a workspace invitation that wasn't accepted yet: the link in the person's email stops working. Identify the invitation by the email list_team shows. Confirm with the user first; to undo it, invite the person again with invite_people. Only owners and admins can do this. To remove someone who already joined, use remove_team_member.
save_to_drive
ChatGPTSave a document as a PDF (default), Word or Markdown file in one of the workspace's Google Drive folders. Only when the user asks to save or file it in Drive; publishing or exporting never implies it. Use a folder name exactly as get_account lists it and never guess one: if the user's words don't clearly match one name, ask. Give the user the Drive link on its own line. Needs Google Drive connected in the workspace (get_account shows it).
send_signature_request
ChatGPTSend a draft signature request (made with create_signature_draft): DocuSeal emails each signer a link to sign, in the draft's order. This sends real email to the people in the draft and can't be unsent; a pending request can still be cancelled with cancel_signature_request. confirm: true records that the user approved sending the draft as summarised. If the workspace requires approving sends in the browser, it returns an approval link for the user instead.
set_auto_join_domains
ChatGPTLet anyone who signs in with a verified email at the company's domain join a workspace as a member without an invitation (add), or stop that (remove). An admin can only add their own email's domain (an admin at jane@acme.com can add acme.com), never personal providers like gmail.com or outlook.com. Explain this to the user and get their OK before adding a domain, since everyone at that domain can then join.
set_defaults
ChatGPTChange where new documents go for this connection: the default workspace, the default project (or null to use the workspace's Default project) and the organise mode (ask: ask before creating projects for new topics; auto: create them and say so; off: always use the default project). Use it when the user says something like "from now on put things in the Legal project" or "use the Acme workspace". Workspaces and projects can be given by name, slug or ID.
set_document_visibility
ChatGPTChange a document's visibility: private (only the user), workspace (workspace members) or public (anyone with the link). Public also needs confirm_public: true, which records that the user chose to make it open to anyone with the link. If people outside the workspace still can't open a public document, a workspace owner has to turn on "Allow public documents" in workspace settings. To give specific people access, use share_document instead.
share_document
ChatGPTGive specific people outside the workspace access to one document, or take it away. People can be email addresses or whole email domains ("@acme.com"). They sign in with that email to read it and don't join the workspace. By default each new person gets an email with the link (notify: false to skip). With neither add nor remove, it lists who has access. Confirm the exact addresses with the user before adding.
unpublish_document
ChatGPTTake a document offline: its link stops working but the content, history and link are kept, and it no longer counts toward the workspace's document limit. Prefer this over delete_document when the user says "remove" or "take down". Check with the user first.
update_document
ChatGPTReplace a document's Markdown, title or tags, creating a new version at the same link (older versions are kept). For a few small changes, edit_document is cheaper. Pass base_version (the version you read with get_document): if someone published a newer version since, this fails instead of overwriting their work; show the user and retry with force: true only if they want their version to win. Changing visibility is done with set_document_visibility.
update_export_theme
ChatGPTChange the brand colour, font, preset, logo or footer used in every PDF and Word export in the workspace. It changes every export in the workspace; confirm: true records that the user agreed to the change. Prefer a preset; a custom colour must be dark, at least 4.5:1 against white (use a navy rather than a bright blue). The logo is set from an image URL (logo_url, or null to remove it) and only appears in exports with logo_in_exports: true. Colour, font, presets and logo work in every workspace; the footer only where get_export_theme says it can be changed. Owners and admins only. Afterwards offer to export one document with export_document as a preview.
upload_image
ChatGPTStore an image in OpenDocs and get a permanent link to put in a document as . Pass the image as base64 (data_base64), or as a file the user attached in ChatGPT (file). Images that already have a public https link don't need this: put the link straight into the Markdown and OpenDocs copies it when you publish. PNG, JPEG, WebP, GIF or SVG, up to 10 MB.
