Pinterest in Sume: Moodboard connect vs the Integrations page
Pinterest shows as coming soon in the integrations catalog. Moodboard and Assets Pinterest connect is a separate path with its own app, not a second OAuth app.
Pinterest appears in Sume's integrations catalog as coming soon and is hidden from the Integrations page. Connecting Pinterest in Moodboard or Assets is a different, separate path, tracked as SUM-680. The catalog deliberately does not add a second Pinterest OAuth app, so the two should not be confused.
What the catalog says
The catalog doc lists Pinterest under Marketing and social with the coming-soon gate. It also says the Moodboard and Assets Pinterest connect (SUM-680) is separate, and that the architecture page "does not duplicate it". So the Integrations page has no Pinterest Connect button, and /api/integrations reports Pinterest as coming-soon.
Which one to use
| Where | Status | Purpose |
|---|---|---|
| Integrations page | Coming soon, hidden | Workspace agent tools; no Connect path yet |
| Moodboard or Assets | Separate path (SUM-680) | Pinterest connect for references and assets |
Why the Integrations row is gated
The coming-soon providers share integrationAvailability, which disables Connect, demos and agent tools together. A provider goes live only when there is a verified OAuth app and a reviewed set of tools. Catalog-only providers have no verified hosted MCP and OAuth pair in the docs, so there is nothing to wire yet.
What to do for a Pinterest campaign
If you are making pins, the generation side does not depend on an integration. Generate the image or video with the API and upload it to Pinterest yourself. For the content-policy side, see can I use AI images on Pinterest.
Avoiding double setup
Do not look for a second Pinterest login on the Integrations page, and do not assume that connecting in Moodboard turns on agent tools for Pinterest. The two paths serve different jobs and the catalog does not merge them.
If your team needs Pinterest data in agent runs, ask for it as a feature request; the doc says each provider needs its own official URL and app first.
Related posts
More in Integrations
- Pub/Sub push ack codes and a Sume webhook relay with a signature check
Pub/Sub treats only 102, 200, 201, 202 and 204 as acks. Verify Sume's sume-v1 signature at the edge, publish, return 2xx, and let Pub/Sub retry the workers.
- readOnlyHint is not authorization: how Sume gates connector tools
A server's readOnlyHint never grants access in Sume. Connector tools need an explicit allowlist, checked when tools are listed and again when a call executes.
- Shopify storefront MCP moved to /api/ucp/mcp: update the URL, add Sume
Shopify's storefront MCP now lives at https://{shop}/api/ucp/mcp, not /api/mcp. Update your agent, then add Sume at mcp.sume.com/mcp for product video.
- Shopify UCP needs an agent profile per call: where a Sume clip fits
Shopify's UCP storefront MCP needs an agent profile on every request. A product clip belongs after get_product, as an async Sume job the agent collects later.
Written by Sume