CMS Integration
A CMS integration connects a content management system with another application, platform, or service.
It allows information or actions to move between otherwise separate systems.
Common CMS Integrations
A CMS may connect with:
- Analytics systems
- Email platforms
- CRMs
- Payment providers
- Ecommerce platforms
- Booking systems
- Search services
- Automation tools
- Social platforms
- Data warehouses
Ghost, for example, supports integrations through embeds, code injection, APIs, webhooks, themes, and automation tools.
How Integrations Work
An integration might use:
- A plugin
- An API
- A webhook
- Embedded code
- A Third-Party Script
- Automation software
- A direct server-to-server connection
The implementation depends on what information needs to move and which system initiates the action.
Integration vs. Plugin
A Plugin extends the CMS itself.
An integration connects the CMS with another system.
Sometimes a plugin provides the integration.
For example:
WooCommerce shipping plugin → connects the CMS/ecommerce platform → to a delivery provider.
The plugin is the technical extension.
The integration is the relationship between the systems.
Why It Matters
Integrations can remove repetitive work.
For example:
New CMS member → CRM record created → welcome workflow triggered
can be more reliable than someone manually copying the information between systems.
But integrations also create dependencies and ownership questions.
Common Problems
Common integration problems include:
- Nobody knowing why an integration exists
- API credentials belonging to former staff
- Duplicate data
- One system overwriting another
- External changes silently breaking the workflow
- Third-Party Scripts affecting Website Performance
- Sensitive information being sent unnecessarily
- Integrations built without documentation
- No fallback when the external service fails
How to Improve
Document:
- Which systems are connected
- Which system owns each piece of data
- What triggers the integration
- What information moves
- Who owns the credentials
- What happens when it fails
An integration should reduce operational complexity rather than hide it.