Integrations: administrator view
The administrator overview of integrations: the hub, credentials kept in an encrypted vault, outbound webhooks and the connector marketplace.
Integrations connect the CRM to the rest of the company tools. As administrator, you decide what to turn on, store the credentials securely and control the flow of data outward. This article gives the overview; each integration has its own detailed article.
The integrations hub
In Settings → Integrations sits the central hub. Each integration starts out inert: nothing happens until you configure and enable it. The philosophy is "ready and off": the connector is available, but only comes into action when you provide the credentials and flip the switch.
Credentials in an encrypted vault
The credentials you enter (tokens, API keys, OAuth secrets) are stored encrypted in the secrets vault. They do not appear in clear text after being saved and are not exposed to regular users. BYO model ("bring your own"): in many integrations you use your own organization app, so we never see your credentials.
Outbound webhooks
In Settings → Webhooks you make the CRM notify other systems in real time: on each event (record created or updated) we send a JSON POST to the URL you register, signed with HMAC so the destination can verify authenticity. It is the bridge to Zapier, Make or your own back end.
API and access keys
For custom integrations, Settings → API exposes the programmatic access keys. Generate one key per integration (never share the same one across systems), give it the smallest scope needed and revoke it as soon as it is no longer used.
Connector marketplace
The marketplace gathers the ready-made connectors. Billing models vary: some use your own account with the service (you bring the key), others are metered by the platform. The default stays conservative: a connector only costs when it is actually enabled and used.