You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A machine-readable signal when records change, so integrations can react: post to Slack when a deal is won, sync people to a mailing tool, mirror deals into a data warehouse.
What exists
Three notification types (CRM_PERSON_CREATED, CRM_DEAL_STAGE_CHANGED, CRM_PERSON_LINKED_TO_USER) delivered to people by email/push, configurable through /iblai-api-notification (iblai-api-crm → references/workflows.md §12). There is nothing for a system to subscribe to, and references/guide.md states the CRM exposes no queues, workers or background-service control plane. The only integration path today is polling every list endpoint — which, without ordering= (#5) or an updated_at__gte filter on every resource, cannot even be incremental.
Proposal
/api/crm/webhooks/ (url, secret, event types) with signed POSTs for person.*, organization.*, deal.* (including deal.stage_changed, deal.won, deal.lost), activity.*; plus updated_at__gte on every list endpoint as the polling fallback.
Activity