# Adobe for AI agents. Managed auth, ready-made tools.

> Send documents for e-signature with Adobe Acrobat Sign, track signing and download signed agreements on behalf of each of your users.

- Page: https://www.agent200.com/tools/adobe/
- Category: Files and knowledge
- Authentication: Managed OAuth
- Identifier in code: `adobe`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-15

## Instructions for AI agents

Connector: Adobe, through Agent200. In code: "adobe".
What it does: Send documents for e-signature with Adobe Acrobat Sign, track signing and download signed agreements on behalf of each of your users.
Page: https://www.agent200.com/tools/adobe/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Adobe's own page, through the authorization link Agent200 returns. Never ask a user for a Adobe password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: adobe_list_agreements, adobe_get_agreement, adobe_download_agreement, adobe_list_templates. Write tools: adobe_upload_document, adobe_send_agreement, adobe_send_reminder, adobe_cancel_agreement. Name "adobe" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/tools/adobe/framework/claude/
   https://www.agent200.com/tools/adobe/framework/chatgpt/
   https://www.agent200.com/tools/adobe/framework/claude-code/
   https://www.agent200.com/tools/adobe/framework/muse/
   https://www.agent200.com/tools/adobe/framework/grok-bot/
   https://www.agent200.com/tools/adobe/framework/openai-dots/
   https://www.agent200.com/tools/adobe/framework/claude-duet/
   https://www.agent200.com/tools/adobe/framework/hermes-agent/
   https://www.agent200.com/tools/adobe/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

## About

With the Adobe connector, your agent works with Adobe Acrobat Sign in each user's account: it sends documents for e-signature, checks who has signed, sends reminders and downloads signed agreements. Each user connects their own Acrobat Sign account through managed OAuth, and your agent stays within that account and the operations your project allows.

Adobe Acrobat Sign is Adobe's e-signature service for sending, signing and tracking agreements.

## Adobe tools

- **Upload a document** (`adobe_upload_document`, write): Upload a file to use in an agreement.
- **Send for signature** (`adobe_send_agreement`, write): Send a document to one or more people to sign.
- **List agreements** (`adobe_list_agreements`, read): List the user's agreements and their status.
- **Get an agreement** (`adobe_get_agreement`, read): Read an agreement's status and who has or has not signed.
- **Download a signed document** (`adobe_download_agreement`, read): Download an agreement's document as a PDF.
- **Send a reminder** (`adobe_send_reminder`, write): Remind the people who still have to sign.
- **Cancel an agreement** (`adobe_cancel_agreement`, write): Cancel an agreement that is out for signature.
- **List templates** (`adobe_list_templates`, read): List the reusable documents in the user's library.

## Limits you can set

**Turn single tools on or off.** Allow `adobe_list_agreements` and the other read tools, and switch off `adobe_send_agreement` and `adobe_cancel_agreement` if your agent should only track signing.

**Restrict what the agent reaches.** Choose the endpoints and scopes a project may use. A call outside them is refused.

## Get started

### Step 1: Set up the SDK

Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 2: Let your user connect Adobe

Each end user authorizes their own Adobe account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

File `connect.js`:

```js
// Each end user authorizes their own Adobe account, once.
const connection = await agent200
  .user("user_123")
  .connect("adobe");

if (connection.authorizationUrl) {
  // Show this link to your user; Agent200 handles the rest.
  console.log(connection.authorizationUrl);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 3: Run with the Adobe tools

Name the user, the model and the tools. The model decides which Adobe tools to call, and Agent200 executes them with that user's connection.

File `run.js`:

```js
const result = await agent200
  .user("user_123")
  .run({
    model: "openai/gpt-5.6-sol",
    input: "Send the NDA to jane@acme.com for signature",
    tools: ["adobe"],
  });

console.log(result.output);
```

(Conceptual example of the Agent200 SDK.)

## Sign-in and permissions

**Who signs in.** Each of your users, once, on Adobe's own sign-in page. You never see or store their Adobe password.

**What access is requested.** The scopes shown on Acrobat Sign's consent screen, such as reading agreements, sending agreements for signature and reading library templates.

## Example requests

- "Send the NDA to jane@acme.com for signature"
- "Who still has to sign the Hamilton contract"
- "Remind everyone who hasn't signed the lease yet"
- "Download the signed partnership agreement"

## Guides: Adobe with your AI framework

- [Adobe + Claude](https://www.agent200.com/tools/adobe/framework/claude.md): Connect Adobe to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Adobe + ChatGPT](https://www.agent200.com/tools/adobe/framework/chatgpt.md): ChatGPT cannot send an API key to a custom MCP server, so this guide builds Adobe into your own agent with OpenAI's models and the Agent200 SDK.
- [Adobe + Claude Code](https://www.agent200.com/tools/adobe/framework/claude-code.md): Have Claude Code build a Adobe agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.
- [Adobe + Muse](https://www.agent200.com/tools/adobe/framework/muse.md): Connect Adobe to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Adobe + Grok Bot](https://www.agent200.com/tools/adobe/framework/grok-bot.md): Connect Adobe to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Adobe + OpenAI Dots](https://www.agent200.com/tools/adobe/framework/openai-dots.md): Dots cannot send an API key to a custom MCP server, so this guide builds an always-on Adobe agent with OpenAI's models and the Agent200 SDK.
- [Adobe + Claude Duet](https://www.agent200.com/tools/adobe/framework/claude-duet.md): Connect Adobe to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Adobe + Hermes Agent](https://www.agent200.com/tools/adobe/framework/hermes-agent.md): Connect Adobe to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Adobe + OpenClaw](https://www.agent200.com/tools/adobe/framework/openclaw.md): Connect Adobe to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

## FAQ

### Who handles the Adobe OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Adobe.

### Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Adobe connection, never another user's. It cannot reach anything the user or Adobe has not authorized.

### Can I limit what my agent can do in Adobe?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

## Related connectors

- [Google Drive](https://www.agent200.com/tools/google-drive.md): Find, read and organize the files in each user's Drive.
- [OneDrive](https://www.agent200.com/tools/onedrive.md): Search, read, upload and share OneDrive files, including Word, Excel and PowerPoint documents, on behalf of each of your users.
- [Dropbox](https://www.agent200.com/tools/dropbox.md): Search, read, upload and organize Dropbox files, and create shared links, on behalf of each of your users.
- [Notion](https://www.agent200.com/tools/notion.md): Search, read and write Notion pages and databases on behalf of each of your users.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
