# geni integration get

> Print one integration's setup metadata — env var names, the field schema, OAuth scopes, and the setup guide.

Source: https://docs.generalinput.com/cli/integration/get



```sh
geni integration get <service> [flags]
```

Everything needed to walk someone through connecting a service, or to know what a credential of it will produce before you declare one.

## Synopsis [#synopsis]

```sh
geni integration get slack
geni integration get salesforce --json
geni integration get salesforce --field envVars
```

| Arg / Flag       | Notes                                                                                        |
| ---------------- | -------------------------------------------------------------------------------------------- |
| `<service>`      | Service slug.                                                                                |
| `--json`         | Machine-readable output (full record).                                                       |
| `--field <path>` | Print one dotted-path field. Useful paths: `envVars`, `oauthScopes`, `fields`, `setupGuide`. |

## Output [#output]

```
slack    Slack
type:    oauth2

description:
  Send messages, react to events, and read history as a specific user.

OAuth scopes:
  channels:history                     history of public channels
  chat:write                           send messages as the user
  …

Secret schema:
  accessToken          secret
  teamId               config

Bash env vars set when used:
  $SLACK_ACCESS_TOKEN, $SLACK_BOT_TOKEN
```

The env var names here are the schema-derived base names. A real credential's names carry an `_<id>` suffix so two credentials of one service can coexist in a single call; read those from [`geni credential get <id> --field envVars`](/cli/credential/get).