Agentic Development of Applications and Integrations

An order arrives on the website and somebody retypes it into the warehouse system. Prices change in the ERP and the website is two days behind. A salesperson keeps their own spreadsheet, because the CRM and the website do not talk to each other.

This is not work for a human. I connect Drupal with the rest of your systems so data moves on its own — and so you notice when something gets stuck.

I develop agentically

I write code with AI agents (Claude Code and others). That lets me cover on my own the scope that usually takes a team, and tests or refactoring are not the line item that gets cut for budget. AI proposes; I decide and I am accountable: every change goes through tests and code review. The AI usage page describes exactly how.

What I connect

  • Drupal with ERP and warehouse — products, prices, availability, orders. One-way or two-way synchronization.
  • Drupal with CRM — contacts, form enquiries, communication history.
  • Website with e-commerce and payment gateways — the order flow from cart to invoice.
  • Marketing tools — Mailchimp, Google Analytics, price comparison sites.
  • AI and MCP — connections to OpenAI, Anthropic, or local models over Ollama.

How I build it

  • API development: design and implementation of RESTful APIs, JSON:API, and webhooks.
  • A custom Drupal module when the protocol or data format does not match anything off the shelf.
  • Failure handling: queues, retries, logging, and alerts when the other side stops responding.
  • API security: authentication, authorization, rate limiting, and separated read and write permissions.
  • Documentation: OpenAPI/Swagger, so anyone can pick up where I left off.
  • Automated integration tests, so a silent breakage shows up before your customers report it.

The foundation I build integrations on is released as open source: the Drupal module api_plugins — instead of a separate service per third-party API, you define a plugin and a shared layer handles requests, authentication, and errors.

Custom applications and automation

Not just integrations. When an off-the-shelf tool does not fit, I build a small application or automation for your process:

  • Automating routine work – content publishing, reports, synchronization and scheduled jobs, in code or in n8n
  • Data collection – fetching and processing data from websites and APIs
  • Converting and cleaning data – migrations between systems, removing duplicates, unifying formats and checking data quality before import
  • AI in the process – LLMs where they save work, with limited permissions and a human on the risky steps

Technologies & tools

  • Languages: PHP, Python, Node.js
  • Frameworks: Drupal, Symfony, FastAPI, Express
  • Testing: Postman, Burp Suite
  • Documentation: Swagger

What you get

  • Data flowing on its own, without retyping and typos
  • Current prices and stock levels on the site, not yesterday’s
  • Fewer order errors and fewer complaints
  • Your people freed up for work a machine cannot do

Frequently Asked Questions

Our ERP is old and has no API. Can it still be done?
Usually yes. I have built integrations over the database, over exported files on FTP, and through middleware layered on top of a legacy system.

Will we know when an integration breaks?
Yes, that is part of the job. I set up logging and alerts so the error reports itself instead of waiting for a customer complaint.

Can you connect one part now and the rest later?
Yes. We usually start with a single data flow, verify it in production, and add more from there.

I build applications and integrations that do the routine work for you. Contact me on LinkedIn or use the form below.

Ask for Service →