Manage and automate Twitter community operations. Recommended: Use from Panel → Communities Module for easier management.#
Join Communities#
Join multiple communities automatically with your accounts.Input: Community URL(s) or ID(s)
Output: Success/fail report per accountCommunity URL(s) or ID(s) (paste or upload .txt)
Accounts (tokens - paste or upload .txt) (Formats) Proxy list (paste or upload .txt) - Optional but recommended
Threads (optional, default: 30)
Use case: Quickly join communities with multiple accounts for engagement
Leave Communities#
Leave multiple communities automatically with your accounts.Input: Community URL(s) or ID(s)
Output: Success/fail report per accountCommunity URL(s) or ID(s) (paste or upload .txt)
Accounts (tokens - paste or upload .txt) (Formats) Proxy list (paste or upload .txt) - Optional but recommended
Threads (optional, default: 30)
Use case: Clean up community memberships, mass exit unwanted communities
Check Join Requests#
Check if accounts are members of specific communities.Input: Community URL(s) or ID(s)
Output: Member status per accountCommunity URL(s) or ID(s) (paste or upload .txt)
Accounts (tokens - paste or upload .txt) (Formats) Proxy list (paste or upload .txt) - Optional
Threads (optional, default: 50)
Use case: Verify membership status, audit community access
Send tweets to a specific community from multiple accounts.Input: Community URL/ID and tweet text
Output: Success/fail report with tweet URLsCommunity URL or ID (text)
Tweet text (single or list with spintax)
Accounts (tokens - paste or upload .txt) (Formats) Proxy list (paste or upload .txt) - Optional but recommended
Delay min/max (seconds between posts, default: 10-20)
Threads (optional, default: 30)
Spintax support: {Hello|Hi|Hey} community! {Great|Amazing} to be hereUse case: Coordinate community engagement, campaigns within communities
Like tweets from specific communities automatically.Input: Community URL/ID
Output: Success/fail report per accountCommunity URL or ID (text)
Max posts to like per account (optional, default: 10)
Accounts (tokens - paste or upload .txt) (Formats) Proxy list (paste or upload .txt) - Optional but recommended
Delay min/max (seconds between likes, default: 5-15)
Threads (optional, default: 50)
Use case: Boost community engagement, support community content
Reply to a specific community post from multiple accounts.Input: Tweet URL (community post) and reply text
Output: Success/fail report with reply URLsCommunity URL or ID (text)
Tweet URL (community post - text)
Reply text (single or list with spintax)
Accounts (tokens - paste or upload .txt) (Formats) Proxy list (paste or upload .txt) - Optional but recommended
Delay min/max (seconds between replies, default: 10-20)
Threads (optional, default: 30)
Use case: Create discussion, coordinate community responses
Retweet posts from specific communities automatically.Input: Community URL/ID or specific tweet URLs
Output: Success/fail report per accountCommunity URL or ID (text)
Tweet URL(s) (paste or upload .txt)
Accounts (tokens - paste or upload .txt) (Formats) Proxy list (paste or upload .txt) - Optional but recommended
Delay min/max (seconds between retweets, default: 5-15)
Threads (optional, default: 50)
Use case: Amplify community content, boost community visibility
Execution#
Panel recommended: Easier management via Communities Module in panel
Delays recommended: Avoid rate limits
Proxies recommended: For bulk tasks
Results: Delivered as .txt files with success/fail breakdown
Telegram: /home → Communities
Panel (Recommended): Panel → Communities Module
API: POST /api/v1/modules/{moduleId}/execute (Ref) Note: Community features work best when managed through the web panel's Communities section for visual interface and easier coordination.Modified at 2025-12-05 23:07:50