CONNECT APP
Build with Zip Archive API
Web & App Development
- API key
MCP
Give your agent Zip Archive API tools
Every Zip Archive API 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 Zip Archive API 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": "zip_archive_api",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Compress Files:
const result = await mcp.callTool({
name: "zip_archive_api-compress-files",
arguments: {
archiveName: "Archive Name",
compressionLevel: 10,
},
})# 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": "zip_archive_api",
}
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 Compress Files:
result = await session.call_tool("zip_archive_api-compress-files", {
"archiveName": "Archive Name",
"compressionLevel": 10,
})API PROXY
Call the Zip Archive API API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Zip Archive API 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://api.archiveapi.com/extract",
})
// Any allowed Zip Archive API 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://api.archiveapi.com/extract
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuYXJjaGl2ZWFwaS5jb20vZXh0cmFjdA?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Zip Archive API actions from your backend
Connect a user's Zip Archive API account once, then run Compress Files 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: "zip_archive_api-compress-files",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
zip_archive_api: { authProvisionId: "apn_xxxxxxx" },
archiveName: "Archive Name",
compressionLevel: 10,
},
})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="zip_archive_api-compress-files",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"zip_archive_api": {"authProvisionId": "apn_xxxxxxx"},
"archiveName": "Archive Name",
"compressionLevel": 10,
},
)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": "zip_archive_api-compress-files",
"configured_props": {
"zip_archive_api": { "authProvisionId": "apn_xxxxxxx" },
"archiveName": "Archive Name",
"compressionLevel": 10
}
}'TOOLS
Zip Archive API actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
EVENTS
Zip Archive API triggers
Event sources your backend can deploy for users and receive through a webhook.
No Zip Archive API triggers are available yet.
MULTI-APP
Use Zip Archive API with other popular apps
Most products don't stop at one integration. Pair Zip Archive API with the other apps your users rely on, and ship use cases that span both.
- App slug
- zip_archive_api
- Authentication
- API key
- Categories
- Web & App Development
- Actions
- 1
- Triggers
- 0
- API proxy
- Available