Frequently asked questions
Morpht has integration experience across a wide range of third-party services. Key partnerships include Recombee (content recommendations), Sajari (AI-powered site search), and NLP Cloud (AI content augmentation). Morpht also integrates Drupal with CRM systems, government analytics tools (Google Tag Manager, Google Analytics 4), webform-to-CRM pipelines, mapping services (Leaflet, GeoJSON), and email/notification systems. For GovCMS SaaS sites, integrations must comply with the platform's constraints, but Morpht has deep experience delivering creative solutions within these boundaries.
Yes. Drupal's RESTful API architecture and extensive contributed module ecosystem make it straightforward to integrate with CRMs (Salesforce, Microsoft Dynamics), marketing automation platforms, data analytics systems, and content delivery networks. Morpht has experience implementing webform-to-CRM integrations, Google DataLayer configuration for marketing analytics, and progressively decoupled architectures where Drupal serves as the content backend for React-based front-end applications. These integrations make Drupal a central hub in a composable digital architecture rather than a siloed website platform.
Morpht works with a curated set of enterprise hosting providers. For GovCMS clients, hosting is on the GovCMS platform managed by the Department of Finance. For enterprise and state government clients, Morpht is a Pantheon Platinum Partner (Pantheon is a leading Drupal/WordPress hosting and WebOps provider) and works with Acquia (a leading Drupal cloud platform). This focused approach means Morpht's team has deep expertise in each platform's deployment, caching, and monitoring capabilities rather than spreading thin across many providers.
CRMs (Salesforce and others), identity providers/single sign-on, payment platforms (e.g. NSW's Customer Payment Platform), marketing automation, recommendation/personalisation engines, analytics and tag management, and data/BI visualisation tools. Drupal's API-first architecture (JSON:API, GraphQL) generally makes these integrations more straightforward than with simpler CMS platforms.
Yes. SaaS's shared, managed nature limits the custom code and direct system access available for bespoke integrations, while PaaS gives you the environment access needed for deeper, custom-built integrations. If a project's core requirement is a complex integration, that alone can be the deciding factor for SaaS vs PaaS.
Underestimating the "glue" work: authentication, error handling, data mapping between systems with different data models, and ongoing maintenance as the external system's API changes over time. A well-scoped integration project accounts for this ongoing maintenance cost, not just the initial connection.
Insights