Overview
This node integrates with the Pinterest API v5 to manage Pinterest boards and pins. Specifically, for the Board - Get Many operation, it lists multiple Pinterest boards accessible by the authenticated user. It supports fetching all boards or limiting the number of results returned.
Common scenarios where this node is useful include:
- Retrieving a list of all Pinterest boards for an account to display or process elsewhere.
- Automating workflows that need to analyze or report on multiple boards.
- Integrating Pinterest board data into other applications or dashboards.
For example, a marketing team could use this node to automatically fetch all their Pinterest boards and then trigger further actions like updating content calendars or syncing board details with a CMS.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication; currently only "OAuth2" is supported. |
| Return All | Whether to return all available boards (true) or limit the number of results (false). |
| Limit | Maximum number of boards to return if "Return All" is false. Minimum value is 1. |
Output
The output consists of an array of JSON objects, each representing a Pinterest board. Each object contains the board's details as returned by the Pinterest API v5, such as board ID, name, description, and other metadata.
No binary data is output by this operation.
Example output item (simplified):
{
"id": "123456789",
"name": "My Board",
"description": "A description of my board",
...
}
Dependencies
- Requires an OAuth2 authentication credential configured in n8n to access the Pinterest API.
- The node makes HTTP requests to the Pinterest API v5 endpoints.
- No additional external dependencies are required beyond the OAuth2 credential.
Troubleshooting
- Authentication errors: Ensure the OAuth2 credential is correctly set up and has the necessary permissions to access Pinterest boards.
- API rate limits: Pinterest API may limit the number of requests; if you encounter rate limit errors, consider adding delays or reducing request frequency.
- Empty results: If no boards are returned, verify that the authenticated user actually has boards and that the OAuth2 token is valid.
- Limit vs Return All: Setting "Return All" to false but specifying a very high limit may still result in partial data due to API pagination; use "Return All" when you want complete data.