> For the complete documentation index, see [llms.txt](https://docs.launchboard.app/cxd/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.launchboard.app/cxd/code-internet-of-things-2.0/tutorials/create-smart-light/3.3-connect-button.md).

# C-3 Connect Button

Physical buttons that people can push are used as inputs on many different types of devices. Your Photon kit should have a set of 4 push buttons with different cap colors: red, yellow, green, and blue.

In this step, your team will connect a push button to your Photon circuit board using the breadboard.

You'll need these components:

* 1 push button (could be any color, but use same color as your LED)
* 2 jumper wires (use two different colors to help identify them)

[Follow these instructions explaining how to connect the button](https://docs.idew.org/code-internet-of-things/references/physical-inputs/push-buttons).  The button can be connected to almost any I/O pin, but connect it to the **D2** pin (which will match the wiring diagram).

![LED and Button connected to Photon](https://1128190565-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-LEGLBX3AeXb13IcoB4Q%2F-LJV49Za70I_zrPyEw5U%2F-LJV4ryoqnX9O0RlNDym%2Fexperiment-2.jpg?alt=media\&token=5f154328-6177-4e90-b265-ea89a1843a34)


---

# 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.launchboard.app/cxd/code-internet-of-things-2.0/tutorials/create-smart-light/3.3-connect-button.md?ask=<question>&goal=<user_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.