CONNECT APP
Build with Podio
Productivity
- OAuth
MCP
Give your agent Podio tools
Every Podio 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 Podio 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": "podio",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Attach File:
const result = await mcp.callTool({
name: "podio-attach-file",
arguments: {
fileId: "File ID",
objectType: "Object Type",
},
})# 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": "podio",
}
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 Attach File:
result = await session.call_tool("podio-attach-file", {
"fileId": "File ID",
"objectType": "Object Type",
})API PROXY
Call the Podio API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Podio 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.podio.com/user",
})
// Any allowed Podio 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.podio.com/user
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkucG9kaW8uY29tL3VzZXI?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Podio actions from your backend
Connect a user's Podio account once, then run Attach File 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: "podio-attach-file",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
podio: { authProvisionId: "apn_xxxxxxx" },
fileId: "File ID",
objectType: "Object Type",
},
})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="podio-attach-file",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"podio": {"authProvisionId": "apn_xxxxxxx"},
"fileId": "File ID",
"objectType": "Object Type",
},
)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": "podio-attach-file",
"configured_props": {
"podio": { "authProvisionId": "apn_xxxxxxx" },
"fileId": "File ID",
"objectType": "Object Type"
}
}'TOOLS
Podio actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Attach File
actionAttaches an uploaded file to the given object. See the documentationWritev0.0.2 -
Create an Item
actionAdds a new item to the given app. See the documentationWritev0.0.5 -
Create Status
actionCreates a status to the given workspace. See the documentationWritev0.0.3 -
Create Task
actionCreates a task to the given workspace. See the documentationWritev0.0.3 -
Find Item
actionFilters items for the given app. See the documentationRead-onlyv0.0.3 -
List Organization ID Options
actionRetrieves available options for the Organization ID field.Read-onlyv0.0.1 -
Update an Item
actionUpdates an item. See the documentationWritev0.0.5 -
Upload File
actionUploads a new file to Podio. See the documentationWritev0.1.3 -
Upload From URL
actionUploads a file from a URL to Podio. See the documentationWritev0.0.2
-
New Application Created
triggerEmit new events when a new application is created. See the documentationInstantv0.0.2 -
New Item Created
triggerEmit new events when a new item is created. See the documentationInstantv0.0.2 -
New Item Updated Event
triggerEmit new events when an item is updated. See the documentationInstantv0.0.2 -
New Organization created
triggerEmit new events when a new organization created. See the documentationv0.0.2 -
New Task Created
triggerEmit new events when a new task is created. See the documentationInstantv0.0.2 -
New View created
triggerEmit new events when a new view created. See the documentationv0.0.2 -
New Workspace created
triggerEmit new events when a new workspace created. See the documentationv0.0.2
MULTI-APP
Use Podio with other popular apps
Most products don't stop at one integration. Pair Podio with the other apps your users rely on, and ship use cases that span both.
- App slug
- podio
- Authentication
- OAuth
- Categories
- Productivity
- Actions
- 9
- Triggers
- 7
- API proxy
- Available
OAuth scopes
These are the scopes Pipedream's managed Podio OAuth client requests when one of your users connects an account. Supply your own OAuth client to request a different set.
- global:all