CONNECT APP
Build with Adobe PDF Services
File Storage
- OAuth
MCP
Give your agent Adobe PDF Services tools
Every Adobe PDF Services action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Adobe PDF Services account for each tool call — you store no tokens.
// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "adobe_pdf_services",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Extract Text and Tables From PDF:
const result = await mcp.callTool({
name: "adobe_pdf_services-extract-text-and-tables",
arguments: {
filePath: "File Path",
filename: "File Name",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", # any stable ID for this user in your system
"x-pd-app-slug": "adobe_pdf_services",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Extract Text and Tables From PDF:
result = await session.call_tool("adobe_pdf_services-extract-text-and-tables", {
"filePath": "File Path",
"filename": "File Name",
})API PROXY
Call the Adobe PDF Services API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Adobe PDF Services API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://pdf-services.adobe.io/assets",
})
// Any allowed Adobe PDF Services endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://pdf-services.adobe.io/assets
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9wZGYtc2VydmljZXMuYWRvYmUuaW8vYXNzZXRz?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Adobe PDF Services actions from your backend
Connect a user's Adobe PDF Services account once, then run Extract Text and Tables From PDF on their behalf from your own code — TypeScript, Python, or plain HTTP.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "adobe_pdf_services-extract-text-and-tables",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
adobe_pdf_services: { authProvisionId: "apn_xxxxxxx" },
filePath: "File Path",
filename: "File Name",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="adobe_pdf_services-extract-text-and-tables",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"adobe_pdf_services": {"authProvisionId": "apn_xxxxxxx"},
"filePath": "File Path",
"filename": "File Name",
},
)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "adobe_pdf_services-extract-text-and-tables",
"configured_props": {
"adobe_pdf_services": { "authProvisionId": "apn_xxxxxxx" },
"filePath": "File Path",
"filename": "File Name"
}
}'TOOLS
Adobe PDF Services actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Extract Text and Tables From PDF
actionExtracts text and table element information from a PDF document and returns a JSON file along with table data in XLSX format within a .zip file saved to the/tmpdirectory. See the documentationRead-onlyv0.0.8 -
Extract Text From PDF
actionExtracts text element information from a PDF document and returns a JSON file within a .zip file saved to the/tmpdirectory. See the documentationWritev0.0.8
EVENTS
Adobe PDF Services triggers
Event sources your backend can deploy for users and receive through a webhook.
No Adobe PDF Services triggers are available yet.
MULTI-APP
Use Adobe PDF Services with other popular apps
Most products don't stop at one integration. Pair Adobe PDF Services with the other apps your users rely on, and ship use cases that span both.
REFERENCE
App details
Reference metadata for the Adobe PDF Services connector in the Pipedream registry.
- App slug
- adobe_pdf_services
- Authentication
- OAuth
- Categories
- File Storage
- Actions
- 2
- Triggers
- 0
- API proxy
- Available