> For the complete documentation index, see [llms.txt](https://graphdex-1.gitbook.io/graphdex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://graphdex-1.gitbook.io/graphdex-docs/getting-started/connect-with-google.md).

# Connect with Google

**Google is the OAuth twin to Telegram in the GraphDex sign-in modal — no wallet extension required, just a Google account you already have.**

Pick Google when you don't have Phantom or MetaMask installed, or when you'd rather authenticate through an existing Google account. The flow is a standard browser OAuth round-trip: pick Google, finish the Google prompt, land back in the terminal signed in. A wallet can be attached later from inside the connected session.

{% hint style="success" %}
**One Google account, one tap**

Open the modal, pick Google, approve in the Google prompt, return to the terminal signed in.
{% endhint %}

## HOW TO START

1. Open the GraphDex Terminal.
2. Click `Connect wallet`.
3. Choose **Google** in the sign-in modal.
4. Complete the Google authorization prompt.
5. Return to GraphDex after authorization.

## ACCOUNT CHECK

Before approving, make sure the Google prompt shows the right account — Chrome and other browsers will often default to the most recently used one.

* If you have several Google accounts in the same browser, the prompt may auto-select or ask you to pick.
* Confirm the email shown matches the account you want connected to GraphDex.
* If the wrong account is selected, cancel, switch in Google, and restart the flow.

{% hint style="info" %}
If Google sign-in doesn't complete: allow pop-ups and redirects for GraphDex, check that third-party sign-in isn't blocked by your browser settings, confirm the right Google account is selected, and retry on a current browser version. If it still fails, send a report through the [Help Center](/graphdex-docs/help-and-feedback/help-center.md).
{% endhint %}

## FAQs

<details>

<summary>Do I still need a wallet if I sign in with Google?</summary>

For trading, yes — you'll need to attach a wallet after signing in. For account-only features (Tracker watchlists, Referrals progress, Earn information), no. See [Connect a Wallet](/graphdex-docs/getting-started/connect-a-wallet.md).

</details>

<details>

<summary>The wrong Google account opened — how do I switch?</summary>

Cancel the prompt, switch the active Google account in your browser (Chrome → profile menu, or Google account chooser at accounts.google.com), then restart the GraphDex sign-in flow.

</details>

<details>

<summary>The flow doesn't complete — what should I check?</summary>

* Pop-ups and redirects are allowed for the GraphDex domain.
* Third-party sign-in isn't blocked by browser settings.
* The intended Google account was selected in the prompt.
* You're on a current browser version.

If the issue persists, send a report through the [Help Center](/graphdex-docs/help-and-feedback/help-center.md).

</details>

<details>

<summary>Is Google sign-in different from Telegram sign-in?</summary>

Mechanically they're parallel OAuth flows — different provider, same outcome. See [Connect with Telegram](/graphdex-docs/getting-started/connect-with-telegram.md) for the Telegram variant.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://graphdex-1.gitbook.io/graphdex-docs/getting-started/connect-with-google.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.