Summer Open your company’s Settings → Integrations to connect Summer to your tools. Each setup has its own access method and verification steps.
Choose the connection you need
| Connection | What you configure | Guide |
|---|---|---|
| Operational provider | Required API keys or client credentials for the selected company and environment. | Provider setup reference |
| Doppler | A read-only service token, project and config; then references to individual secrets. | API keys and Doppler |
| Slack | Workspace authorization, optional personal read access, selected channels and read/post settings. | Slack |
| Website messenger | Installation, allowed website origins, public destinations and optional verified account identity. | Install the messenger |
| Another tool | A custom setup describing the environment variables it needs. | Custom integrations |
Public website links need no clinical-provider API key. Account-specific links use a separate server-signed identity integration. Operational access to the clinical system is a further connection with its own credentials.
Add a provider
- Confirm the company in the header.
- Choose Production or Staging in the credentials area. Keep credentials for each environment separate.
- Search for the provider and open its tile.
- Review its required and optional fields. Select Add beside a field to open the credential editor.
- Store the value in Summer or reference a connected Doppler secret. Save each field.
- Confirm the tile shows the expected saved fields, then verify the intended reads with Summer as part of your company’s workflow setup.
The credential guide covers editing, revealing, rotation and removal. The provider reference lists exact names and special requirements.
Understand connection status
Required credentials saved means the required values or usable Doppler references are recorded. It does not run a live provider request, verify every permission or enable an agent capability.
Doppler disconnected means a saved reference has no active vault connection. Reconnect the intended config or edit the credential’s source.
Slack has a separate Verify account access check. It confirms the current Slack account and workspace; channel selection and history coverage still need inspection.
Operations connection pending means Summer has not finished enabling and verifying this company’s case runtime. Adding keys or choosing a workflow does not complete that managed step. Other companies do not inherit Rebody’s case access or tool configuration.
Verify the first workflow
With an authorized operator, check the provider account, environment and one known record needed for the workflow. Confirm the result against its original source. Record any missing permissions or unavailable reads rather than assuming that a saved key works.
Keep reads and proposed changes distinct. Refunds, subscription changes, vendor contact and other business effects require their supported execution connection and exact human approval. A key, custom integration or knowledge instruction cannot grant that approval.
For errors, see Troubleshooting and support. For rollout checks, see Security and testing.