Google Photos integration

What it does

The Google Photos integration lets you organize client deliverables inside Google Photos without leaving TaskJuice. Connect a client's Google account once and TaskJuice can create albums, rename them, look up albums by ID, list every album the workspace has created for that account, and search media items scoped to an album. Google restricts the Library API to data your app creates, so TaskJuice will only ever see albums and media items that originated from a TaskJuice workflow.

Connect a Google Photos account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Google Photos and click Connect.
3. Sign in with the Google account whose Photos library you want to manage on behalf of your client.
4. Grant the requested scopes (append-only and app-created read access).
5. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

To revoke access at any time, visit Google Account permissions and remove the TaskJuice entry.

Triggers

Google Photos does not publish webhook subscriptions. To react to new photos, combine this integration with the polling utility node and the Search Media Items action.

Actions

• google-photos/create-album creates a new app-created album with the title you supply.
• google-photos/list-albums lists every album the workspace has created in the connected account, with cursor pagination.
• google-photos/get-album returns the metadata and cover photo for one album by ID.
• google-photos/update-album-title renames an existing app-created album.
• google-photos/search-media-items searches for app-created media items, optionally scoped to a single album, with cursor pagination.

Known limitations

• Since March 2025 Google restricts the Library API to data your app creates. Albums and media items uploaded through the consumer app or another integration are not visible.
• Only the appendonly and readonly.appcreateddata scopes are requested. Editing or deleting non-app-created content is not supported.
• The Library API enforces per-user quotas. When a 429 is returned, TaskJuice surfaces it as a retryable rate-limit error and respects the recommended backoff.