Connect Pinterest boards and publish an image Pin
Select an authorised board, prepare a supported image and publish a Pin with a clear title and destination link.
Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.
Social accounts → Pinterest; Configuration where applicable
PermissionManage connections; administrator for app credentials; Create posts + Publish posts for a live test
Before you begin
A Pinterest developer app, an eligible authorised Pinterest account and a board available to that account. Confirm the app’s trial/production entitlement for the actual API route.
Follow these steps
- In Configuration, copy the Pinterest application callback into the matching provider app. Save its matching ID and secret with Save encrypted credentials. Leave direct publishing locked during connection setup.
- Choose Pinterest Connect, grant the requested access and select the intended board from discovered destinations.
- In Social accounts, choose Verify connection and compare the account or destination identity with the intended test account.
- Attach a JPEG/PNG image, provide a required title up to 100 characters and keep the description within 500. Review an optional HTTPS link. Video Pins are not supported here.
- When a controlled test is authorised and the direct gate is enabled, select only this destination, choose Post Now once and inspect its existing receipt.
Fields and options
- Requested OAuth permissions
- boards:read, pins:read, pins:write and user_accounts:read. These are the scopes requested by the current adapter; provider products/review must permit them.
- Destination and scope
- A saved connection targets the selected board. The current module uses the production Pinterest API host; it does not switch to a separate sandbox host.
- Publishing format
- Attach a JPEG/PNG image, provide a required title up to 100 characters and keep the description within 500. Review an optional HTTPS link. Video Pins are not supported here.
Rules and limits
- Saving credentials or passing connection verification does not prove that a live publication succeeded.
- Use a dedicated test destination and the most restrictive appropriate visibility. Provider consent, app review and organisational approvals remain separate requirements.
Check the result
- Open the selected board and check the actual Pin, title, image and destination link against the receipt.
- Match the actual provider outcome to the destination receipt, remote reference and intended visibility.
If something does not look right
- For board discovery or access errors, check board ownership/access and the app’s approved scopes and entitlement. Do not assume an app labelled Trial is a complete isolated sandbox.
- Do not repeat Post Now after an ambiguous result until the original provider outcome has been checked.
Common questions
Does a connected account mean publishing is approved?
No. Connection identity, app publishing entitlement, content eligibility and the separate direct-publishing gate are independent checks.
What is a complete first test?
Official consent, correct destination discovery, successful verification, one deliberate test publication, a destination receipt and direct verification in the actual provider account.