Connected Services
Link Google Calendar, LINE, Slack and other accounts to your organization once, grant them to your apps, and build features on them without your code holding a secret.
Connected services are external accounts you link to your organization, such as a Google Calendar, a LINE Official Account or a Slack workspace. You connect a service once in your dashboard and decide which apps may use it. From then on, your coding agent can build features on 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.
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:
Connect the service
Go to your organization's Settings → Integrations and link the account. You authorize once in your browser.
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.
Build the feature
Tell your coding agent what you want, for example "book appointments on my calendar" or "send a Slack message when an order comes in". See Build features.
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 and access stops immediately.
Available services
Google Calendar
Book appointments, check availability, create events with Google Meet links—on your calendar or your users' own.
LINE
Message customers on their LINE Official Account, and react when they message back.
Slack
Post to channels, send notifications, and react to messages, mentions, and button clicks.
Other services
Settings → Integrations also manages these connections. Each one follows the same connect, grant, and default steps.
- Email: inbound addresses that forward received email to your apps. See Email.
- Google Sheets: spreadsheet access, and managed Data Store syncs.
- Facebook & Instagram: Messenger and Instagram DMs for your Facebook Pages.
- Edge Devices: Stardeck Edge hardware at your site. See Stardeck Edge.
Grant a connection to your apps
A connection does nothing until you allow an app to use it.
Open Grants
In Settings → Integrations, click Grants on the connection.
Add an app
Pick an app from your organization and grant it access. Repeat for each app that should use this connection.
Set a default
If an app can reach more than one account, mark one as the default (the star). The app's code uses the default when it doesn't name a specific account.
For email, LINE and Slack you can also grant from the app's own Settings → Integrations tab, or ask your coding agent to do it over Stardeck's MCP server. It shows you what will change and waits for your confirmation. Connecting a new account stays a dashboard step, because it needs your sign-in or credentials.
An app can only use connections you've granted to it. Granting is also how you keep accounts separated: an app you didn't grant can't see or touch the connection.
Build features
Once an app has a grant, build in the app's code with your coding agent (Claude Code, Codex, Cursor
and similar), working in your local copy of the app. See Run Your App Locally.
The agent reads the guide that ships with the integrations SDK, in
node_modules/@stardeck-customer-apps/integrations-sdk/SKILL.md, so describe the outcome you want
and let it write the code. Each service's page has example requests.
Can't work locally? Describe the same feature in the app's Build tab and Starcat Developer builds it.
Not the same as AI Integrations. 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.