Custom Directus Extensions: Development & Integration

When integrating Directus into corporate infrastructure, syncing with accounting systems like 1C, CRM, or warehouse databases often becomes necessary. Standard REST and GraphQL APIs don't always cover specific business logic—custom event handlers, endpoints, or complex validation are required. That's where custom Directus extensions come in: they extend functionality without modifying the core. A typical example: when an order is created, we need to send data to CRM, generate a PDF invoice, and log the record. A Hook extension handles this in a few lines of TypeScript, while an Operation in Flows triggers the action chain.

We've been developing custom Directus extensions for 5+ years, delivering 30+ solutions for 1C synchronization, PDF report generation, and Telegram bot integration. All extensions are written in TypeScript using the official SDK.

Custom Directus Extensions: Types and Code Examples

Extension Types

Custom vs. Ready-Made Plugins

How Hook Extensions Sync Data in Real Time?

Hook extensions subscribe to action (after change) or filter (before save) events. A classic case: on order creation, send data to CRM. The handler code looks like this:

// extensions/hooks/lifecycle-events/index.ts
import type { HookExtensionContext } from '@directus/types'
export default ({ action, filter, schedule, init }: HookExtensionContext) => {
  action('items.create', async ({ collection, item, accountability }) => {
    if (collection === 'orders') {
      await fetch(process.env.CRM_WEBHOOK!, {
        method: 'POST',
        headers: { 'Content-Type': 'application/json' },
        body: JSON.stringify({ event: 'order_created', orderId: item.id, total: item.total })
      })
    }
  })
}

We add error handling and retry logic for robustness. For example, on a recent project with a retailer, we reduced order processing time from 8 seconds to 1.2 seconds by offloading CRM sync to an async Hook with retry and deduplication.

What Is an Endpoint Extension and How to Create One?

Endpoint extensions allow you to add custom Express routes. For instance, a sales report with date filtering:

// extensions/endpoints/reports/index.ts
import type { EndpointExtensionContext } from '@directus/types'
import { Router } from 'express'
export default (router: Router, { services, getSchema }: EndpointExtensionContext) => {
  router.get('/sales', async (req, res) => {
    const schema = await getSchema()
    const { ItemsService } = services
    const ordersService = new ItemsService('orders', { schema, accountability: req.accountability })
    const orders = await ordersService.readByQuery({ filter: { status: { _eq: 'completed' } }, fields: ['id', 'total', 'date_created'] })
    const totalRevenue = orders.reduce((sum, o) => sum + (o.total || 0), 0)
    res.json({ totalOrders: orders.length, totalRevenue })
  })
}

We routinely add pagination, sorting, and caching. All endpoints undergo load testing.

How Operation Extensions Automate Business Processes?

Operation extensions are used in Flows. They consist of two files: server logic and a UI for the Flow builder.

// extensions/operations/send-sms/index.ts (server)
export default {
  id: 'send-sms',
  handler: async ({ phone, message }, context) => {
    const response = await fetch('https://api.sms-provider.com/send', {
      method: 'POST',
      headers: { Authorization: `Bearer ${process.env.SMS_API_KEY}` },
      body: JSON.stringify({ to: phone, text: message })
    })
    if (!response.ok) throw new Error('SMS failed')
    return { sent: true }
  }
}

// extensions/operations/send-sms/app.ts (UI)
export default {
  id: 'send-sms', name: 'Send SMS', icon: 'sms',
  description: 'Send SMS via provider',
  options: [
    { field: 'phone', type: 'string', meta: { interface: 'input', required: true } },
    { field: 'message', type: 'text', meta: { interface: 'input-multiline', required: true } }
  ]
}

Why Custom Extensions Outperform Ready-Made Plugins?

Ready-made plugins often miss the mark: they're either bloated or lacking functionality. Custom extensions are written precisely for the task. For example, a Hook can not only send data to CRM but also check for duplicates, while an Endpoint can generate complex filtered reports. You get exactly what you need, no dead code.

Our projects show that custom solutions cut integration time by an average of 40% compared to customizing ready-made plugins. Moreover, the risk of update failures drops by 60%. For common scenarios, we have ready templates—contact us to get them.

Turnkey Extension Development Stages

1. Requirements analysis (1 day) — client interview, identify integration points and data formats.
2. Prototype (1 day) — create a Hook skeleton and test endpoint, agree on API.
3. Development (1–3 days) — code, unit tests, integration with external services.
4. Staging (1 day) — deploy to test environment, verify with real data.
5. Documentation (0.5 day) — detailed README, installation and configuration guide.

extensions/
├── hooks/sync-to-crm/
│   ├── index.ts
│   └── package.json
├── endpoints/reports/
│   ├── index.ts
│   └── package.json

What's Included in Custom Extension Development

• Source code in your repository (TypeScript, commented).
• Installation, configuration, and usage documentation.
• Testing in a staging environment.
• One-month bug fix warranty.
• Consultation on integration and ongoing support.

Timelines and Estimated Cost

Developing a single extension (Hook or Endpoint) takes 2 to 4 days. A comprehensive set of three extensions (Hook + Endpoint + Operation) takes 3–5 days. The cost is calculated individually based on complexity. Contact us for a precise estimate.

Order custom extension development and get a turnkey solution with documentation and warranty.

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.