> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stardeck.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Connected Services

> Link external accounts—like Google Calendar—to your organization once, then let your apps use them. Stardeck holds the credentials so your app code never touches a secret.

Connected services are external accounts you link to your organization—a Google Calendar, a messaging account, and more over time. You connect a service **once** in your dashboard, decide which apps are allowed to use it, and from then on the agent can build features against it.

The key idea: **Stardeck holds the credentials.** Your apps never see access tokens or secrets. They ask Stardeck to act on the connected service, Stardeck signs the request on the app's behalf, and the service responds.

```mermaid theme={null}
flowchart LR
    App["📱 Your app"] -- "signed request" --> SD["☁️ Stardeck"]
    SD -- "holds credentials" --> Svc["🔗 External service\n(e.g. Google Calendar)"]
    Svc -- "response" --> SD
    SD -- "response" --> App
```

## How it works

Every connected service follows the same shape:

<Steps>
  <Step title="Connect the service">
    Go to your organization's **[Settings →
    Integrations](https://www.stardeck.ai/dashboard/settings?tab=integrations)** and link the
    account. You authorize once in your browser.
  </Step>

  <Step title="Grant it to apps">
    Choose which apps in your org are allowed to use the connection. An app can't reach a service it
    hasn't been granted.
  </Step>

  <Step title="Set a default (optional)">
    If you connect more than one account, mark one as the default for an app so the agent knows
    which to use unless told otherwise.
  </Step>

  <Step title="Let the agent build">
    Tell the agent what you want—"book appointments on my calendar," "send a Slack message when an
    order comes in." It wires up the rest.
  </Step>
</Steps>

Some services are **two-way**: messaging channels like LINE and Slack don't just send—your apps can also react when a message, mention, or button click comes in.

## Security

* **Credentials stay on Stardeck.** Your app code never holds the service's tokens or secrets.
* **Granted, not global.** A connection only works for apps you've explicitly granted it to.
* **Signed per app.** Every call an app makes is authenticated on that app's behalf—apps can't impersonate each other.
* **Revocable anytime.** Remove a connection or a grant from **[Settings → Integrations](https://www.stardeck.ai/dashboard/settings?tab=integrations)** and access stops immediately.

## Available services

<CardGroup cols={2}>
  <Card title="Google Calendar" icon="calendar" href="/connected-services/google-calendar/overview">
    Book appointments, check availability, create events with Google Meet links—on your calendar or
    your users' own.
  </Card>

  <Card title="LINE" icon="line" iconType="brands" href="/connected-services/line/overview">
    Message customers on their LINE Official Account, and react when they message back.
  </Card>

  <Card title="Slack" icon="slack" iconType="brands" href="/connected-services/slack/overview">
    Post to channels, send notifications, and react to messages, mentions, and button clicks.
  </Card>
</CardGroup>

<Note>
  **Not the same as [AI Integrations](/ai-integrations/overview).** Connected Services are accounts
  your *apps* use. AI Integrations connect external AI *tools* (Claude, Codex, Cursor, ChatGPT) to your
  organization over MCP. Different feature, different settings tab.
</Note>