Facelift Hella
Povio × Facelift bbt · Client: HELLA

Facelift Hella: MS Planner integration

Awaiting HELLA confirmation PM: Timi Hraš Target: testable MVP January 2027 As of 17 Nov 2026

Short description

HELLA plans tasks in Microsoft Planner. This integration imports selected Planner tasks into Facelift and links them to existing Frames in the editorial calendar. Planner remains the source of truth. Updates sync one way, Planner to Facelift, by polling, because Planner has no change events. The build follows the Debeka pattern on Facelift's Activepieces workflow engine.

The goal for Facelift is adoption and retention. HELLA's non-social teams can keep working in Planner while their work still appears in Facelift. Facelift has at least three similar sync projects in the pipeline, so this one is set up as a reusable template.

278.5 hEstimate, iteration 2
216 hBack end
33 / 29.5 hPM / Solution architecture
Povio
  • Timi Hraš Project manager
  • Aldin Milanović Solution architect
  • Edo Civic Developer, starts 23 Nov
  • Žiga Triller Account owner
Facelift
  • Maik Rogowski (Maro) Customer success, owns HELLA comms
  • Robert Albrecht Executive sponsor
  • Florian Höft Wrote the client scope
  • Holger, Elias DevOps access
HELLA
  • IT contact Not named yet. Maik introduces after contract.

Timeline

Stage and task
Nov162330Dec7142128Jan4111825
Planning phase
Project timeline, questions and access request for HELLA
18 Nov HELLA call · 20 Nov plan to Maik
Facelift task API exposure
API Gateway task routes
Task operations in the Facelift piece
Change detection and state store
State store
ETag-diff poller
MS Graph connector
Entra app registration and credential
Planner read operations
Resilience against Graph behaviour
Routing and mapping
Routing configuration and resolution
Validation and unmatched reporting
Sync behaviour and lifecycle
Field mapping and task creation
Updates and completion
Deletion and re-routing
Hardening and operations
Failure handling and health checks
Configuration and MVP setup
Testable MVP ≈ 19 Jan
Preparation
Customer inputs and PRD sign-off
Confirm the Planner setup
Polling and throttling validation

Milestones

HELLA input:FullMinimalNone
StageIncludesHELLA inputBEPMSATotal
PreparationConfirm Planner setup · polling and throttling validation · customer inputs and PRD sign-offFullTier, sync scope, cadence, routing rules487661
MS Graph connectorEntra app registration · Planner read operations · resilience against Graph behaviourNoneKnowing the tier speeds it up304.5438.5
Change detection and state storeState store · ETag-diff pollerNone223328
Facelift task API exposureAPI Gateway task routes · task operations in Facelift nodesNone366547
Routing and mappingRouting configuration and resolution · validation and unmatched reportingMinimalPlanner-to-Facelift field mapping223.5328.5
Sync behaviour and lifecycleField mapping and task creation · updates and completion · deletion and re-routingMinimalCadence and lifecycle settings345.5544.5
Hardening and operationsFailure handling and health checks · configuration and go-liveMinimalStaging feedback before production243.53.531
Total2163329.5278.5

Hours from Povio Estimates, read 17 Nov 2026. Input levels follow Aldin's kickoff walkthrough and are tentative until the timeline is shared. QA is not estimated.

Decision log

Agreed decisions first, then open items
IDDateQuestion and decisionAgreed withStatus
D012 JulWhich way does the MVP sync?One way, Planner to Facelift. No reverse sync, comments or permission mapping in the MVP.FaceliftAgreed
D0212 NovHow does Facelift detect Planner changes?Polling with an ETag diff against a state store, because Planner has no change events.InternalAgreed
D0313 NovWhich workflow engine do we build on?Activepieces, replacing n8n. The flow stays the same as Debeka.InternalAgreed
D0413 NovCan we start before HELLA confirms?Yes. Stages that need no HELLA input start now. Only Preparation waits on HELLA.Internal, FaceliftAgreed
D0513 NovHow do we handle the unknown Planner tier?Investigate Basic and Premium in parallel, then switch once HELLA confirms.Internal, FaceliftAgreed
D0613 NovWhat is the delivery target?A testable MVP in January 2027. The December MVP is dropped.FaceliftAgreed
D0713 NovDo we build this for reuse?Yes, as a template for the next sync integrations in Facelift's pipeline.Internal, FaceliftAgreed
D0818 NovHow is the plan scheduled?Aldin's milestone order, back-end hours at 32h a week, development from 23 Nov, no work 24 Dec to 3 Jan.InternalAgreed
O0118 NovDoes HELLA use Planner Basic or Premium?Premium would change the connector estimate. Maik is asking HELLA.Facelift, HELLAOpen
O02Before kickoffDo Planner-owned fields need to be locked in Facelift?The client scope wants them display-only. The estimate does not cover locking.FaceliftOpen, high risk
O0311 DecWhich Frame does each plan, bucket and label route to?Routing rows from HELLA.HELLAOpen
O0411 DecHow do Planner statuses and notes map to Facelift?Status list, how completion maps to it, and whether notes means description or checklist.HELLAOpen
O0511 DecWhat happens to tasks deleted in Planner?Name of the deleted status in Facelift.HELLAOpen
O0618 DecHow often do we poll?1, 5 or 10 minutes, checked against throttling on HELLA's tenant.HELLAOpen