Service
Integrations & APIs
Integrations with payment processors, CRMs, ERPs, marketing platforms, and partner APIs — webhooks, OAuth flows, queue-backed sync, and enough logging to see what happened when a remote system fails.
The question that comes up on every integration is the same one: did order #4181 actually reach the ERP? We build assuming the other side will be slow, rate-limited or down, which means queues, retries with backoff, idempotent writes, and dead-letter handling where the business flow needs it. The point of all of it is that the answer to that question is something you can look up.
Scope
How the work is delivered
-
Integration design
We map the data contract first: what flows which way, how often, who is the source of truth, what "eventually consistent" means here. Output: a sequence diagram and a list of failure modes, agreed before code.
-
Auth & connectivity
OAuth2, API keys or mutual TLS handled properly, including token refresh, secret rotation and sandbox-to-prod promotion. Webhook endpoints verify signatures and survive replays.
-
Resilient sync
Queue workers between Drupal and the upstream so a slow ERP never freezes a page load; retries with exponential backoff, idempotent writes, and a dead-letter queue for the records that need a human.
-
Common targets
Payment processors, CRMs (Salesforce, HubSpot, Dynamics), ERPs and PIMs, marketing and analytics platforms, shipping and tax services, partner APIs. All of it built on Drupal's queue and HTTP-client stack rather than cron scripts written for one occasion.
-
Observability
Structured logs per integration, success and failure metrics, alerting on backlog growth or error spikes, and an admin view of recent syncs, so support can answer "did order #4181 reach the ERP?" without pulling in a developer.
Recent builds
Where we shipped this
Talk through the build
Send the platform, constraints, and timeline. We'll reply with the engineering questions that decide scope.
- Reply within one business day, weekday hours UA / EU.
- 30-minute discovery call when it is useful.
- Scope written around deliverables, risks, and ownership.