Send your first document for signature
Five minutes, six prompts. You talk to your agent; it drives GetSign on your monday.com board and reports back at every step. Nothing here needs the GetSign interface.
Your first signing workflow
“Send the contract for item 987654321 after I approve the plan.”
- 1Prepare the document
Choose the workflow, template and signer fields.
- 2Review and send
Check the details and approve the request.
- 3Track the result
Follow progress and retrieve the signed PDF.
What you need
Three things, all of which you probably already have.
A connected client
Claude Code, ChatGPT, Claude Desktop, Cursor, Codex, VS Code or any MCP client, with GetSign added and monday access approved.
A monday board
Any board with the items you want signed. You will need its board ID: it is in the board URL.
A signer column on that board
An Email, People or mirrored-email column holding the person who signs. Signers come from board columns, so this is the one thing worth checking first.
Why a column and not an email address? GetSign resolves signers from your board so the signature stays tied to the item. You can copy extra people on the email, but a copy recipient is not a signer. If the board has no suitable column yet, add one and put the signer’s address in it.
The conversation, step by step
Copy each prompt, replacing the board and item IDs with yours. Your agent will tell you what it is about to do before it changes anything.
Check the connection
Run a GetSign preflight check.
Confirms GetSign is installed on your monday account and that your agent is authorized. If it is not, this is the step that hands you the login link: worth running once rather than debugging a failed send later.
Choose or create a workflow
Show me the GetSign workflows on board 123456789.
A workflow is the signing setup that lives on a board: who signs, what gets sent, which reminders go out. One board can have several.
If the board already has one, your agent will list them and ask which to use, or whether to create a new one. If the board has none, it creates one. It will also offer to add a GetSign tab to the board so you can see signing status there.
A fresh workflow is complete and usable with every optional feature switched off. Your agent will ask where documents should come from: a reusable template, or a file column on the board: and which optional features you want. “Decide later” is a fine answer to the second question.
Put a document on it
Three ways in, depending on where the document already lives:
Uploading from disk needs a client that can read your files: Claude Code, Cursor, Codex or VS Code. From ChatGPT, use the gallery or the board’s File column.
Attach our NDA template from the GetSign gallery to that workflow.
Upload ~/contracts/mutual-nda.pdf as a GetSign template and attach it to that workflow.
Use the PDF already in the Contract column on item 987654321 as the signing document.
Map the signature fields
Detect the signature fields on that document and assign the signer from the board's Email column.
GetSign’s AI reads the document and finds the signature pads, initials, date fields, text boxes and checkboxes. Your agent then saves them and points each one at the board column that names the signer.
You will get a link to review the result in the PDF editor before anything goes out. Two things worth knowing:
- Detection alone saves nothing. The fields are not persisted until the save step: your agent handles this, but it is why you should let it finish rather than stopping at the preview.
- Edits default to the template. Changing fields on a shared template changes them for every item using it. Say so explicitly if you want the change to affect this one item only.
Want board values in the document itself: the client’s name, the amount? Ask for them in the same prompt: “detect the signature fields and the board fields.” GetSign then fills those boxes from the item’s columns. In a DOCX template you can use {columnId} merge tokens instead. Text already printed in a PDF, such as a typed {{Client Name}}, is not replaced.
Send it
Send the GetSign signature request for item 987654321 with the message "Please review and sign this agreement."
Your agent shows you a summary: document, signer, message: and asks you to confirm. Nothing is emailed until you do. Sending is the one genuinely per-item step: everything before it can be set up for the board as a whole.
This sends a real email. Point the first run at your own address, or at a test item, before you point it at a customer.
Track it, then collect the signed copy
Who still needs to sign on board 123456789?
Summarize the signing history for item 987654321, give me the audit trail, and link the signed PDF.
You get the full audit trail: who opened it, when, from where, and when each party signed: alongside a download link for the sealed PDF. Same trail as a signature started from the board, because it is the same signing engine.
Once the first one works
Everything else is a variation on those six prompts.
Two signers, in order
“CISO signs first, then the CFO.” Signing order is set from chat: you never have to open the PDF editor for it.
The whole board at once
Ask which items are still unsigned, then work through them. Status, reminders and cancellation are all single prompts.
Automatic write-back
Have the signed PDF land in a board File column, and the item’s status move on completion: configured once on the workflow.
Questions at this stage
No. Sending a signature request asks for confirmation before the email goes out, and so do the other destructive actions: cancelling a request, resetting a signing process, deleting a document. Your MCP client also asks before each tool call unless you have allowlisted it. We recommend leaving both on.
No. GetSign MCP prepares and sends documents; the signature itself is always made by the signer, in their own browser session, against their own email. An agent can start a sign-by-me flow for you, but it cannot produce anybody else’s signature.
Signers come from existing monday columns: an Email, People or mirrored email column. If nobody has added a suitable column yet, your agent will tell you which one to create. Extra addresses can be copied on the email, but a copy recipient is not a signer.
Ask it to refine the detection with a hint: “the signature block is at the bottom of page 3”: or to start over. You can also open the PDF editor from the link it gives you and place the fields by hand. Nothing is sent until you confirm.
Yes. MCP is a new way to drive the same GetSign signing engine: signatures keep the same audit trail, tamper-evident sealing, and ESIGN/UETA/eIDAS compliance as signatures started from a monday board.
Continue with GetSign MCP
Choose the next MCP guide based on what you are trying to finish now. You can connect another AI client, send a first document for signature, review every available MCP tool, or return to the overview before sharing the setup with your team.
Connect Claude Code, ChatGPT, Claude Desktop, Cursor, Codex, VS Code, or another MCP-compatible client. The setup path explains where the server URL goes and what to check before the first signing request.
MCP guideClaude CodeConnect Claude Code, ChatGPT, Claude Desktop, Cursor, Codex, VS Code, or another MCP-compatible client. The setup path explains where the server URL goes and what to check before the first signing request.
MCP guideChatGPTConnect Claude Code, ChatGPT, Claude Desktop, Cursor, Codex, VS Code, or another MCP-compatible client. The setup path explains where the server URL goes and what to check before the first signing request.
MCP guideTool referenceUse the tool and recipe reference when you need the exact actions behind a workflow. It explains what the MCP server exposes and how the tools chain together for common signing jobs.
MCP guidePlugin guideInstall the GetSign MCP plugin when your agent supports skills and you want guided recipes loaded before work begins. It helps the agent follow the right order for signing workflows.
Review every available action in the tool reference, or add guided signing recipes with the plugin guide.
Connect your AI agent to GetSign.
Bring GetSign into the AI client your team already uses. Connect once with OAuth, then ask your agent to prepare documents, send them for signature, track status, and bring the signed PDF back into your monday.com workflow.