With the tool activated (section 5), your agent can send a document to be signed at the right moment in the conversation: > **Note — Example: sending a contract to sign** > > A customer confirms they accept the terms of an engagement. The agent uses "Send a document to electronic signature" on the document already generated from the approved template — PandaDoc sends the signing email to the customer, and when they sign (or reject), the automatic status notice reaches your Platform without anyone having to check it by hand. PandaDoc doesn't have its own piece in the **flow builder** today: its tools are available to any agent with access, within a normal conversation, not as a step in a multi-step flow. > **Notice — Never free-form content** > > The agent can only send to signature documents ALREADY generated from a DocGen template approved by your team — it never drafts or sends an improvised document. It's the same reason this integration has no generic MCP mini-server: its surface is deliberately surgical, two tools with an exact purpose, not free access to PandaDoc's API.