Adobe

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

    Write
    adobe_upload_document

    Upload a file to use in an agreement.

  • Send for signature

    Write
    adobe_send_agreement

    Send a document to one or more people to sign.

  • List agreements

    Read
    adobe_list_agreements

    List the user's agreements and their status.

  • Get an agreement

    Read
    adobe_get_agreement

    Read an agreement's status and who has or has not signed.

  • Download a signed document

    Read
    adobe_download_agreement

    Download an agreement's document as a PDF.

  • Send a reminder

    Write
    adobe_send_reminder

    Remind the people who still have to sign.

  • Cancel an agreement

    Write
    adobe_cancel_agreement

    Cancel an agreement that is out for signature.

  • List templates

    Read
    adobe_list_templates

    List the reusable documents in the user's library.

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_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

Connect Adobe
in three steps.

  1. 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.js
    Conceptual example
    Set 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. 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.js
    Conceptual example
    Let 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. 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.js
    Conceptual example
    Run 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.

Agent brief
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.

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.

  • Google Drive

    Google Drive

    Find, read and organize the files in each user's Drive.

    Managed OAuth Files and knowledge
  • OneDrive

    OneDrive

    Search, read, upload and share OneDrive files, including Word, Excel and PowerPoint documents, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Dropbox

    Dropbox

    Search, read, upload and organize Dropbox files, and create shared links, on behalf of each of your users.

    Managed OAuth Files and knowledge
  • Notion

    Notion

    Search, read and write Notion pages and databases on behalf of each of your users.

    Managed OAuth Files and knowledge
200 OK

Start with Adobe.
Your agent does the rest.

Your users connect their own Adobe accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)