Skip to content

No webhooks or event stream for CRM changes #16

Open

Description

@mamigot

What the CRM needs

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

  1. added
    api-gapNeeds a platform/CRM API endpoint that does not exist today
    on Sep 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    api-gapNeeds a platform/CRM API endpoint that does not exist today

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions