Skode CRM

Versioned API at crmserver.skode.ai/api/v1: enquiries (+ notes), deals (+ won/lost), contacts, companies, tasks, and meetings (free times, booking, cancel). sk_crm_ keys from Settings → Integrations → Developer, with a read/write scope per module; 300 calls a minute per key with X-RateLimit headers; Idempotency-Key on creates; OpenAPI 3.1 at /api/v1/openapi.json and a reference at crm.skode.ai/developers/api. Rolling out to organisations now. Invoices, quotes, payments and products are not in v1 yet.

Token-authenticated bulk lead create + import status polling.

Author code that runs on create/update/stage-change. Today: declarative automation rules only; an ad-hoc Skript runner exists but cannot be bound to an event, stored or versioned.

Custom panels/buttons on the record detail, list view and related lists. The placement catalog and bridge are specified; the host is not shipped.

Rules on page/field/button events in the CRM UI. v1 will be declarative (setRequired/setVisible/setValue/message/block); third-party JavaScript in the product page is not offered.

enquiry/contact/company created·updated·deleted, deal created·updated·stage_changed·won·lost·deleted, task created·updated·completed·deleted, meeting booked·cancelled — the record as the API returns it. Skode-Signature HMAC (t=…,v1=…), retries after 1/2/4/8/16 min, switched off after 10 failed events in a row (or at once on 410), delivery log, replay and secret rotation. Rolling out with API v1. Zapier and other built-in integrations use the CRM’s own older webhooks.

Grants tokens to ChatGPT/Claude/Zapier; consumes HubSpot/Salesforce/Pipedrive/Meta. Scopes are currently read/write only, with long-lived non-rotating tokens — least-privilege grants for extensions are pending.

Streamable HTTP MCP with PII masking, OAuth dynamic client registration and OpenAPI for GPT Actions. Read/write leads, deals, tasks, analytics, search. The tool list is first-party.

Add fields (text/select/lookup/rollup/formula/…) with an approval workflow; schema.updated events. Custom fields flow into filters and the AI schema tools.

Define entirely new record types beyond the fixed module set. The module list is currently first-party and code-defined.