Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Full read-write Claude connector for Conga

Have Claude generate documents and send them for signature in Conga

Stop clicking through Conga or Salesforce to assemble every agreement. Claude generates the document from your template, merges in the account and pricing data, stages recipients and a signing order, and sends through Conga Sign only once you approve.

Build my connectorTalk to us

Conga is the document generation, CPQ, contract lifecycle, and e-signature suite teams use to assemble proposals and agreements, then route them for signature, often alongside Salesforce. People want Claude to do more than check a document's status: to generate documents from templates, fill in data and recipients, and send them out for signature.

What is a Conga MCP server?

A Conga MCP server is a small hosted service that exposes Conga's data and actions to Claude over the Model Context Protocol, so Claude can agreements and signatures inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.

What can Conga's current connector do today?

Today, Conga's available Claude connections tend to be read-leaning or cover a thin slice: Claude may look up a document or agreement's status and its recipients, but generating a document from a Composer or Conga Sign template, populating merge data, and sending for signature are usually limited or unavailable. A custom connector adds those write actions with scoped, human-in-the-loop controls.

What does full read-write Conga access unlock?

Full read-write Conga access lets Claude generate a document from a template, merge in the right account and pricing data, add recipients and a signing order, and send it for signature through Conga Sign once you approve. The agreement prep that used to mean clicking through Conga or Salesforce happens where the request already started.

  • Generate a document from a Conga Composer or Sign template and merge in its data
  • Populate pricing, line items, and account fields on a quote or agreement
  • Add recipients and set a signing order on a Conga Sign envelope
  • Send a prepared document for signature after you approve it
  • Set an automatic reminder schedule so unsigned signers are reminded after N days when the package is sent
  • Update a draft agreement's fields or content before it goes out

Can Claude generate a document from a template in Conga?

Generating a document from a template is exactly what a full Conga connector enables. Claude pulls a Conga Composer or Sign template, merges in the right account, pricing, and line-item data, and produces the draft agreement. It works within your existing permissions, so it can only build documents you could build yourself.

Can Claude send a document for signature in Conga?

Sending for signature in Conga is supported, but it is a separate, gated action. Claude can add recipients, set a signing order on a Conga Sign envelope, and stage everything, then send through Conga Sign only after you approve. Read-leaning default connections usually cannot send at all, which is why this needs a purpose-built connector.

Can Claude update a draft agreement in Conga before it goes out?

Updating a draft agreement is part of the write flow. Claude can revise fields, merge data, and adjust content on a draft, and configure an automatic reminder schedule that reminds unsigned signers after a set number of days once the package is sent. Deleting and sending stay gated behind your confirmation, and Claude never gets more access than your own Conga account already has.

How a Conga connector works

We build a small MCP server that authenticates to Conga with OAuth 2.0 or a scoped API key and the narrowest scopes the work needs. Read tools (look up document, list recipients) and write tools (generate document, merge data, send) are separated, and outbound or destructive actions like send and delete are gated behind your confirmation. Claude never has more access than your own Conga account already has, and we can add IP allowlisting where your setup supports it.

Frequently asked questions

Can Claude generate and send a document for signature in Conga?
Yes. A custom Conga connector exposes write tools that generate a document from a template, merge in its data, add recipients, and send it for signature through Conga Sign. Sending is a separate, gated action, so Claude builds the document and you approve before anything goes out. Read-leaning default connections usually cannot send, which is why this needs a purpose-built connector.
Will Claude send or delete a Conga document without my approval?
No. Sending a document for signature and deleting one are separate, gated write actions. Claude can generate the document, merge its data, and stage the recipients, but it only sends or deletes after you approve that step. You decide which actions run automatically and which require an explicit confirmation first.
Does a Conga connector get more access than my own account?
No. The connector authenticates as your account and inherits your existing permissions, including any Salesforce-side sharing rules your Conga setup relies on. If you cannot generate or send a given document, neither can Claude. It never grants Claude more access to your Conga account than you already have yourself.

Related connectors

SignNow connectorSignRequest connectorProposify connector

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us