Open your workspace
Open the bot, tap Start, then open the control panel. Your workspace keeps your accounts, videos and queue together.
In the bot, tap “🎛 Dashboard”. In the Mini App, open Overview.SYNAIRGY.AICROSSPOST ENGINE
Back to the siteGET STARTED · TELEGRAM + TIKTOK + LINKEDIN
Your first video.
One clear next step.
Start with Telegram, TikTok and LinkedIn personal profiles. Connect the accounts you control, review every setting and check the result for each destination.
Telegram channels TikTok · Publishing enabled LinkedIn · personal profilesCheck all network restrictions
Connect your destinations
Open Connections and connect TikTok or LinkedIn through the network’s official sign-in screen. For Telegram, add the bot as a channel administrator with permission to publish.
LinkedIn supports personal profiles and public video posts. Reconnect the profile when access expires. If a connection needs attention, complete the recovery step before selecting it for a post.Send a ready video
Send a saved MP4 from your gallery. LinkedIn accepts videos from 3 seconds to 30 minutes, up to 20 MB. For TikTok, record with your phone camera at 30 fps: Telegram's built-in camera can record below TikTok's 23–60 fps range.
In Create post, add a caption, choose the specific accounts, select TikTok visibility and review the required confirmations.Publish and check the queue
Choose Now for your first test. Tap Review post and confirm the accounts and visibility. Open Queue to see the status and result link for each destination.
If one destination fails, fix the stated cause and retry only that destination. Review an uncertain result before sending it again.PAYMENTS
Choose a plan when you are ready.
The Plan screen shows your limits and opens Stripe Checkout. You can manage an existing subscription in the customer portal.
View the plansIF YOU GET STUCK
Start with the exact next action.
Open the connection or publication details for the reason and recovery step. Send /help to the bot for instructions.
Help & FAQUse official network authorization. Never send passwords or access tokens in a support message.