DocsAutomations and community
Auto-posting
Schedule Telegram and Discord messages, market summaries and market-cap or holder milestones, with delivery history.
Open Automations → Auto-posting. Choose a token created on CryptoMuz or imported through its paid import flow, then select connected Telegram or Discord destinations. The dashboard checks token eligibility and available market data.
Choose a post type
- Scheduled message: send your own message on a recurring interval, for example a launch announcement or community update.
- Market summary: post an available snapshot of the token's price, market cap and holder count. Values may be delayed or unavailable and depend on supported networks and data sources.
- Milestone: post when reported USD market cap or wallet-holder count reaches your target, for example $5,000 market cap or 1,000 holders. Missing values never trigger a milestone.
Set up and review
- First connect your channels and send a test message.
- Choose the token, destinations and post type. Write the message where applicable and review the preview and available placeholders.
- Set the recurring interval or milestone target. Choose start and optional end times using your automation timezone in Settings.
- Choose whether a milestone should finish after the first post or repeat after falling below and crossing the target again, at most once an hour. Milestones are checked every five minutes.
- Start auto-posting. Use the schedules list to pause, resume or delete a schedule, inspect its last check and review recent delivery history.
Server execution and delivery
A provider timeout can occur after Telegram or Discord has accepted a post. Uncertain deliveries are not automatically resent, check the channel first. Explicit rate-limit rejections retry with backoff. Pausing or deleting a schedule cannot retract a post already being sent.
Settings → Automations controls default destinations, intervals, timezone and the account-wide pause. Market figures are estimates, not a guaranteed real-time feed. For condition notifications rather than public posts, see Alerts.