Blog

Connector Hub: the integration layer I build for Drupal

I build Connector Hub so I don't have to solve the same problem over and over.

Here's what it is, why I started it, and where it's heading.


Header met pictogram van verbonden knooppunten

I like structure and overview.
Connector Hub is what happens when you apply that to the way Drupal talks to external systems.

It's a module I build myself, alongside my day job, as a solid foundation other developers can build on.
Here's what it is, why I started it, and where it's heading.

The same problem, solved over and over

Connecting a payment provider, talking to a CRM, handling a webhook from Slack: a different API every time, but the same underlying questions every time.

How do you store a secret key safely and what happens when a request fails?
How do you stop the same webhook being processed twice?

On projects I saw these questions come up again and again, answered afresh each time, sometimes well, sometimes only half.
Connector Hub is my answer to that: a layer that solves this once, properly, so a specific integration only needs to know the protocol of that one system.

What Connector Hub actually does

At its core is a ConnectorEndpoint: a configuration entity per external connection, with a plugin for the protocol and a secret key that runs through the Key module, never directly in the configuration.

Outgoing work runs through a queue, so a slow or temporarily unreachable external service never slows down the rest of the site.
On the incoming side there's a secured, generic webhook route, with rate limiting and verification via HMAC or a bearer token.

Persoon verbindt meerdere knooppunten met een centraal punt

A health dashboard shows the latest successful and failed attempt for each connection, and appears automatically based on what you've actually got installed.

I build this deliberately as a solid foundation for other developers: adding your own integration only needs a small plugin for that specific protocol, not a repeat of everything Connector Hub already handles.

From core to a family of modules

When Google needed the same OAuth2 mechanism as the payment providers, authentication became a separate module.
When both Slack and an AI text generator needed a way to notify a human, that became its own notification layer.

Only on a second, genuine case do I pull something out as a separate module, never in advance.

A more recent extension: AI agents that can't just act on their own

The newest addition, from mid-November, is a layer that exposes connector functionality to AI agents.
Every action falls into one of three categories, from freely allowed to strictly controlled.

Read

Always allowed automatically: looking up a status or fetching data, without changing anything.

Write

Also automatic, but logged: creating a record or updating a status.

Approval needed

Never automatic: a refund through a payment provider is the clearest example.

Where this is heading

Connector Hub has been on drupal.org since 26 October 2026 as version 1.0.0-alpha1, installable via Composer for Drupal 10.3 or higher.
It's alpha, not yet covered by Drupal's own security advisory policy, and I say so myself: use it at your own risk.

The roadmap looks beyond payments and Google, towards CRM, ERP and PEPPOL, the European standard for electronic invoicing that's increasingly mandatory in government and business contexts.

This article is the first in a series: later instalments go deeper into specific integrations and technical decisions from this family of modules.
Together with Smart 404, you will also find Connector Hub on my contributions.

I'm also actively looking for co-maintainers: anyone who wants to help review issues or pick up a piece of the roadmap can get in touch via the project page on drupal.org.
Full documentation and background are at connector-hub.porschmann.be.

I apply that same architectural thinking, building a system cleanly instead of stacking layer on layer, for clients too, through technical management and consultancy.

Curious how this works behind the scenes, or working on something similar yourself?
Send your question via the contact form and I'll get back to you within 24 hours.

Frequently asked questions

What exactly is Connector Hub?

A Drupal module that provides a reusable foundation for talking to external systems: payment providers, Slack, Google and more.
Instead of solving the same underlying problems again for every integration, Connector Hub handles that once, with only a small plugin per system for its specific protocol.

Is Connector Hub stable enough to use yet?

It's listed as alpha on drupal.org, so not yet covered by Drupal's own security advisory policy.
The core module and the first integrations are tested and in use, but I'd advise against putting this into a critical production environment blindly, without checking it yourself first.

Which systems can I connect with it today?

Payments via Mollie, Stripe, MultiSafepay or Buckaroo, Slack notifications and slash commands, Google sign-in and calendar, and AI text generation via OpenAI or Anthropic.
Adyen, additional Google services and integrations beyond payments are on the roadmap.

Can I help contribute to Connector Hub?

Yes, I'm actively looking for co-maintainers.
Anyone who wants to help review issues or pick up a piece of the roadmap can get in touch via the project page on drupal.org.

Question about Connector Hub or a similar project?

Briefly describe what you're working on, and I'll think it through with you.

Privacy policy
You can read how I handle your data in the privacy policy.

More to read