Google Calendar, CRM connections, and API keys.
Settings → Integrations is where Stynar connects outward — your calendar for meeting booking and your CRM for lead import, with API keys on their own Settings tab right next to it. Every card here shows a clear status at a glance — Connected, Not connected, or Reconnect needed — and it's the one place to manage or reconnect any of these later, even if you first connected from somewhere else in the app.
You'll usually connect this first from the Meetings page itself — this card is the same connection, useful for checking status or reconnecting later without leaving Settings.
If Google access is ever revoked or expires, the card switches to "Reconnect needed" with a status line explaining why — one click restarts the OAuth flow.
Connect a CRM once here, and it becomes available as an import source wherever leads get imported — Saved Lists or the campaign wizard.
| Field | What it means |
|---|---|
| HubSpot | Connect via OAuth, then import contacts directly — no CSV export needed. |
| Zoho CRM | Same OAuth-based connection, for teams running Zoho instead of HubSpot. |
Every account can create API keys — there's nothing to request or turn on. Open Settings → API keys to connect your own apps and scripts to Stynar's API. See the API quickstart for your first request.
The card opens with requests used this month against your monthly limit, plus your per-minute and per-second burst rate.
Give it a name and pick one or more scopes — read (view account & resource data) or write (trigger actions, like starting a campaign).
The full key is shown exactly once, right after creation. Stynar can't recover it later — losing it means creating a new one.
Rename, rotate, or revoke any active key at any time from the same card.
Read and write are independent — grant only what an integration actually needs.
Create one key per integration, up to your account's active-key limit (3 by default), so you can revoke one without breaking the others.
The plaintext key is never shown or stored again after the creation or rotation modal closes.
Rotating issues a new key immediately — the old one stops working the instant you confirm.
Any application still using a revoked key loses access immediately, with no grace period.
No approval step and no plan requirement — every account starts with the same default limits.