> For the complete documentation index, see [llms.txt](https://cfconfig.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cfconfig.ortusbooks.com/using-the-cli/command-overview/manage-event-gateway-instances.md). # Manage Event Gateway Instances Event Gateway Instances are currently only supported for Adobe ColdFusion. Please contact us if you'd like to sponsor this feature. ## List all Event Gateway Instances ``` cfconfig eventgatewayinstance list cfconfig eventgatewayinstance list from=serverName cfconfig eventgatewayinstance list from=/path/to/server/home ``` To receive the data back as JSON, use the `--JSON` flag. ``` cfconfig eventgatewayinstance list --JSON ``` ## Add or update an Event Gateway Instance ``` cfconfig eventgatewayinstance save myInstanceId myType "/path1/some.cfc,/path2/code.cfc" cfconfig eventgatewayinstance save gatewayId=myInstanceId type=myType cfcPaths="/path1/some.cfc,/path2/code.cfc" configurationPath="path3" to=serverName cfconfig eventgatewayinstance save gatewayId=myInstanceId type=myType cfcPaths="/path1/some.cfc,/path2/code.cfc" configurationPath="path3" to=/path/to/server/home ``` ## Delete an Event Gateway Instance ``` cfconfig eventgatewayinstance delete myInstanceId cfconfig eventgatewayinstance delete myInstanceId serverName cfconfig eventgatewayinstance delete myInstanceId /path/to/server/home ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cfconfig.ortusbooks.com/using-the-cli/command-overview/manage-event-gateway-instances.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.