Files
agentrhq__authsome/docs/site/integrations/api-key/intercom.mdx
Manoj Bajaj cac5f9f2c4 fix(docs): remove all broken links to missing pages
Remove references to five pages that do not exist:
reference/provider-schema, reference/file-layout,
concepts/profiles-vs-connections, security/hosted-deployment,
guides/profiles.

Strategy: strip the links/sentences from the 59 source files rather than
creating stub pages. Card blocks pointing to missing pages are removed;
inline sentence references are removed or reworded so the surrounding
prose stays coherent.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-02 16:33:45 +05:30

107 lines
3.0 KiB
Plaintext

---
title: "Intercom"
sidebarTitle: "Intercom"
description: "Store and use your Intercom API key with authsome. Local encrypted vault, proxy injection, no key in the agent's environment."
icon: "intercom"
keywords: ["intercom api key authsome", "intercom key broker", "intercom agent credentials", "authsome intercom"]
---
import MultiConnectionsCta from "/snippets/multi-connections-cta.mdx";
import MaskedInputNote from "/snippets/masked-input-note.mdx";
import WhatsNextApiKey from "/snippets/whats-next-apikey.mdx";
Intercom uses a long-lived API key. Authsome stores the key encrypted in the local vault, injects it at request time through the proxy, and keeps it out of shell history, process listings, and environment dumps.
## At a glance
| | |
|---|---|
| Provider name | `intercom` |
| Display name | Intercom |
| Auth type | API key |
| Header | `Authorization: Bearer <key>` |
| Proxy host | `api.intercom.io` |
| Env var | `INTERCOM_API_KEY` |
| Where to get a key | [https://app.intercom.com/a/developer-hub](https://app.intercom.com/a/developer-hub) |
## Get a key
Create an API key in the Intercom dashboard at [https://app.intercom.com/a/developer-hub](https://app.intercom.com/a/developer-hub).
Intercom access tokens live under your workspace's developer hub. Replace `_` placeholders in the URL with your real workspace.
## Log in
```bash
authsome login intercom
```
A local browser form opens at `http://127.0.0.1:7998`. Paste the key into the masked input and submit.
<MaskedInputNote />
Verify:
```bash
authsome get intercom --field status
# → connected
```
## Use the key
Run the agent under the proxy. The library tab is for embedding authsome inside a larger Python orchestrator.
<CodeGroup>
```bash Proxy (recommended)
authsome run -- python my_agent.py
```
```bash Environment
eval "$(authsome export intercom --format env)"
echo $INTERCOM_API_KEY
```
```python Python library
from authsome.server.dependencies import create_auth_service
auth = create_auth_service()
key = auth.get_access_token("intercom", connection="default")
```
</CodeGroup>
Under the proxy, authsome sets `INTERCOM_API_KEY=authsome-proxy-managed` in the child's environment and injects the real key into outbound requests to `api.intercom.io`. The child process never sees the actual value.
## Multiple keys
<MultiConnectionsCta />
```bash
authsome login intercom --connection personal
authsome login intercom --connection team
```
## Rotate or remove the key
```bash
authsome login intercom --force # rotate
authsome logout intercom # remove local credential
authsome remove intercom # remove all local state for the provider
```
API-key providers have no revocation endpoint, so `revoke` and `remove` are equivalent for Intercom.
## Override the bundled definition
```bash
authsome inspect intercom > ~/.authsome/providers/intercom.json
# edit fields
authsome list # source now shows "custom" for intercom
```
## What's next
<WhatsNextApiKey />