Skip to content
← Back to documentation
Technical Reference

Pinterest

Pinterest integration for Flows360 workflows.

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

Overview

Connect Pinterest with Flows360

Pinterest integration for Flows360 workflows.

Use the Pinterest 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 6 actions and 3 triggers.

Available actions

  • Create Pin
  • Create Board
  • Delete Pin
  • Find Board by Name
  • Find Pin by Title/Keyword
  • Update Board

Available triggers

  • New Board
  • New Follower
  • New Pin on Board

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: Pinterest
  • Package: @activepieces/piece-pinterest@0.1.8
  • Exact artifact digest: sha256:dd3de7970d5307748afaa492fae061cd7c29ded34f4a7066498259cd5994d192
  • 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 Pin (createPin), Upload an image or video to create a new Pin on a board. Classification: read.
  • Create Board (createBoard), Create a new Pinterest board for organizing Pins. Classification: read.
  • Delete Pin (deletePin), Permanently delete a specific Pin. Classification: read.
  • Find Board by Name (findBoardByName), Search for boards by name using Pinterest's search API. Classification: read.
  • Find Pin by Title/Keyword (findPin), Search for Pins using title, description, or keywords. Classification: read.
  • Update Board (updateBoard), Update a board's name, description, or privacy settings. Classification: read.

Trigger contracts

  • New Board, polling.
  • New Follower, polling.
  • New Pin on Board, polling.

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 objects9
Supported actionsNot published
Triggers3

Authentication

Authentication method: OAuth 2.0

Required scopes

ads:readboards:readboards:writeboards:read_secretpins:readpins:writepins:read_secretuser_accounts:read

Authentication profiles

connection · oauth2

OAuth scopes: ads:read, boards:read, boards:write, boards:read_secret, pins:read, pins:write, pins:read_secret, user_accounts:read

Supported objects

ObjectReadWriteNotes
Create Pin Yes No Upload an image or video to create a new Pin on a board.
Create Board Yes No Create a new Pinterest board for organizing Pins.
Delete Pin Yes No Permanently delete a specific Pin.
Find Board by Name Yes No Search for boards by name using Pinterest's search API.
Find Pin by Title/Keyword Yes No Search for Pins using title, description, or keywords.
Update Board Yes No Update a board's name, description, or privacy settings.
New Board Yes No polling trigger declared by the pinned package.
New Follower Yes No polling trigger declared by the pinned package.
New Pin on Board Yes No polling trigger declared by the pinned package.

Triggers

New Board · Poll

Fires when a new board is created in the account.

Inputs

  • ad_account_id · string
  • privacy_filter · string
  • page_size · number
New Follower · Poll

Triggers when a user gains a new follower.

New Pin on Board · Poll

Fires when a new Pin is added to a specific board.

Inputs

  • board_id · string
  • ad_account_id · string
  • creative_types · array

Setup

Setup

  1. Add the Pinterest 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

  • ads:read
  • boards:read
  • boards:write
  • boards:read_secret
  • pins:read
  • pins:write
  • pins:read_secret
  • user_accounts:read
  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-pinterest@0.1.8; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 3 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 Pinterest 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-pinterest@0.1.8 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.