Skip to content

Integrations

Outgoing webhooks, Slack and SMTP, with credentials encrypted at rest.

Integrations connect a workspace to systems you already run. Each provider declares its own configuration, and anything secret is encrypted before it is stored.

Available today

ProviderWhat it does
WebhookPosts events to a URL you control, optionally signed.
SlackPosts to an incoming webhook.
SMTPSends mail through your own server.
ZapierUses a workspace API key rather than its own credential.

Google Sheets and HubSpot appear in the catalogue marked as coming, and cannot be connected.

How credentials are handled

  • Secrets are encrypted with AES-256-GCM before they are written, using a key derived from the application secret.
  • No route ever returns a decrypted secret. The interface shows that one is configured and offers to replace it.
  • Test requests run server-side, with a timeout, and refuse private, loopback and link-local addresses at every redirect hop.

Looking for API keys?

Workspace API keys live under Developer → API keys and are documented in API authentication.