Bridge URL on framework deployment
Hi, I am trying to move our workflows into code by using the framework sdk. However I've run into a bit of a snag, I synced using a local deployment from my machine and the tunnel url which I then passed as a bridge url when syncing but now I'm getting an error when trying to trigger some of the notifications I have setup with code:
I'm assuming this is because my local machine is not running the project. What I was looking for is a way to tie the code workflow we have to the API on our Novu Business account, is this possible? Or would the only way to use our Business account to process the triggered workflows be to create the workflows on the dashboard itself (no-code)?
5 Replies
@sandsower
One major requirement to use
@novu/framework
workflows is to have publicly available bridge url. In your case, you synced worklflows from local machine application (used as bridge application) and using tunnel url as bridge url.
As soon as you stop the local application node server, tunnel url is not able to forward request to.
You will need to deploy your application and your application deployed base url + novu api path becomes actual production bridge url
I would recommend to use dashboard created workflows if you don't want to manage bridge application and bridge urlIs there a way to have those be in code or is no-code the only way to do it without a bridge application? I seem to recall an option to export/import as json a while back
@sandsower
No-code is the only way to do it without bridge application.
Are there plans to provide this in the future? We'd like to move to code if possible but our backend is not written in typescript (it's in go) so a bridge application within our backend monorepo would be a no-go
Thanks for the feedback @sandsower
I am sharing this to our team. for non nodejs users, best way would be if they can directly use our api to manage the workflows. I will keep you updated once we add support of it.