← Back to all sparks
P

Plain

SUPPORT
Velocity7.5

API-first customer support platform for B2B SaaS teams consolidating Slack, email, and in-app messages into one inbox

Sidekick got skills and MCP; now Plain is clearing the path to move your history in.

sidekickmcpmigrationcustomer-supportworkflowsextensibility
Current state
Plain's recent releases built Sidekick from an in-thread helper into an operator that uses workspace skills and connects to any MCP server, with workflows becoming the trigger layer for that agent work. The newest entry moves to the other end of the funnel: custom importers pull past conversations in from any tool, including in-house systems, with no built-in importer required.
Where it's heading
Capability, then autonomy, then extensibility, and now onboarding. Removing the importer dependency means adoption stops being capped by Plain's connector roadmap, the same way the agent's ceiling stopped being its integration roadmap. The pattern across both is Plain declining to sit as the bottleneck between a customer's existing systems and its own product.
Prediction
Expect the importer work to be followed by tooling that puts migrated history to use - Sidekick reading imported conversations for context is the obvious next step given the skills and MCP groundwork already shipped.

Recent moves

  1. 5d ago

    Import past conversations from any tool, no built-in importer

    Custom importers let teams bring conversation history in from any source, including in-house systems, without waiting for Plain to build a connector. It clears the migration barrier sitting in front of the Sidekick capabilities the recent releases have been stacking up.

    View source ↗
  2. 11d ago

    Sidekick connects to any MCP server

    ⚡ SPARK

    Sidekick can now connect to any MCP server, not just Plain's own integrations. This is the release that removes the ceiling from the whole month's autonomy work — the agent's reach is now customer-defined rather than roadmap-defined.

    View source ↗
  3. 13d ago

    Sidekick gains reusable, workspace-shared skills

    ⚡ SPARK

    Teams can write a skill once and share it across the workspace, turning repeated routines into agent behavior. It converts Sidekick from a general assistant into one that encodes a specific team's procedures.

    View source ↗
  4. 18d ago

    Share published workflows by link

    Published workflows can be shared by link, landing in the recipient's editor as a reviewable draft. Small, but it treats workflow definitions as artifacts meant to travel between teams — useful once workflows are what trigger agent work.

    View source ↗
  5. 28d ago

    Sidekick gets its own full-page home and tool controls

    Sidekick gets a full page as the first sidebar item, with session management and control over which tools it can reach. Giving the agent its own surface, rather than a panel inside a thread, is what made the later autonomy releases coherent.

    View source ↗
  6. 1mo ago

    Workflows run on a recurring schedule

    Workflows can run on a recurring schedule with no thread to trigger them. It decouples automation from inbound conversations, which is a prerequisite for the agent doing proactive work.

    View source ↗