Platform overview

What your app can reach, and how the pieces fit.

The surfaces you extend

surfacewhat your package declareswhat the platform does on install
Custom objectsObject + field schemas (15 field types incl. platform-computed formulas, lookups to Leads/Contacts/Companies/Opportunities, validation rules, field-level role ACLs)Creates the objects via the schema builder; an auto-generated CRUD API appears at /api/crm/custom/{apiName}/records
WorkflowsTemplates in the production engine's typed DSL — 16 triggers, 12 actions, true if/else branchingCreates them per tenant (drafts in sandbox installs, active in prod), wired to live event firing, DLQ retries and the audit ledger
WebhooksHTTPS endpoints + platform event namesRegisters outbound subscriptions with retries and a delivery ledger the tenant can inspect
AI agentsBuilder-agent scripts (system prompt + skill names)Creates the agent in the tenant's Agent Builder, subject to their model keys and token budgets
UI extensionsHTTPS links templated with record contextSurfaces them on lead/contact/opportunity detail, dashboard or settings

Identity & isolation

Where requests flow

your code ──▶ https://app.ivorycomcrm.com/api/marketplace/…   (catalog, submissions, installs)
tenant SPA ─▶ https://app.ivorycomcrm.com/api/crm/…           (CRM gateway: leads, custom records, workflows)
platform ──▶ your https endpoints                              (outbound webhooks, signed deliveries)

Categories

sales marketing finance productivity support data