Skip to content
Summer Docs
DocumentationOpen Summer ↗
Documentation /

Custom integrations

Define credential fields for another tool and arrange its workflow connection.

A custom integration groups the credential fields for a tool that is not in the standard catalog. Summer must separately connect and verify any workflow that will use it.

Define the setup

  1. Open Settings → Integrations and confirm the company and environment.
  2. Select Custom integration.
  3. Enter the integration’s name, such as your shipping provider.
  4. For each variable, enter a readable Label, its exact Environment variable name, and whether it is required.
  5. Select Add variable for additional fields. Each variable name must be unique within the setup and use uppercase letters, digits and underscores, beginning with a letter.
  6. Select Save integration.
  7. Open its tile and add each credential through the secure editor, using Summer storage or a Doppler reference.

For example, a tool might require YOUR_SERVICE_API_KEY. Enter the name in the setup definition and the real secret only in the credential editor. The definition stores field names, labels and required flags.

Arrange the actual workflow

Tell Summer which provider API or trusted interface the workflow should use, which company account it belongs to, and what a useful read or outcome looks like. Share provider documentation and safe sample record references through the agreed setup process.

Summer will confirm supported reads, any missing connection work, allowed destinations and the permission model for proposed changes. A saved custom tile does not add an API adapter, generate a webhook, enable an agent capability or authorize outgoing actions.

Instructions in company knowledge can explain how to use an authorized tool. They cannot create access to a new tool.

Edit or remove the setup

Open the custom tile and choose Edit setup to change its name or fields. Check that each field still points to the intended saved credential.

Remove setup removes the grouping and preserves its saved credentials. Remove obsolete credentials separately from the credentials list, and revoke provider keys or sessions at the provider when appropriate.

See API keys and Doppler for credential changes and history.

UP NEXTBuild your knowledge base →