Frontend needs server-side support, correct deployment approach?

Hi everyone,

I have build app with an Item View feature, it is already released and hosted on monday.com as client-side code. Now i need to add server-side support for my app. I’m trying to understand the recommended way to implement it. Looks like my current approach might be wrong. i implemented server-side logic and hosted it on monday.code as Server-side code. I am testing it using a draft version, but it doesn’t work. I keep getting CSP errors when the frontend tries to call the backend.

Do i need to change deployment type for my app, pack client-side and server-side code together and host it as server-side code on the monday.com to fix this issue? Is it ok to change deployment type for released app? or how to implement it correctly?

Any clarification would be really helpful. Thanks!

Hello @Juliia
You don’t need to bundle client and server together. It’s fully supported to keep your Item View as client side code and add a separate monday code backend.

The main issue is usually how the frontend calls the backend. Avoid hardcoding the monday code URL. Use the mondayCodeHostingUrl from the SDK context so the request matches the correct app version and region. This typically resolves CSP errors.

Also make sure your draft Item View is calling the draft backend URL. Mixing draft and live URLs often shows up as CSP errors.

If it still doesn’t work, check your backend CORS configuration and confirm it allows requests from the monday iframe origin.

Changing the deployment setup for a released app is OK. Just create a new app version, test it in draft, and then promote it to live.

Dr. Tanvi Sachar
Monday Certified Partner, Tuesday Wizard

1 Like