Developer Platform: MCP server availableDeveloper Platform: MCP server available, App SDK from Q4 2026

[ Marketing ]

Pinterest integration for your workflows.

Connect Pinterest to Collabase once and use 6 actions and 3 triggers in your workflows. No code needed, hosted in Switzerland.

Sign-inOAuth 2.0
CategoryMarketing
UpdatedOctober 2026
LicenceOpen source (MIT)
Back to the directory

Pinterest in Collabase

Connect Pinterest to Collabase once and use 6 actions and 3 triggers in your workflows. No code needed, hosted in Switzerland.

How to connect it

  1. Open the integrations in the workspace settings.
  2. Choose Pinterest and connect your account.
  3. Add a trigger or an action to the workflow.
  • Log in to Pinterest Developers and create an app.
  • In the app settings, add the Redirect URL shown below to the allowed redirect URIs.
  • New apps start with trial access: Pins and boards created through the API stay visible only to you until Pinterest grants standard access.

[ Marketing ]

Related integrations

All integrations

Tools that often share a workflow.

Questions about Pinterest

What can I automate with Pinterest in Collabase?

Pinterest brings 6 actions and 3 triggers, for example Create Pin, Create Board, Delete Pin, Find Board by Name and 2 more. You combine them in a workflow without code and mix them with every other integration.

How do I connect Pinterest to Collabase?

You open the integrations in the workspace settings, choose Pinterest and connect your account once, using OAuth 2.0. After that all triggers and actions are available in the workflow.

Can Pinterest start a workflow?

Yes. Pinterest provides 3 triggers, for example New Board, New Follower and New Pin on Board. The workflow runs as soon as the event happens.

Does the Pinterest integration cost extra?

No. All integrations are included in every licence, in the Isolated Cloud and in Self-Hosted operation. There is no module price.

Test it against your own content. A proof of concept is ready within days.

We set up an instance with your content and you test it against real workflows. In a first conversation we clarify scope, operating model and timing.