> For the complete documentation index, see [llms.txt](https://docs.getmesa.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getmesa.com/connect/pinterest.md).
# Pinterest
### Connection
When you're setting up your first workflow with Pinterest, you'll need to create a Connection. Click on **Connect with Pinterest** to start the process.
You may be asked to log in to your Pinterest account if not already logged in. Once logged in, you will be prompted with a screen to give MESA access to your Pinterest account.
Then, click on the **Give access** button.
Afterwards, you will be redirected back to MESA. You can re-use the newly created connection and select it for your future workflows! MESA is now connected with Pinterest!
***
### I don't see my Pinterest workflow activating when a board or pin is created?
MESA workflows that contain **Pinterest Board Created** or **Pin Created** [Trigger](/workflow-builder/triggers.md) will run on a polling system. Meaning, on every hour or whatever the selected frequency is selected in your MESA workflow, MESA will look for any recent activity in Pinterest. As a result, you may not see immediate activity in your MESA workflow until the frequency hits.
You can find the polling system (Schedule) under the **More options**. You can keep the default frequency or adjust it.
Once the frequency hits, MESA will process every single task that has accrued within the previous timeframe.
{% hint style="info" %}
Please note that available frequencies will differ depending on your MESA billing plan.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.getmesa.com/connect/pinterest.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
