Integrations
Connect Kadryn to collaboration and activation destinations without mixing product integrations with developer setup.
What this menu is for
Integrations connects Kadryn signals to the tools where teams coordinate and act. Today, the primary surfaces are Slack and Activation.
Use this menu to connect Slack, choose the default destination, verify delivery status, and turn product signals into review and follow-up workflows.
What belongs elsewhere
Technical API setup belongs in Developer tools. Provider credentials belong in Provider Keys. Subscription limits belong in Billing.
This separation matters for security: product integrations should not expose provider secrets, API keys, webhook signing secrets, or low-level gateway diagnostics.
Tabs
- Slack: connect the workspace, verify channel routing, review connection status, and reconnect when the Slack workspace changes authorization.
- Activation: use connected destinations to route reviews, alerts, digests, and follow-up actions.
Recommended workflow
- Connect Slack from an admin account.
- Select a default channel that the right team owns.
- Send or test the relevant notification flow.
- Confirm the delivery result in the product surface that owns it.
- Use Activation to make recurring reviews and follow-ups predictable.
Permissions and plan behavior
Read-only users can inspect status and understand what is missing. Workspace admins manage connections, channels, and activation settings. Some activation workflows can be plan-restricted; locked states are expected and should link to Billing instead of looking like failures.
Reliability expectations
Kadryn should keep Slack connected using secure token refresh and controlled retries when Slack returns recoverable authorization failures. Reconnect only when the Slack installation is revoked, the workspace removes the app, the token cannot be refreshed, or the admin intentionally changes the integration.