SIGNALS Documentation
API Reference

Integrations

Geocoding, SSO providers, allowed email domains, self-hosted AI embeddings, Stripe payment keys, and Nightwatch monitoring settings.

Overview

Integrations covers third-party credentials: what3words geocoding, Google/Microsoft SSO, allowed email domains, (self-hosted) AI embeddings configuration, Stripe payment keys, and Laravel Nightwatch monitoring.

Where it lives

Route: /admin/settings/integrations (admin.settings.integrations)

Open Admin → Preferences → Integrations. Requires settings.manage.

Sections

Geocoding & SSO

  • what3words API key (masked)
  • Google / Microsoft SSO enable toggles
  • Self-hosted: client ID, write-only client secret, copyable callback URL
  • Allowed email domains (normalised, deduplicated)

On Signals Cloud, SSO credential fields are hidden; toggles and the allow-list remain editable.

AI embeddings (self-hosted)

Enable embeddings, API key, provider/model (openai / gemini / mistral, or openai_compatible for a bring-your-own endpoint), refresh cadence, monthly token budget, usage retention, and pause sync. Choosing openai_compatible swaps the model dropdown for a base URL, model id, and dimensions — point it at Ollama, vLLM, or any OpenAI-compatible server and record text never leaves your network. Changing provider/model while enabled can dispatch a full embedding refresh job.

On Cloud, credentials are platform-managed — see AI embeddings & configuration for behaviour and API details.

Payments

Stripe credentials for customer portal invoice payments: publishable key, secret key, and webhook signing secret. All three are stored encrypted and are write-only — a blank input keeps the stored value, and stored secrets are never rendered back into the form.

Stored keys take precedence over the STRIPE_* environment variables; a blank setting falls back to the Cashier config, so env-configured installs are unaffected. See Document portal & payments.

Monitoring (self-hosted)

Laravel Nightwatch enable toggle, write-only ingest token (encrypted), and request sample rate (0–1). Values override nightwatch.* config at boot when a token is stored.

On Signals Cloud, Nightwatch is provisioned via environment variables — the form is hidden.