Notifications
Integrations and notifications
Send the right deployment, file transfer, and workspace events to the places your team already watches.
What integrations do
Integrations connect deployment, file transfer, and workspace events to the places your team already watches. They reduce silent failures by routing high-signal events to Slack, Discord, Telegram, webhooks, SMS, or other configured destinations.
Before connecting integrations
- Decide which events deserve notifications.
- Pick the destination that the responsible team actually monitors.
- Confirm the workspace plan allows the integration.
- Avoid sending every low-value event to every channel.
Typical workflow
- Connect the integration provider.
- Validate the destination where the provider supports a test.
- Choose site or workspace notification settings.
- Trigger a safe event and confirm delivery.
- Review delivery behaviour after the first production deployment or transfer.
Checks before relying on notifications
- Deployment success and failure routes are configured.
- File-transfer failures go to someone who can act.
- Webhooks are signed or protected where needed.
- Billing and workspace notices reach the owner.
- Team members know where notification settings live.
Common issues
- Notifications go only to the person who created the resource.
- A destination is connected but not selected for the site.
- A noisy channel causes the team to ignore important failures.
- A webhook endpoint changes and deliveries start failing silently.