It's possible to change custom start command via API?
Hello. I have an n8n instance running in queue mode. I have a worker with 30 councurrency working. Everything fine. But I have a nightly one-time task that need to run 15-20k requests... So + concurrency means it will finish earlier...
I would like to know if It's possible to use API to make a change to the custom start command and change it back to what it was before after completing this task also via API.
Solution:Jump to solution
these are all the variables that will be available automatically to your deployment
https://docs.railway.app/develop/variables#railway-provided-variables...
18 Replies
Project ID:
53d90c0e-0d69-400d-8c78-aaa211f288a153d90c0e-0d69-400d-8c78-aaa211f288a1
I see there's a public API https://docs.railway.app/reference/public-api to use, but I can't seem to find anything that mentions the custom start command
have a look through the playground https://railway.app/graphiql
you want the
serviceInstanceUpdate mutationAnd that mutation is specific for the "custom start command" or it's used for more actions?
you can use it to update a lot of things on a given service, once of which is the start command
ah ok
I see now
yep that's it
one last question
When I send the API
do I need to also use the API re-deploy
Or by sending it Railway will detect that change
and will re automatically?
(I have re ON)
oh good question I forgot, you would need to use the api to redeploy
ah
Okay
The environment id is the same as the project id?
I only have production
they are very much not the same
ok, just double checking because I only have one environment in my project
so I though maybe they use the same id
Solution
these are all the variables that will be available automatically to your deployment
https://docs.railway.app/develop/variables#railway-provided-variables
but I think I need to know my environment id to send it on the graphql api
yes, please have a look at this docs section
perfect
made it work
thanks again
awsome!