Help Articles – Page 2
Yes. Core dna provides a documented REST API for integrating our content and commerce platform with your existing software, alongside a webhooks engine for real-time, event-driven updates.
On top of that, Core dna offers hundreds of prebuilt native integrations — SAP, Salesforce, Oracle, Stripe, HubSpot and more — so you can connect legacy systems, run file transfers, or build against the latest API technology. If a system has an API, Core dna can integrate with it.
Reach for a webhook when you need to act the instant something happens and don't want to keep asking — an order placed, a payment processed, inventory changed. The event pushes the data to you automatically, which is lighter on resources than repeatedly polling an API.
Reach for an API when your system needs to control the timing — pulling a product catalog on a schedule, syncing customer records, or running a query on demand. Many teams use both, and Core dna's content and commerce platform supports each pattern across its native integrations.
Yes, and in practice most integrations do. A common pattern is to let a webhook notify your system the moment an event occurs — say, a new order — and then use an API call to pull the full order record or push an update back to another system. The webhook handles the real-time trigger; the API handles the on-demand data exchange.
Core dna is built for exactly this. Our platform pairs a documented REST API with a webhooks engine, so you can react to events in real time and query or sync data on your own schedule from the same integration.
No — though they're closely related. An API (application programming interface) is a two-way channel: your system sends a request and gets a response, so you control when data moves. A webhook is one-way and event-driven: the moment something happens — an order is placed, a payment clears — the source app automatically pushes the data to a URL you specify, with no request needed.
The simplest way to think about it: with an API you ask for data; with a webhook the data comes to you. Core dna provides both a REST API and a webhooks engine, so you can use whichever fits the job.
The same Core dna MCP works with ChatGPT, Claude, Gemini, Copilot, and Cursor. Connect whichever your team already uses.
Yes. Once connected, ChatGPT can update pages, refresh content, fix SEO, and manage your existing Core dna site through conversation.
Not for everyday work. The person who wants a change makes it by describing it. Developers get their time back for what genuinely needs engineering.
Always. Changes land as drafts on your real Core dna site, so you can fine-tune them in the editor, ask for more changes, or roll back, all before publishing.
Yes. ChatGPT acts inside your roles and permissions, every change lands as a draft for approval, and everything is versioned and logged. You can preview, diff, and roll back before anything goes live.
Add Core dna as a connector in ChatGPT, then authorize it with your existing Core dna login. ChatGPT's setup has a few more steps than Claude's (you turn on developer mode and add the connector), but it's all clicks, no code.
Want the exact steps? See the full setup guide.
The same Core dna MCP works with Claude, ChatGPT, Gemini, Copilot, and Cursor. Connect whichever your team already uses.