OnimatorOnimator
Check price

What is IGBot? IGBot is the Instagram-specific bot installation within the Onimator product family — the dedicated Instagram automation platform that handles the specific tool set, configuration surface, and behavioral patterns Instagram automation requires, and the specific installation that other Onimator components reference when they need to coordinate with Instagram-side operations. Rather than bundling Instagram automation into a monolithic multi-platform binary, the Onimator ecosystem splits platform-specific automation into dedicated installations — IGBot for Instagram, plus platform-specific bots for Threads, TikTok, Snapchat, and other supported platforms — each of which maintains its own bot folder, its own device registrations, its own per-account configurations, and its own operational surface. IGBot is the specific installation that Instagram-focused operators deploy, and the specific reference point sibling bots use when they need to avoid parallel-execution conflicts with Instagram accounts on shared devices.

How IGBot Relates to Onimator

The naming reflects the product’s history. Instagram automation was the original platform Onimator’s technology started against, and IGBot was the specific product name during the platform’s early development. As the technology extended to Threads, TikTok, Snapchat, Reddit, and dating platforms, the umbrella product name became Onimator while the platform-specific installations retained their original naming conventions — IGBot for Instagram, sibling bots for each additional platform.

The specific implication for current operators is that IGBot isn’t a separate product from Onimator; it’s the Instagram-specific installation within the Onimator ecosystem. Operators running Instagram automation are running IGBot; operators running Instagram plus Threads plus TikTok are running IGBot plus the Threads bot plus the TikTok bot, all coordinated through the shared OniHelper Suite that manages them at the fleet level.

What IGBot Handles

IGBot exposes the specific tool set Instagram automation requires. The Engage Tool handles the composite outbound engagement (follow, like, comment, DM, story view) that replaced standalone single-action bots. Post Monitor handles reactive engagement dispatch against new posts from monitored accounts. Post Scheduler handles content publishing at defined times. Story Viewer Bot, Reels Watching Bot, and other passive-engagement tools handle the internal behavioral signals Instagram treats as load-bearing indicators of account legitimacy.

Each tool operates against per-account configuration IGBot stores in the account’s settings within the IGBot installation. The specific configuration values (action limits, timing ranges, target lists, warm-up settings) live inside IGBot’s bot folder and get read by IGBot’s core execution engine when running sessions against the device.

Multi-Bot Coordination

The specific reason IGBot exists as a distinct installation rather than as one part of a monolithic multi-platform binary is that each platform’s automation has enough platform-specific tooling, configuration, and behavioral characteristics that bundling them together would produce a UI too complex to serve any single platform well. The split lets each platform-specific bot install expose the tools that actually apply to that platform, without cluttering the interface with tools from platforms the operator isn’t running against.

Coordination between IGBot and sibling bots happens through references between installations. When the Threads Manager tab in the OniHelper Suite runs its Avoid Conflicts with Instagram Accounts on Same Device option, it reads the IGBot installation’s schedules from the specified IGBOT Folder path and treats those windows as blocked slots when calculating where Threads windows can fit. This produces coordinated scheduling across both bots without requiring the operator to manually reconcile schedules between installations.

The specific implication is that the IGBot installation’s Bot Folder path becomes a load-bearing configuration for sibling-bot coordination features. Operators running Instagram plus Threads on shared devices need the IGBOT Folder specified correctly in the Threads Manager’s Time Manager sub-tab for the Avoid Conflicts feature to prevent the specific parallel-execution signature that flags accounts as coordinated automation from one hardware source.

The Bot Folder Structure

Each IGBot installation maintains a bot folder — the data directory that stores the installation’s device registrations, per-account configurations, session histories, scheduled posts, target lists, and everything else the installation needs to persist between sessions. The OniHelper Suite reads and writes to this same bot folder when it performs bulk operations against IGBot accounts, which means changes made through OniHelper appear in IGBot on the next refresh without any synchronization step.

For operators running multiple IGBot installations (rare but occasionally justified — separate installations for separate client operations, separate installations for testing versus production), each installation maintains its own bot folder, and coordination between them requires specifying the correct folder path in each context. Most operators run a single IGBot installation and coordinate everything through the shared bot folder that installation uses.

Where IGBot Sits in the Product Family

IGBot is one of the specific platform installations within the broader Onimator ecosystem. Parallel installations exist for Threads (with its own bot folder), TikTok (with its own), and other supported platforms. Each installation handles the automation for its specific platform, and OniHelper Suite provides the shared bulk-management surface that spans all of them. Xmator handles X automation through cloud architecture rather than through the real-device model IGBot and its siblings use.

Operators running Instagram plus additional platforms typically maintain the IGBot installation alongside the Threads bot, TikTok bot, and any other platform-specific installations the strategy requires. The OniHelper Suite acts as the coordination layer that lets the operator work with all installations from one interface for tasks that span platforms (analytics reporting, tagging, cross-platform scheduling coordination).

Why the Split Architecture Exists

The specific reason Onimator splits platform-specific automation into dedicated installations rather than bundling them is that each platform’s automation has enough platform-specific tooling, safety requirements, and behavioral characteristics that a monolithic multi-platform bot would either produce a cluttered UI or force platform-specific tools into a shared interface that doesn’t fit any platform well. Instagram’s Engage Tool has no meaningful analog on TikTok; TikTok’s specific FYP-oriented tooling has no meaningful analog on Instagram; dating platform Matching tools have no analog on either.

The split lets each installation expose the specific tool set that actually applies to its platform, at the specific configuration granularity that platform requires. IGBot handles Instagram-specific tools with Instagram-appropriate configuration surfaces; sibling installations handle other platforms with their respective specific tools and surfaces. The OniHelper Suite handles cross-installation work through the dedicated fleet-management tools designed for it.

Why It Matters for Automation

IGBot is the specific installation Instagram-focused operators actually run. Understanding that IGBot is the Instagram-specific installation within the Onimator ecosystem — rather than a separate product or the same product as Onimator generally — matters for operators specifically because it clarifies the operational architecture. Sibling-bot coordination requires the IGBot installation’s bot folder specified correctly; OniHelper Suite operations reference IGBot accounts through the shared bot folder; support resources and documentation often refer to Instagram-specific features by their IGBot naming. Operators running the platform without this context sometimes struggle to reconcile documentation that references IGBot with their Onimator installation, when the two are the same installation viewed under different names.

Related Terms