Step-by-step flow

From account connection to approved publication.

Pinboardy is designed to make the publishing flow easy to understand for users, reviewers, and support teams. Every major action is visible and intentionally approved.

Product flow

A simple sequence with clear user checkpoints.

The core logic is structured around connected accounts, uploaded content, draft generation, user review, and explicit publication approval.

1. Connect a Pinterest account with OAuth

Users start by connecting their Pinterest account through OAuth. The product uses permission-based access and does not ask for Pinterest passwords.

2. Upload original images

Users upload images through the website or Telegram companion workflow. The system is intended for content users own or are authorized to publish.

3. Generate draft metadata with AI

AI prepares draft titles, descriptions, alt text, keywords, and board suggestions. The output is presented as a draft for review, not as an automatic publication.

4. Review and edit each draft

Users can edit generated copy, change the board, revise timing, or discard the draft. This review step is a core part of the product design.

5. Approve and publish

Publication happens only after the user explicitly approves the draft. This supports a transparent human-in-the-loop workflow.

6. Schedule, track, and manage history

Approved pins can be published immediately or scheduled. The system can keep a draft and publication history to support clarity and troubleshooting.

What each step means

The product aims to reduce manual work without hiding publishing decisions.

This public explanation is written to make the intended use and boundaries of the product clear.

OAuth explanation

OAuth allows users to authorize access to their Pinterest account in a standard way. Access can be revoked, and the product does not request account passwords.

AI draft generation explanation

AI helps prepare structured metadata drafts. Users can inspect and change those drafts before publication, which keeps the human review layer intact.

Scheduling explanation

Scheduling is available only after approval. It supports normal creator planning without removing user oversight over what is eventually published.

Reviewer notes

What a reviewer should expect to see.

The intended product behavior is clear and constrained. Reviewers should be able to verify it with minimal guesswork.

OAuth is used for account connection and revocable access.

The product is described as draft-first, not post-first.

Every publication is framed around explicit approval by the user.

Users can edit AI-generated metadata before publishing.

Telegram is a companion interface, not the source of truth for records.