add-signature-request-approver
ChatGPTAdd an approver (approves a DRAFT before signers sign, NOT a signer), from scratch (first_name, last_name, email). Returns the created approver approver_id, status, recipient_stage_index, identity fields and custom_text. Ordering needs custom recipient order or approver reordering enabled, else it errors. One approver per call; chain via a returned approver_id as next insertAfterId. Drafts only. Adding from an existing user/contact/signer needs the Youtrust app. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature".
add-signature-request-follower
ChatGPTAdd ONE follower ("CC" recipient) to a signature request. Followers never sign: they track the request and receive its emails. On a draft they are notified once it is sent; on a sent request, immediately. Returns the created follower. One follower per call. A canceled or declined request, an email already following it, or an exceeded follower quota is rejected with an explicit message: surface it verbatim, do not retry. Followers cannot be edited: to change one's email or locale, call remove-signature-request-follower with its follower_id, then add the new one here. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature".
add-signature-request-signer
ChatGPTAdd ONE ad-hoc signer (from scratch: name + email, not linked to a contact or user) to an editable signature request (draft or paused only). No signature fields are placed for the new signer: the user MUST position their fields in the Youtrust app (request url) before sending. Returns the created signer and its attributes. Do NOT propose adding or editing documents or fields: those happen in the Youtrust app. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature".
create-signature-request
ChatGPTCreate a signature request DRAFT from scratch, WITHOUT a template. NEVER sends. USE THIS BY DEFAULT when the user named no template. The user then adds documents and recipients in the Youtrust app from the returned url: expected, not a limitation, never fall back to a template to avoid it. ALWAYS tell the user the workspace_name used and the custom_experience applied. Pass only the settings the user asked for; the others keep the organization defaults. Later changes: update-signature-request. Do NOT offer (Youtrust app only): cancelling, deleting or duplicating the draft. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature".
create-signature-request-from-template
ChatGPTCreate a signature request DRAFT from a template. NEVER sends. Returns its id, name, status, assigned placeholder_signers (slots filled by the caller), recurring_signers (signers fixed in the template, info only, not changeable via this tool), resolved read_only_text_fields (with current value or null), and a url to review/edit the draft in the Youtrust app before confirmation. Unknown placeholder or text-field labels are rejected with the list of valid labels, retry with a valid one. Once created, the only follow-up is send-signature-request. Do NOT propose editing the draft further: no adding/removing signers, no document/field changes outside readOnlyTextFields, no cancel/delete/duplicate — those must be done in the Youtrust app.When responding in a language other than English (FR, IT, DE, ES, PT, RO), read glossary://product-terms first and use its canonical translations verbatim. FR: "signature request" → "invitation à signer", NEVER "demande de signature".
get-signature-request
ChatGPTFull detail of ONE signature request by UUID: settings (status, delivery mode, recipient ordering, expiration, reminders, decline-to-sign, custom experience), workspace, sender, signers in signing order (status, signed_at) and approvers, each with custom_text and recipient_stage_index, followers, documents, labels, decline/rejection info and the app url. History: get-signature-request-activity-feed. Never returns signing, approval or follower links. Read-only. Do NOT offer (Youtrust app only): reminders, edit, cancel, archive, delete, duplicate, resend, extend, recipients, documents, fields. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature".
get-signature-request-activity-feed
ChatGPTRead the chronological activity feed (history) of one signature request: creation, sending, signatures, declines, cancellations, expirations, reminders, approver decisions, identity verifications, document renames. Events are sorted newest first; each has an event_type discriminating the shape of data. Requires the signature request UUID — if you only have a name/filter, call search-signature-requests first to resolve it. Read-only. After showing the history, do NOT propose, offer, or hint at unsupported actions: no sending reminders (even when reminder events appear in the feed), no editing/canceling/archiving/deleting/duplicating/resending/extending the request, no managing signers or fields. Those live only in the Youtrust app; if asked, tell the user to go there.When responding in a language other than English (FR, IT, DE, ES, PT, RO), read glossary://product-terms first and use its canonical translations verbatim. FR: "signature request" → "invitation à signer", NEVER "demande de signature".
get-signature-request-approver
ChatGPTFetch one approver (approves before signers sign, NOT a signer) of a signature request. Returns the approver approver_id, identity fields, status, approved_at, custom_text, and its recipient_stage_index in the flow. Use approver_id as insertAfterId for add-signature-request-approver or as approverId for remove-signature-request-approver. Approver groups (deferred identities) are NOT supported: their ids come back as not found; check the Youtrust app. Read-only. To edit an approver, use update-signature-request-approver; to send reminders, use the Youtrust app. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature".
get-signature-request-signer
ChatGPTFetch ONE signer of a signature request by its id: status, name, email, phone_number, locale, signature_level, authentication_mode, delivery_mode, custom_text, recipient_stage_index (1-based signing order) and signed_at (null until signed). Use it to read a signer's current values before update-signature-request-signer, or to check whether they were notified (status other than initiated). Read-only: modifies nothing, notifies no one. Signers only: approvers are read with get-signature-request-approver. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature".
list-custom-experiences
ChatGPTList the custom experiences (brandings) the user can apply to a signature request. Each result gives custom_experience_id (the customExperienceId to pass to create-signature-request or update-signature-request), name, and is_default (the one applied when customExperienceId is omitted). Paginated: the organization default first, then newest first. There is no search parameter: page through the list and match the name the user gave; if several match, ask. Do NOT offer (Youtrust app only): creating, editing or deleting a custom experience. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature".
remove-signature-request-approver
ChatGPTRemove an approver (approves before signers sign, NOT a signer) from a DRAFT signature request. get-signature-request-approver confirms an approver before removal. Drafts only: fails on a sent or scheduled request. Permanent: confirm with the user before calling. Approver groups (deferred identities) are not supported. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature".
remove-signature-request-follower
ChatGPTRemove ONE follower ("CC" recipient who never signs) from a signature request, identified by its follower_id. Works on drafts and on sent requests; a canceled request is rejected. The follower is not notified. Returns the signature_request_id and the removed follower_id. An unknown follower id or a rejected status comes back with an explicit message: surface it to the user, do not retry. Followers cannot be edited: to change one's email or locale, remove it here, then re-add it with add-signature-request-follower. Always remove first, an email that still follows the request cannot be re-added. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature".
remove-signature-request-signer
ChatGPTRemove ONE signer from an editable signature request (draft or paused only). IRREVERSIBLE: deletes the signer with their signature fields, document requests and consents; other signers and documents are untouched. ALWAYS ASK THE USER TO CONFIRM before calling it. Returns the ids of the request and of the deleted signer. On an ongoing or completed request, tell the user to do it in the Youtrust app. Approvers and followers: remove-signature-request-approver and remove-signature-request-follower. Do NOT offer (Youtrust app only): adding or editing documents or fields. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature".
search-signature-requests
ChatGPTList/search signature requests in the user's organisation. Use it to find requests by name/status/signer/date/etc., resolve UUIDs needed by other tools, or inspect last_reminder metadata. Filters are AND-ed; see the JSON schema for allowed criteria/operator/operands pairs. Read-only. Do NOT propose unsupported actions on the returned requests: no sending reminders, no editing/canceling/archiving/deleting/duplicating/resending/extending, no managing signers or fields. Those live only in the Youtrust app; if asked, tell the user to go there.When responding in a language other than English (FR, IT, DE, ES, PT, RO), read glossary://product-terms first and use its canonical translations verbatim. FR: "signature request" → "invitation à signer", NEVER "demande de signature".
search-templates
ChatGPTList/search templates in the user's organisation. Use to find a template before calling create-signature-request-from-template. For each result you get: id (the templateId to pass to create), status (active or draft — only active templates can be sent), placeholder_signers[].label (the placeholder_label values you map recipients to in create), and a direct link to the template in the app. Pass search for a partial-name match; results are paginated and sorted by creation date desc. Templates cannot be managed from here — do NOT propose creating, editing, deleting, duplicating, or sharing a template. The only template-related action available is create-signature-request-from-template. Any template management must be done from the Youtrust app.When responding in a language other than English (FR, IT, DE, ES, PT, RO), read glossary://product-terms first and use its canonical translations verbatim. FR: "signature request" → "invitation à signer", NEVER "demande de signature".
search-workspaces
ChatGPTList/search workspaces accessible to the user. Use this when create-signature-request-from-template reports that the template is not bound to a workspace: pick a workspace here and pass its workspace_id as the workspaceId argument. For each result you get: workspace_id (the workspaceId to pass to create-signature-request or create-signature-request-from-template), name, and is_default. Results are paginated and sorted by name asc. Workspaces cannot be managed from here: do NOT propose creating, renaming, or deleting a workspace; that must be done in the Youtrust app. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature".
send-signature-request
ChatGPTSend an existing draft to its recipients. DESTRUCTIVE and NOT idempotent — triggers real emails; the request becomes non-editable. Workflow: create-signature-request-from-template returns the draft url; show it to the user, wait for EXPLICIT confirmation (see "Confirmation" in global instructions — words like "ok"/"looks good" do NOT count), then call this tool. Never call on the same turn the draft was just created. Trial subscriptions are rate-limited — on a rate-limit error, surface the message verbatim and stop, do not retry. After sending, do NOT propose, offer, or hint at cancelling, editing, resending, extending, sending reminders, or otherwise modifying the request. Those must be done from the Youtrust app.When responding in a language other than English (FR, IT, DE, ES, PT, RO), read glossary://product-terms first and use its canonical translations verbatim. FR: "signature request" → "invitation à signer", NEVER "demande de signature".
send_feedback
ChatGPTRecords that the user asked for something these tools cannot do, so the developers of this server can add it. It changes no data and contacts no one. Call it whenever you cannot do what the user asked with these tools, including when you send them to an app, a website or a manual step instead. Then answer them as usual.
update-signature-request
ChatGPTUpdate the settings of a signature request: name, delivery mode, workspace, recipient ordering, email sender and custom text, automatic reminders, decline-to-sign, custom experience, expiration date. Pass ONLY the settings the user asked to change: omitted ones are untouched, null only removes customExperienceId. Allowed settings depend on the status: a refused call changes nothing and names the offending settings. On an ongoing or approval request, a new expiration date emails the pending recipients: ask the user to confirm first. Never touches documents, fields or recipients, and never sends. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature".
update-signature-request-approver
ChatGPTUpdate ONE existing approver (approves before signers sign, NOT a signer) of a DRAFT signature request: name, email, phone number, locale, custom email texts, or position in the approval order. PARTIAL UPDATE: only the parameters you pass change. Get the ids via search-signature-requests (approvers[].approver_id); returns the updated approver, same shape as get-signature-request-approver. Drafts only: fails once sent or scheduled. Approver groups (deferred identities) are not supported. Do NOT offer (Youtrust app only): editing documents, fields, or an approver created from a user/contact. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature".
update-signature-request-signer
ChatGPTUpdate ONE existing signer of a signature request: name, email, phone number, locale, signature level and authentication mode, delivery mode, custom email texts, or position in the signing order. PARTIAL UPDATE: only the parameters you pass change; fields already placed for this signer are kept. On an ongoing request, changing the name, email or phone number of an already notified signer sends them a new signing email: ASK THE USER TO CONFIRM first. Returns the updated signer. Do NOT offer (Youtrust app only): adding or editing documents or fields. Non-English: use glossary://product-terms verbatim; FR: "invitation à signer", never "demande de signature".
