Skip to main content

​
One integration workspace

Open Settings → Integrations to configure vendors, monitor their health, and manage authentication. Administrators see three tabs:
  • Connections is the default view. A connection combines one connector, its non-secret endpoint settings, and governed authentication.
  • Health shows connection diagnostics and connector execution activity.
  • Credential vault is an advanced inventory for encrypted credentials, revocation, and rotation. The Connections tab presents every configured integration in one list, regardless of its internal execution implementation. Analysts retain read-only access. Only organization and super administrators can add, test, or manage connections.

​
Certified connectors

​
Add an integration

  1. Select Add integration from the Connections tab.
  2. Choose a provider from the searchable logo catalog.
  3. Enter a friendly connection name and choose an authentication method.
  4. Complete the connector-defined Connection details and Authentication fields. Slugs, connector versions, and fixed endpoints are derived automatically.
  5. Review organization scope and requested OAuth scopes. Custom approved hosts and platform-wide visibility are under Advanced settings.
  6. For connectors with guided setup, select Connect integration. Casebender saves the credential and connection as one operation, then performs a health check. Other providers continue into their established provider-specific configuration.
If a vendor health check fails, the connection remains saved. Select Manage from its row to correct the endpoint or authentication and retry. Webhook keys are displayed once after setup and must be copied immediately. OAuth connectors redirect to the vendor and return to the setup wizard. Only a non-secret draft is stored in the browser while authorization is in progress.

​
Manage integration settings

Select Manage on an integration to open one settings workspace:
  • General owns identity, organization scope, endpoint, enabled state, and health testing.
  • Authentication owns encrypted secrets and OAuth authorization. Replacing authentication creates and selects a credential for the existing connection; it never starts the Add integration wizard or creates a second connection.
  • Automation owns polling, webhook ingestion, synchronization, mappings, and automatic provider behavior.
  • Advanced owns transport and low-frequency provider controls, approved hosts, webhook-key rotation, and removal.
CaseBender stores these controls once and mirrors only the required compatibility values for older ingestion consumers. Secret fields never appear in Automation or Advanced.

​
Best Practices

​
Setting up integrations

  • Choose names that identify the environment and tenant.
  • Use guided connector setup when it is available for new workflow automations.
  • Keep custom private-host access as narrow as possible.
  • Use Manage to disable unused connections without deleting audit history.

​
Security Considerations

  • Never paste secrets into endpoint settings or workflow inputs.
  • Use organization-scoped connections unless platform-wide access is required.
  • Rotate or revoke credentials from the advanced vault.
  • Monitor failures from the Health tab.

​
Maintenance

  • Regularly verify integration status
  • Update configurations as needed
  • Monitor performance metrics
  • Keep documentation current