Most Figma Users Don't Know Its Agent Can Now Read Your Slack and Notion

Figma's new Agent connectors pull live context straight from Slack channels and Notion databases—so your designs are informed by real research without ever leaving the canvas.

August 12, 20267 min read Verified by AI · 3 sources checked
Works with:FigmaSlackNotion

01. What It Is

Figma Agent is an AI assistant that lives inside Figma Design and Figma Make. With its newest capability, it gains connectors built on the Model Context Protocol (MCP) paired with custom skills that let it reach outside Figma and pull live data from tools your team already uses—starting with Slack and Notion, and extending to GitHub, Atlassian, Linear and more.

In practice this means the agent can fetch a design system documented in Notion, grab a PRD from Drive, or read project context from a Slack channel, then apply that research directly to work on the canvas. One of the standout moves: using Custom Agents you can point it at a Notion page or database and say something like 'Create a flowchart from this PRD,' and it will generate a FigJam diagram based on that live content.

Because the flow runs both directions, agents can also post updates back to external systems—dropping a note in Slack, Notion, or Asana when work is done. The result is a design workflow where research, documentation, and canvas work stay connected instead of scattered across a dozen browser tabs.

Why It Matters

Designers routinely lose time hopping between Slack, Notion, and Figma just to gather context before they can start. Letting the agent read live source material means fewer copy-paste round trips, fewer stale references, and design decisions grounded in the actual requirements—turning what used to be an hour of gathering into a single prompt.

Who Can Benefit

  • Product designers who work from PRDs and specs living in Notion
  • Design system maintainers who document tokens and components outside Figma
  • Cross-functional teams coordinating in Slack who want design tied to real discussion
  • Design ops leads standardizing how research feeds into the canvas

02. Step-by-Step Guide

  1. 1

    Open the Agents panel

    In Figma Design, click the Agents icon in the left sidebar (it's also available inside Figma Make). This is where you chat with and configure the agent.

  2. 2

    Confirm your seat and plan

    You need a Full seat on a Professional, Organization, or Enterprise plan to have the agent make edits. View, Dev, and Collab seats can still chat with the agent but can't apply changes to the canvas.

  3. 3

    Connect Slack and Notion

    Set up the connectors so the agent can access your Slack channels and Notion databases. Connectors are MCP-based and pair with custom skills that define what context the agent fetches.

  4. 4

    Reference a source in your prompt

    Ask the agent to use live context—for example, point it at a Notion page or database and prompt 'Create a flowchart from this PRD.' It will pull the content and generate a FigJam diagram from it.

  5. 5

    Let it post back updates

    When the work is done, the agent can post updates back to Slack, Notion, or Asana, closing the loop so your team sees progress in the tools they already watch.

Copy-Paste Prompt
Using the linked Notion PRD, create a FigJam flowchart of the primary user journey. Group steps by phase, flag any decision points, and reference the requirements from the Slack thread I connected for edge cases.

Pro Tips

  • Combine connectors with custom skills so the agent always pulls from the right source—e.g. a skill that fetches your design system from Notion every time.
  • Because it can read Slack, keep the relevant discussion in a single channel so the agent gets clean context instead of noise.
  • Even on View, Dev, or Collab seats you can chat with the agent to explore context before someone with a Full seat commits edits.

Warnings & Limitations

  • Figma Agent launched in beta on May 20, 2026 and is free only during the open beta—after beta ends it will consume AI credits.
  • Access is being granted in waves as part of a gradual rollout, so connectors may not appear for everyone immediately.
  • Editing requires a Full seat on Professional, Organization, or Enterprise; other seat types are read/chat only.
  • Admins can disable AI features for entire teams or orgs, which may block the agent or its connectors.
#figma#slack#notion#ai-agents#design-workflow#mcp#connectors#custom-skills
Share this trick:

Related Tricks