Pinterest

CRM and sales

Pinterest for AI agents. Managed auth, ready-made tools.

Create pins and boards and read pin analytics in Pinterest on behalf of each of your users.

About Pinterest

With the Pinterest connector, your agent works with each user’s own Pinterest account. It can list boards and their pins, create a board or a pin, delete a pin and read a pin’s analytics, using only the tools your project allows.

Pinterest is a visual discovery platform where people save and share ideas as pins on boards.

Tools

What your agent can do in Pinterest.

Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Pinterest connection.

  • List boards

    Read
    pinterest_list_boards

    List the user's boards.

  • Create a board

    Write
    pinterest_create_board

    Create a new board.

  • List pins

    Read
    pinterest_list_pins

    List the pins on a board.

  • Get a pin

    Read
    pinterest_get_pin

    Get a pin's details and link.

  • Create a pin

    Write
    pinterest_create_pin

    Create a pin on a board from an image and a link.

  • Delete a pin

    Write
    pinterest_delete_pin

    Delete a pin.

  • Get pin analytics

    Read
    pinterest_get_pin_analytics

    Read impressions, saves and clicks for a pin.

Control

Limits you can set.

You decide what your agent may do in Pinterest, and Agent200 runs every call within those limits.

  • Turn single tools on or off

    Let the agent read boards and create pins, and switch off pinterest_delete_pin so it can never remove a pin.

  • Restrict what the agent reaches

    Choose the endpoints and scopes a project may use, for example boards and pins but not analytics. A call outside them is refused.

Get started

Connect Pinterest
in three steps.

  1. 1

    Set up the SDK

    Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.

    agent.js
    Conceptual example
    Set up the SDK with the Agent200 API key
    // One Agent200 API key covers every connector enabled for the project.
    const agent200 = new Agent200({
      apiKey: process.env.AGENT200_API_KEY,
    });
  2. 2

    Let your user connect Pinterest

    Each end user authorizes their own Pinterest account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.

    connect.js
    Conceptual example
    Let an end user connect their account (managed OAuth)
    // Each end user authorizes their own Pinterest account, once.
    const connection = await agent200
      .user("user_123")
      .connect("pinterest");
    
    if (connection.authorizationUrl) {
      // Show this link to your user; Agent200 handles the rest.
      console.log(connection.authorizationUrl);
    }
  3. 3

    Run with the Pinterest tools

    Name the user, the model and the tools. The model decides which Pinterest tools to call, and Agent200 executes them with that user's connection.

    run.js
    Conceptual example
    Run a request with the connector's tools
    const result = await agent200
      .user("user_123")
      .run({
        model: "openai/gpt-5.6-sol",
        input: "Pin this product photo to my Summer board",
        tools: ["pinterest"],
      });
    
    console.log(result.output);

Access

Sign-in and permissions.

  • Who signs in

    Each of your users, once, on Pinterest's own sign-in page. You never see or store their Pinterest password.

  • What access is requested

    The scopes the connection needs, such as reading boards, writing pins or reading user account analytics, listed on Pinterest's authorization screen. Users can remove the app later from their Pinterest account settings.

For agents

Instructions for AI agents.

Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Pinterest connector and how to use it.

Agent brief
Connector: Pinterest, through Agent200. In code: "pinterest".
What it does: Create pins and boards and read pin analytics in Pinterest on behalf of each of your users.
Page: https://www.agent200.com/connectors/pinterest/

1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs.
2. Sign-in is managed OAuth. Each end user approves access once, on Pinterest's own page, through the authorization link Agent200 returns. Never ask a user for a Pinterest password or token in chat.
3. Give every request a stable id for the end user. Agent200 uses only that user's own connection.
4. Read tools: pinterest_list_boards, pinterest_list_pins, pinterest_get_pin, pinterest_get_pin_analytics. Write tools: pinterest_create_board, pinterest_create_pin, pinterest_delete_pin. Name "pinterest" in the tools of a request; the model decides which tool to call.
5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it.
6. Before a write, confirm with the user, unless they asked for that exact change.
7. For setup with a specific framework, follow its guide:
   https://www.agent200.com/connectors/pinterest/framework/claude/
   https://www.agent200.com/connectors/pinterest/framework/chatgpt/
   https://www.agent200.com/connectors/pinterest/framework/claude-code/
   https://www.agent200.com/connectors/pinterest/framework/muse/
   https://www.agent200.com/connectors/pinterest/framework/grok-bot/
   https://www.agent200.com/connectors/pinterest/framework/openai-dots/
   https://www.agent200.com/connectors/pinterest/framework/claude-duet/
   https://www.agent200.com/connectors/pinterest/framework/hermes-agent/
   https://www.agent200.com/connectors/pinterest/framework/openclaw/

The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/

This page is also available as Markdown, for agents and LLMs: /connectors/pinterest.md

Guides

Use Pinterest with the AI you build on.

Step-by-step setup for Pinterest with a specific model, assistant or agent framework.

FAQ

Pinterest and Agent200, answered.

Who handles the Pinterest OAuth flow and the tokens?

Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Pinterest.

Does my agent act as the end user?

Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Pinterest connection, never another user's. It cannot reach anything the user or Pinterest has not authorized.

Can I limit what my agent can do in Pinterest?

Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.

  • HubSpot

    HubSpot

    Look up and update contacts, companies and deals in your users' HubSpot CRM.

    Managed OAuth CRM and sales
  • Salesforce

    Salesforce

    Query and update accounts, contacts and opportunities in Salesforce.

    Managed OAuth CRM and sales
  • LinkedIn

    LinkedIn

    Share posts and read profile details on LinkedIn on behalf of each of your users, where the relevant API permissions are available.

    Managed OAuth CRM and sales
  • Zendesk

    Zendesk

    Search, read, create and update Zendesk tickets, and reply to customers, on behalf of each of your users.

    Managed OAuth CRM and sales
200 OK

Start with Pinterest.
Your agent does the rest.

Your users connect their own Pinterest accounts. Agent200 handles the OAuth, the tokens and every tool call.

Book a demo.
See it in action.

Tell us who you are, then pick a time for a 1:1 session with an expert from our team.

We use your details only to email you about Agent200. See the Privacy Policy.

Pick a time. We'll take it from there.

A 1:1 session with an expert from our team, about what you are building.

Open in Calendly (opens in a new tab)