Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Podio

Podio integration for Flows360 workflows.

CategoryOther
AuthenticationOAuth 2.0
Version0.2.0
Published scopes2 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Podio with Flows360

Podio integration for Flows360 workflows.

Use the Podio connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 10 actions and 6 triggers.

Available actions

  • Create Item
  • Update Item
  • Create Task
  • Update Task
  • Attach File
  • Create Comment
  • Create Status Update
  • Find Item
  • Plus 2 additional declared actions.

Available triggers

  • New Item
  • New Task
  • New Status
  • Item Updated
  • New App
  • Member Added

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Podio
  • Package: @activepieces/piece-podio@0.2.0
  • Exact artifact digest: sha256:27d4d5ded9362e41396261a103f21ecac861500878e83542f9fd325ca9f88859
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create Item (create_item), Create a new record in a Podio app with specified field values. Classification: read.
  • Update Item (update_item), Update an existing record in a Podio app with specified field values. Only provided fields will be updated. Classification: read.
  • Create Task (create_task), Add a new task to an item or workspace with due dates, assignees, and attachments. Classification: read.
  • Update Task (update_task), Modify an existing task's details or status. Only specified fields will be updated. Classification: read.
  • Attach File (attach_file), Upload and attach a file to an item/task/comment. Classification: read.
  • Create Comment (create_comment), Post a comment on an item or task. Classification: read.
  • Create Status Update (create_status), Add a status to an item or workspace stream. Classification: read.
  • Find Item (find_item), Retrieve a single item by ID or field value. Classification: read.
  • Find Task (find_task), Retrieve a task by ID for further updates. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Item, webhook.
  • New Task, webhook.
  • New Status, webhook.
  • Item Updated, webhook.
  • New App, webhook.
  • Member Added, webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects16
Supported actionsNot published
Triggers6

Authentication

Authentication method: OAuth 2.0

Required scopes

global:readglobal:write

Authentication profiles

connection · oauth2

OAuth scopes: global:read, global:write

Supported objects

ObjectReadWriteNotes
Create Item Yes No Create a new record in a Podio app with specified field values.
Update Item Yes No Update an existing record in a Podio app with specified field values. Only provided fields will be updated.
Create Task Yes No Add a new task to an item or workspace with due dates, assignees, and attachments.
Update Task Yes No Modify an existing task's details or status. Only specified fields will be updated.
Attach File Yes No Upload and attach a file to an item/task/comment.
Create Comment Yes No Post a comment on an item or task.
Create Status Update Yes No Add a status to an item or workspace stream.
Find Item Yes No Retrieve a single item by ID or field value.
Find Task Yes No Retrieve a task by ID for further updates.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Item Yes No webhook trigger declared by the pinned package.
New Task Yes No webhook trigger declared by the pinned package.
New Status Yes No webhook trigger declared by the pinned package.
Item Updated Yes No webhook trigger declared by the pinned package.
New App Yes No webhook trigger declared by the pinned package.
Member Added Yes No webhook trigger declared by the pinned package.

Triggers

New Item · Webhook

Fires when a new item (record/entry) is created in an app

Inputs

  • appId · string
New Task · Webhook

Fires when a new task is added to any workspace

Inputs

  • orgId · string
  • spaceId · string
New Status · Webhook

Fires when a new status is created in a workspace stream

Inputs

  • orgId · string
  • spaceId · string
Item Updated · Webhook

Fires when an existing item is updated (excluding comments)

Inputs

  • appId · string
New App · Webhook

Fires when a new app is created in a workspace

Inputs

  • orgId · string
  • spaceId · string
Member Added · Webhook

Fires when a new member is added to a workspace

Inputs

  • orgId · string
  • spaceId · string

Setup

Setup

  1. Add the Podio connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.

OAuth scopes

  • global:read
  • global:write
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-podio@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 10 actions and 6 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Podio connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-podio@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com