Hi ,
I am unable to use a third-party tool (Weavy) because Figma consistently returns figma.com/blocked.html during the connection flow. This happens across Brave and Chrome, on different networks (including mobile hotspot), and even with newly created accounts, which suggests the issue is not account- or device-specific. It appears the tool is attempting to load Figma inside an embedded/iframe context, which is being blocked. Could you please confirm whether embedded authentication or app loading is restricted, and advise the correct redirect or popup OAuth flow that integrations should use to avoid this error?
I am accessing Weavy directly through the official website of Weavy (weavy.ai) using my Weavy account. However, when I try to open or connect my designs inside Weavy, the Figma authorization flow redirects to figma.com/blocked.html and returns 401 errors.
I understand that the Weavy / Figma integration is not yet fully available on the Figma platform. My concern is that the current embedded login / connection flow from weavy.ai itself is failing and blocking access to my projects entirely.
Could you please confirm whether this behavior is a known or expected limitation at the moment, and whether there is a supported workaround (such as a redirect or popup-based login flow) that would allow me to continue working while the integration is still in progress?
This issue is currently blocking my active production work, so any guidance would be greatly appreciated.