Can't seem to get webtriggers to work

Forge
1

I don’t know how to fix this. Keep getting a 424, so I started stripping back the function until I eventually just copied the examples in the forge dev docs, but they also don’t work!
Here’s what I have:

  1. in resolvers/index.js
export async function egressFunction() {

  const data = {message: "test"};

return {

statusCode: 200,

contentType: "application/json",

body: JSON.stringify(data),

  };

}
  1. in manifest.yml
 modules:
   function:    
    - key: egress-function       
      handler: resolvers/index.egressFunction

   webtrigger:
    - key: egress-web-trigger
      function: egress-function
      response:
          type: dynamic
  1. in index.jsx (just a link, but doesn’t work even with a curl -i …. call from the terminal
const App = () => {

  const WEBTRIGGER_URL = "WEBTRIGGER_URL";

return (
<>
      <Stack space="space.100">
        <Link href={`${WEBTRIGGER_URL}`}>Try</Link>
      </Stack>
</>

  );

};

This is the response I get with the curl call

date: Fri, 14 Nov 2025 09:16:26 GMT

content-type: application/json

content-length: 158

vary: Origin,Access-Control-Request-Method,Access-Control-Request-Headers

cache-control: no-cache, no-store, max-age=0, must-revalidate

pragma: no-cache

expires: 0

x-frame-options: DENY

referrer-policy: no-referrer

server: AtlassianEdge

x-content-type-options: nosniff

x-xss-protection: 1; mode=block

atl-traceid: 093cdd06098e4e768f3cc3683ba9c5c6

atl-request-id: 093cdd06-098e-4e76-8f3c-c3683ba9c5c6

strict-transport-security: max-age=63072000; preload

report-to: {"endpoints": [{"url": "https://dz8aopenkvv6s.cloudfront.net"}], "group": "endpoint-1", "include_subdomains": true, "max_age": 600}

nel: {"failure_fraction": 0.001, "include_subdomains": true, "max_age": 600, "report_to": "endpoint-1"}

x-ratelimit-limit: 25000, 25000;w=60

x-ratelimit-remaining: 23518

x-ratelimit-reset: 34

server-timing: atl-edge;dur=170,atl-edge-internal;dur=4,atl-edge-upstream;dur=167,atl-edge-pop;desc="aws-eu-central-1"

Please somebody help me understand what’s wrong?

2

In your response, instead of contentType: "application/json" can you try contentType: ["application/json"]. According to the docs, this should be the expected format.

1 Like
3

Thanks for the suggestion, but it didn’t solve the issue

4

Did you add the webtrigger URL to the external.fetch.client section of your Forge manifest? Since you’re calling it from the frontend, maybe you need to declare it.