> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/stagehand/stagehand-fx/connecting-an-effect.md).
# Connecting an Effect
## HOOKING UP A SWITCHED EFFECT
The Stagehand FX has four (4) switched outputs that can be used to control any simple on/off device. The switched outputs located on the front panel are dry contact closures. In other words, the Stagehand FX doesn’t provide any power from those outputs just a switch closure. The figure below shows a typical output connection.
Reminder: The contacts are rated for 3A 30VAC/42VDC maximum. This means you may need to add a relay into the mix in order to fire higher voltage/amperage effects.
## HOOKING UP AN INPUT SWITCH
The Stagehand FX has four (4) inputs that can be used to detect a switch closure. By using normally open switch connected to a Stagehand FX input, you can trigger cue links and other actions in SpikeMark software when the switch is closed. The figure below shows a typical input connection.
---
# 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://docs.creativeconners.com/docs/stagehand/stagehand-fx/connecting-an-effect.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.
