AtlasWork, planned itself.

The AI-native, all-in-one work platform. Tasks, projects, CRM, contracts, and analytics in one calm workspace.

All systems operational
  • SOC 2 II
  • ISO 27001
  • HIPAA
  • GDPR

Product

  • Overview
  • PDF tools
  • Diagram tools
  • People & HR
  • Integrations
  • Marketplace
  • Pricing

Resources

  • Guides
  • Glossary
  • Compare
  • Docs
  • API reference
  • Support
  • Changelog
  • Status

Company

  • About
  • Careers
  • Press
  • Contact

Legal & trust

  • Trust center
  • Security
  • Privacy
  • Terms
  • DPA
  • GDPR
  • SLA
  • Refunds
  • Google API data
Atlas, a product by wrxstack.com·© 2026 wrxstack·All rights reserved
PrivacyTermsSecurityStatus
Skip to documentation
Docs
Back to Atlas

Start here

  • Overview

Developer

  • REST API guide
  • Authentication
  • API reference
  • MCP (AI agents)
  • SDKs
  • Quick actions

Webhooks

  • Overview
  • Quickstart
  • Events
  • Payloads and headers
  • Security and signing
  • Delivery and retries
  • Managing via API

Connect

  • Connectors
  • Integrations

Product

  • Collaboration and chat

Reference

  • Glossary
  • Keyboard shortcuts
  • Module reference
Figma logo

Knowledge

Figma

Embed Figma file thumbnails into Atlas tasks and watch file change activity so product reviews stay in sync.

AuthOAuth 2.0UpdatesReal-timeAvailable

What this connector does

  • Embed Figma file thumbnails inline on Atlas tasks.
  • Read file and project metadata for evidence rows.
  • Listen for file update events using Figma webhooks v2.
  • Never store full design file content.

Before you begin

  • You are a Figma team admin.
  • Your plan allows the Webhooks v2 API (Professional or higher).
  • You have a sandbox team to validate the first connection.

Get your credentials

1

Open the Figma developer settings

Sign in with the admin account. figma.com/developers/apps

2

Create a new OAuth app

Name it Atlas Connector and add the website URL.

3

Add the Atlas redirect URL

Set Callback URL to https://YOUR-ATLAS-HOST/oauth/callback/figma.

4

Select scopes

Pick file_read for file metadata access. Webhooks v2 do not require an additional scope.

5

Copy the client id and secret

Copy Client ID and Client Secret into the Atlas Figma connector settings page.

Required scopes and permissions

Read filesfile_read
Read usercurrent_user:read

Setup checklist

  1. Create the provider app in a sandbox or development workspace.
  2. Add the Atlas redirect URL to the provider app configuration.
  3. Copy the client id, client secret, or API key.
  4. Paste the credentials into the Atlas connector settings page.
  5. Click Connect and complete the provider sign-in screen.
  6. Run Test connection from the connector page to verify health.

Troubleshooting

  • invalid_token

    Refresh token expired. Reconnect from Atlas.

  • No files visible

    The connected user must be a member of the team that owns the files.

  • webhook 403

    The team plan does not include webhooks. Upgrade or use polling mode.

Webhooks

Atlas creates webhooks v2 per team and validates the signature header.

Events Atlas listens for

  • FILE_UPDATE
  • FILE_VERSION_UPDATE
  • FILE_COMMENT
  • LIBRARY_PUBLISH

Provider docs: https://www.figma.com/developers/api#webhooks-v2

Disconnect and data deletion

  1. Click Disconnect on the Atlas Figma connector page.
  2. Open developer apps and delete the Atlas Connector app.
  3. Atlas removes cached file metadata within 24 hours of disconnect.

Once you have the credentials above, paste them into the live connector page to finish connecting Figma.

Open the Figma connector page

On this page

  • What this connector does
  • Before you begin
  • Get your credentials
  • Required scopes and permissions
  • Setup checklist
  • Troubleshooting
  • Webhooks
  • Disconnect and data deletion