Automation Engineer - Meddbase/O365/Egress Integration Pipeline

You'll own the build and delivery of a 5-stage automation pipeline for a private healthcare client, integrated directly into their clinical and administrative stack. This is a 6-week contract engagement covering discovery, build, UAT and go-live, followed by a 30-day hypercare period. The scope is defined, the client relationship is live, and the stack is locked. You'll be embedded with the ivee delivery team and given full ownership of the technical build from day one. The project removes 54 hours of manual administrative work per week from a consultant support team. Every consultant appointment generates a patient letter. Today that letter goes through 10 manual steps before it reaches the patient. You're replacing 9 of them with a single automated pipeline, triggered on consultant approval, integrated into Meddbase, O365 and Egress. The complexity here sits mostly in the API layer, not the automation tooling. Meddbase's public documentation doesn't cover everything you'll need to build against it reliably, so a meaningful part of this role is validating real API behaviour during discovery, rather than assuming the published docs tell the whole story. Key responsibilities - Stress-test Meddbase's actual API behaviour against its published documentation before committing to the technical design - Build a trigger-based PDF generation pipeline that fires on letter approval in Meddbase and renders a formatted output via a templating engine - Build a CC/referrer address lookup that resolves recipient contacts from Meddbase, augmented with internet search - Implement dispatch routing across encrypted paths: Meddbase secure link where no CCs are present, Egress encrypted PDF where CCs are present, plus print handling for cases that need physical post - Build status writeback to Meddbase, replacing the parallel Excel log entirely with a live dashboard - Design and implement an exception queue, with real-time alerts on failures - Run a two-day on-site discovery sprint with the client's consultant support team in Week 1 to lock the spec and edge cases - Deliver UAT with the support team in Week 3 and manage go-live in Week 4 What we're looking for - Real API integration fluency rather than just tool operation: comfortable reading a third-party API's documentation critically, spotting where it's incomplete or doesn't match live behaviour, and testing directly against a real or sandbox account - Proven experience with API integration in regulated or data-sensitive environments - Experience integrating with CRM or practice-management APIs (Salesforce, HubSpot, or similar) in regulated or data-sensitive environments - Hands-on experience with n8n/Make.com - PDF generation and templating experience, e.g. Puppeteer, Playwright/Chromium, or WeasyPrint - O365 and programmatic email/document dispatch experience - Prior work in a CQC-registered or otherwise regulated clinical environment is a plus - GDPR-aware data handling, since you'll be working with patient health records - Enough JavaScript to write expressions and transformations inside automation nodes - Comfortable building basic monitoring and alerting so the pipeline stays visible and debuggable - Meddbase experience is a significant advantage - Egress integration experience is a plus A clear communicator, comfortable working directly with non-technical stakeholders What success looks like - A 10-step manual workflow reduced to 2 human touchpoints - ~54 hours a week returned to the consultant support team - Zero patient letters lost, duplicated, or mis-routed during rollout - An exception queue the team actually uses, not one it works around Engagement details Type: Contract Start: August 2026 Duration: 3 weeks (discovery, build, UAT, go-live), plus 30-day hypercare Location: London, on-site Week 1 and go-live week, remote otherwise Rate: Competitive, based on experience