Business Process Automation: From Manual Work to Digital Flows

Approval emails, "please fill in the attached Excel and send it back" threads, signature folders circulating around desks: much of the enterprise process landscape in Turkey still revolves around this trio. A purchase request starts as an email, waits in turn across three managers' inboxes, and stalls all week if one of them is on holiday; an expense form is filled in Excel and sent to accounting by email, then keyed into the ERP by hand; a contract is printed for approval, signed, scanned, and returned by email again. The downstream effect: no one can give a clear answer to "who is this request with right now, and how long has it been waiting?" The process is invisible, delays depend on personal reminders, and at audit time who approved what and when is pieced together from scattered emails. When we talk about digital transformation, the first thing we touch on the process side is exactly this: moving work that runs over email and Excel into defined, SLA-tracked, auto-notified digital flows with a full audit trail, on a BPMN-based workflow engine.

Our Approach

On a process automation project we'd spend the first week mapping the current process as it really is, without writing any code. Because in most organisations what is described as "the process" differs from what actually happens: the written procedure says "three approvals", but in practice a WhatsApp message someone sent stands in for an approval, or a "shadow step" that is not in the official flow is the real backbone of the work. So we'd model the process in BPMN 2.0 notation, on a whiteboard together with the business unit, until who approves what, which branch runs under which condition, and where parallel approvals exist all become clear. This diagram becomes both a shared language and a definition that can be loaded directly into the workflow engine; we close the gap between "the documented process" and "the process that actually runs" from the start.

The second critical decision is the choice of workflow engine. If the process is mainly human approvals (purchasing, expenses, leave, contract approval) we'd recommend Camunda; running the BPMN diagram directly, with task inbox and form capabilities, fits this scenario well. If the process is long-lived, multi-step, and needs resilience across systems (flows that run for hours or days and must survive crashes) we'd prefer Temporal; thanks to durable execution the flow resumes from where it left off even if the server restarts. In either case we'd keep process state in PostgreSQL and pending work queues and scheduled triggers in Redis. The point is that the process state lives in a single queryable source of truth, not in an email chain.

The third layer is interface, notification, and SLA. The side the employee sees we'd build as a clean form plus approval panel with Next.js: a personal "task inbox", one-click approve/reject, a justification field, document preview. We define an SLA duration for every step; if no action is taken before the time elapses, automatic escalation kicks in (routing to a higher manager, a deputy approver, a reminder). We orchestrate notifications with n8n: single-point distribution to email, SMS, WhatsApp, or Slack channels. For systems with an API we build direct webhook/REST integration; for legacy applications that only have a screen and no API we'd recommend an RPA bridge with UiPath or Automation Anywhere; we always position RPA as a last resort because it is fragile, trying the API first.

The final layer is legal validity and audit trail. For approved documents we'd recommend qualified e-signature under Law no. 5070 and mobile signature integration where needed, and KEP integration for processes that require official correspondence. Every event, who, when, from which IP, with which document version they approved/rejected, is written to a tamper-evident audit trail; document versions are sealed with a hash. We trace the whole flow end to end with OpenTelemetry and catch errors with Sentry; so the answer to "which approval is getting stuck where" shows up not at audit time but on a live dashboard.

Our Preferred Technology Stack

We typically reach for the following, adapted per project to your process type, existing systems, and compliance requirements.