Hi, In my connect plugin, My app (For example: hosted on www.abc.com ) generate a javascript code which user can embed in his website/app. This javascript loads javascript file from www.abc.com (my connect app url) and also calls some API from my App url. How can i achieve the same with Forge app?…

Name: Implementing REST endpoints with web triggers | Atlas Camp 2025
Uploaded: 2025-02-14T06:16:24Z
Description: You can check this recently published video about web triggers for implementing REST endpoints for an app: [Implementing REST endpoints with web triggers | Atlas Camp 2025]

Web triggers can return data, would that meet your needs? https://developer.atlassian.com/platform/forge/manifest-reference/modules/web-trigger/

Yes this works. But when i tried to embed this webtrigger url in https://77e69e7a-2e4e-417c-a279-0f65a519c9ae.hello.atlassian-dev.net/x1/h76mmE0rfv_6T0sApGFE6z34GCw in the iframe as src. It gives me “424 Failed Dependency”. Is there a way to define cross origin policy so that this url can be render…

You can check this recently published video about web triggers for implementing REST endpoints for an app: [Implementing REST endpoints with web triggers | Atlas Camp 2025]

Thanks for sharing this video, but we have a requirement where I need to show the web trigger URL in an iframe. This video does not answer this. I tried setting up ‘X-Frame-Options’, ‘Content-Security-Policy’ and ‘Access-Control-Allow-Origin’ headers in the trigger response, but it did not worked.

I think setting fetch.client permissions might be what you need? https://developer.atlassian.com/platform/forge/manifest-reference/permissions/#fetch

added below in manifest external: frames: - 'https://*.hello.atlassian-dev.net' fetch: client: - 'https://*.hello.atlassian-dev.net' backend: - 'https://*.hello.atlassian-dev.net' still getting in the response x-frame-options: DENY

The URL should be the URL of the web trigger itself - is that the format of the web trigger URL? And did you re-install to get the latest version?

Also try without the https:// prefix.

Added below configuration external: frames: - 'https://*.hello.atlassian-dev.net' - '*.hello.atlassian-dev.net' fetch: client: - 'https://*.hello.atlassian-dev.net' - '*.hello.atlassian-dev.net' backend: - 'https://*.hello.atlassian-…

My apologies, I think you actually need to declare the URL as a frames permission.

The Atlassian Developer Community

URL for Forge app

Forge Adopting Forge from Connect

CaterinaCurti February 14, 2025, 6:16am 4

You can check this recently published video about web triggers for implementing REST endpoints for an app: