Telegram-first Meta API Integration for SaaS: Instagram/Facebook Posts, Reels, Stories, Carousels

We are building , a Telegram-first AI publishing assistant for small businesses. The current system already supports Telegram publishing: users can create posts, receive previews, approve/schedule/rewrite/cancel content, and publish through a Telegram bot. Now we want to extend the system to Instagram and Facebook using the official Meta API. This is not just a simple “post to Instagram/Facebook” integration. The goal is to build a Telegram-first mini Buffer experience: The user should manage daily publishing through the Telegram bot, while the web dashboard is used only for connecting Meta accounts, settings, logs and troubleshooting. # Main Goal Users should be able to: * send text, photo, video or multiple media to the Telegram bot; * choose content type: Post, Reel, Story or Carousel; * choose channels: Telegram, Instagram, Facebook or all suitable channels; * receive AI-generated/adapted versions for each platform; * preview content inside Telegram; * publish now or schedule from Telegram; * rewrite, edit or cancel from Telegram; * receive publishing success/failure/reconnect notifications in Telegram. # Required Platforms and Formats Instagram: * Feed image posts; * Feed video posts; * Reels; * Stories; * Carousels. Facebook: * Facebook Page posts; * Facebook Page video posts; * Facebook Reels; * Facebook Stories. Telegram: * Existing Telegram publishing logic must remain stable; * New Meta integration should not break the current Telegram bot flow. # Technical Requirements The implementation should include: 1. Meta Login / OAuth flow. 2. Facebook Page connection. 3. Instagram Business/Creator account connection. 4. Secure backend storage of access tokens. 5. Token refresh / reconnect logic. 6. Publishing permissions validation. 7. Telegram bot flow for selecting format and channels. 8. Platform-specific previews. 9. Separate publishing statuses per platform/version. 10. Media validation before publishing. 11. Clear error handling for expired tokens, missing permissions, unsupported formats and Meta API errors. 12. Logs and admin visibility for troubleshooting. 13. Preparation for Meta App Review if required. 14. A future-ready data model for advertising marketplace features, but the marketplace itself is not part of this milestone. # Very Important Product Rule The Telegram bot must be the primary interface for daily publishing operations. The web dashboard must not be required for daily publishing. It should only be used for: * Meta account connection; * business settings; * default preferences; * logs; * troubleshooting. # First Required Deliverable Before Development Before starting implementation, I need a short Meta Feasibility & Capability Matrix. The matrix should include: * platform; * format; * direct publish support; * schedule support; * required permissions; * App Review requirement; * known limitations; * technical risks; * whether the format is included in your estimate. This is required because Meta API limitations, permissions and App Review requirements must be clear before development starts. # Tech Stack The existing project uses: * Telegram bot; * Node.js / TypeScript backend; * React / Next.js frontend; * Supabase / PostgreSQL; * scheduled publishing logic; * AI post generation; * existing post status machine. The developer should be comfortable working with an existing codebase and extending the current architecture without rewriting everything from scratch. # What Is Not Included in This Stage This stage should not include: * analytics; * comments management; * direct messages; * TikTok; * LinkedIn; * YouTube Shorts; * full Buffer-style dashboard; * drag-and-drop calendar; * paid ads manager; * payments; * advertising marketplace UI; * ratings/reviews; * team collaboration features. # Expected Proposal Please include in your proposal: 1. Your experience with Meta Graph API. 2. Your experience with Instagram/Facebook publishing APIs. 3. Whether you have worked with Reels, Stories and Carousels through API. 4. Your estimated timeline. 5. Your estimated budget. 6. Suggested milestone split. 7. What risks you see. 8. What parts may require Meta App Review. 9. Whether you can start with a paid feasibility/capability matrix before implementation. # Budget I am open to proposals. Expected range: $3,000 Please do not apply with a generic proposal. I need someone who understands Meta API, publishing flows, permissions, App Review and multi-platform content architecture.