Files and knowledge
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.
About Adobe
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.
Tools
What your agent can do in Adobe.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Adobe connection.
-
Upload a document
Writeadobe_upload_documentUpload a file to use in an agreement.
-
Send for signature
Writeadobe_send_agreementSend a document to one or more people to sign.
-
List agreements
Readadobe_list_agreementsList the user's agreements and their status.
-
Get an agreement
Readadobe_get_agreementRead an agreement's status and who has or has not signed.
-
Download a signed document
Readadobe_download_agreementDownload an agreement's document as a PDF.
-
Send a reminder
Writeadobe_send_reminderRemind the people who still have to sign.
-
Cancel an agreement
Writeadobe_cancel_agreementCancel an agreement that is out for signature.
-
List templates
Readadobe_list_templatesList the reusable documents in the user's library.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Adobe, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Allow
adobe_list_agreementsand the other read tools, and switch offadobe_send_agreementandadobe_cancel_agreementif 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
Connect Adobe
in three steps.
-
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.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
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.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // 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); } -
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.
run.jsConceptual exampleRun a request with the connector's tools 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);
Access
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.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Adobe connector and how to use it.
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/
This page is also available as Markdown, for agents and LLMs: /tools/adobe.md
Guides
Use Adobe with the AI you build on.
Step-by-step setup for Adobe with a specific model, assistant or agent framework.
-
Adobe + Claude
How to connect Adobe to Claude
-
Adobe + ChatGPT
How to connect Adobe to ChatGPT
-
Adobe + Claude Code
How to connect Adobe to Claude Code
-
Adobe + Muse
How to connect Adobe to Muse
-
Adobe + Grok Bot
How to connect Adobe to Grok Bot
-
Adobe + OpenAI Dots
How to connect Adobe to OpenAI Dots
-
Adobe + Claude Duet
How to connect Adobe to Claude Duet
-
Adobe + Hermes Agent
How to connect Adobe to Hermes Agent
-
Adobe + OpenClaw
How to connect Adobe to OpenClaw
FAQ
Adobe and Agent200, answered.
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.