Build on Digize
Digize gives a small business a CRM, sites and a store, messaging, automations, ads, analytics and reviews in one workspace. Developers meet it in three places: the sites they deploy, the public API, and the webhooks that tell their own systems what happened.
Everything runs on Digize’s Cloudflare account. You don’t need a Cloudflare account of your own, and there’s nothing to set up there.
Each site in a workspace is a Cloudflare Worker that Digize builds and hosts. You push code to the site’s git repository; Digize installs and builds it, uploads it, and puts the new version live. A site answers at <name>.yourfreesite.com and on any of the workspace’s own domains.
A site can be static files, a framework’s build (Astro, Vite, SvelteKit, Nuxt, Next.js and others), or a Worker of your own with KV, D1, R2, queues and Durable Objects declared in its wrangler.jsonc. It reaches the rest of the workspace through the platform paths: form posts become CRM contacts and start automations, and a storefront reads the catalog and starts checkouts without ever holding a key.
The public API
Section titled “The public API”https://digize.com/api/v1 has the workspace’s data and actions, the same ones the app and its agent use: contacts, orders, products, invoices, sites, deployments and the rest. Calls are made with a workspace API key that carries read or write access module by module. The whole API is described by an OpenAPI 3.1 document, which the reference here is built from.
Webhooks and Zapier
Section titled “Webhooks and Zapier”When something happens in a workspace, such as an order being paid or an invoice sent, Digize posts the event to the endpoints that asked for it, signed with each endpoint’s secret and tried again with backoff when the endpoint doesn’t take it. The Zapier app is built on the same events and the public API.