Lucca connector

Use your Lucca data for reporting, automation and AI.

Data Panda pulls your Lucca employee files, leave requests, time entries, expense reports and payroll runs into the same warehouse as your finance, sales and operations data. From one place we turn it into dashboards, automations, AI workflows and custom apps that HR, finance and team leads use during the month, not only when a payroll close or quarterly review forces the issue.

About Lucca

The modular HRIS built à la carte, for companies that want HR software written for the people who use it.

Lucca was founded in 2002 in Paris by Gilles Satgé and ran independently for two decades before partnering with One Peak in 2022. The company sits on roughly 800 employees today, with offices in Paris, Nantes and Marseille and subsidiaries in Switzerland, Spain and Germany. Public reporting puts the install base above 7,000 customers and the active-user count above one million people across more than a hundred countries, with logos including Deezer, Michel et Augustin, Le Roy Logistics and JobTeaser.

Lucca's product is a suite of modules sold à la carte rather than one monolithic HRIS: Poplee for the core people record, performance and engagement; Timmi for time-off, timesheet, project time and office presence; Cleemy for expense reports and procurement; Pagga for payslip distribution, salary and meal vouchers; Figgo for leave; and Bloom at Work for engagement surveys, which joined the group in 2021. Customers buy the pieces they need and bolt the rest of the suite on as the organisation grows, which is why Lucca shows up on stacks where BambooHR or HiBob would otherwise be the default. Pulled into a warehouse next to a French payroll engine, an accounting tool like Sage or Exact, and a CRM like HubSpot or Salesforce, the Lucca record finally answers the questions a Cleemy export or a Timmi report alone does not: real cost of an FTE per entity and country, expense-policy drift between Paris and Madrid offices, or whether the absence concentration in one team is the early signal behind the leavers showing up in the next quarter's headcount.

What your Lucca data is for

What you get once Lucca is connected.

HR and workforce reporting

Headcount, leave, expenses, time and engagement on one page across every entity and country.

Headcount and FTE per entity, department and country, against the approved plan
Cleemy expense burn per category, cost centre and policy band, with the cases past policy named
Timmi leave and absence concentration per team, projected on delivery capacity

Process automation

Turn Lucca joiner, mover, leaver, leave and expense events into the downstream work the rest of the stack expects, without a per-tool handoff.

Provision identity and SaaS access the day a Poplee joiner record posts
Push Cleemy approved expenses and Pagga payroll output into the GL per entity
Free SaaS seats and revoke access the moment a Poplee leaver record posts

AI workflows

Put the Lucca people record, Bloom engagement signals and Timmi absence patterns behind AI that reads the full workforce picture.

Attrition-risk scoring on Bloom-trend, absence-pattern and tenure signals together
Expense-anomaly detection on Cleemy submissions, scored per category and submitter
Natural-language Q&A across the people record, leave register and expense ledger

Custom apps on your data

Lightweight tools on Lucca data for managers and BU heads who should not need a Poplee seat to read their own team.

Manager workbench with team headcount, planned leave, expense burn and Bloom trend
Group-finance cockpit with payroll cost per entity and expense variance per country
Onboarding tracker with the Poplee steps that consistently slip in each office

Use cases

Use cases we deliver with Lucca data.

A list of concrete reports, automations and AI features we have built on Lucca data. Pick the one that matches your situation.

Headcount-versus-planActive and pending hires against the approved plan per entity, BU and country.

Time-to-fully-onboardedDays from Poplee joiner start to onboarding workflow complete, per role and office.

Cleemy expense-policy driftExpense submissions per category and country plotted against policy bands and approval lead time.

Timmi leave-versus-capacityApproved Figgo and Timmi leave per team and country, projected on delivery and revenue capacity.

Bloom engagement-versus-attritionBloom at Work engagement trend per team plotted against actual leaver patterns.

Pagga payroll cost per entityPayslip cost per worker, entity and cost centre, reconciled with the GL and the Poplee record.

Project time profitabilityTimmi Project hours plotted against billable revenue and cost per project, per team.

First-year attrition by officeVoluntary leavers within twelve months of hire, per office, manager and cohort.

Open-role agingReqs open past their target start date, per hiring manager, office and BU.

Performance review throughputPoplee Performance cycle progress against plan, per manager, BU and country.

Document and policy coverageRequired Poplee documents in place per worker and country, with the gaps named.

Office-presence patternsTimmi Office check-in patterns per site and team, joined to leave and project time.

Real business questions

Answers you will finally get.

Where is Cleemy expense policy drifting before group audit picks it up?

Cleemy submissions per category, country and submitter plotted against the policy bands and approval lead time, with the cases above band counted. The CFO sees the office where the meal-and-entertainment line in Madrid is running fifteen percent above policy while Paris and Lyon still sit in band, four months before the next group audit cycle would have picked the pattern up.

Are Timmi absences concentrating in the same team that is about to lose two engineers?

Timmi absence rate per team and quarter joined to actual leaver records over the following two quarters. Group HR sees the teams whose absence rate climbed before the resignations posted, and which offices carry the absence concentration this quarter, instead of treating absence as a leave-balance line and the leaver report as a separate document.

What does an FTE in our Madrid entity cost, including Pagga payroll, Cleemy expenses and Timmi leave?

Pagga payroll cost per worker and entity, joined to Cleemy expense burn and Timmi paid-leave equivalents, rolled up to a fully-loaded cost per FTE per country and cost centre. Group finance sees that the loaded cost per engineer in Madrid is running closer to the Paris band than the local headline salary suggests, before the next budgeting round prices out a planned hiring wave.

Value for everyone in the organisation

Where each function gets value.

For finance leaders

Pagga payroll cost per entity and country, Cleemy approved expenses and Timmi paid leave lined up with the GL and the headcount plan. Group close stops waiting on a payroll export and an expense file per entity, and the personnel-cost line on the management report ties back to the Lucca record it came from.

For sales leaders

Quota coverage against the staffed seller roster from Poplee, with Timmi planned leave windows on the same calendar. Sales leadership sees when DACH mid-market falls below coverage because two AE roles slipped past their target start, or because three senior reps stack their summer leave in the same week.

For operations

Joiner onboarding state, planned leave and headcount across offices in one capacity picture. The COO sees which office is letting joiners drift past day-thirty without finishing onboarding in Poplee and which sites carry the absence concentration in Timmi this quarter.

Ideas

What you can automate with Lucca.

Pair with Slack

Drive joiner, leaver and approval Slack moments from the Lucca timeline

Poplee joiner records post a welcome message on day one in the team channel and ping the manager when an onboarding step has been waiting longer than the agreed window, per office. Cleemy expense reports past their approval-lead-time SLA ping the approver in their personal channel, and Timmi leave requests sitting unanswered before the policy window closes ping the manager. People ops and finance stop running a weekly chase queue across HR, IT and approvers by hand.

Pair with Exact Online

Reconcile Pagga payroll and Cleemy expenses with Exact Online per entity

Pagga payroll output per worker and entity, plus Cleemy approved expenses per cost centre, post into Exact Online on the same accounting key the rest of the GL uses. Group finance closes the month without waiting on a payroll export and an expense file per country, and the personnel-cost line on the management report ties back to the Lucca record it came from. The cases where a Cleemy approval landed after the Exact period closed are listed by name, not absorbed into a generic accrual.

Pair with HubSpot

Match HubSpot pipeline coverage to the Poplee-staffed sales roster

Active sellers, ramp dates and territory assignments from Poplee keep the HubSpot pipeline-coverage view in sync with the staffed sales team per region. Revenue leaders see when the Benelux mid-market segment drops below coverage because two BDR roles slipped past their target start in Poplee, or because Timmi shows three senior reps stacking summer leave in the same week. The HubSpot seat cost stops being a flat line and becomes a number per rep that carries against the pipeline they own.

Pair with HiBob

Run group HR on Lucca and HiBob without picking one master record

Some groups end up with Lucca for the French entities and HiBob for the UK and EU scale-up entities after an acquisition or a regional rollout. The two systems each hold one half of the group; the warehouse holds both. Lucca Poplee, Timmi and Pagga records land next to HiBob people, time-off and Pento payroll on a shared employee key per entity, so group HR sees one headcount-versus-plan view, one time-off calendar, one payroll cost per entity, instead of running two HRIS reports and reconciling them in a sheet.

Pair with monday.com

Plan project work on monday.com against Timmi capacity per team

Timmi Project hours and approved leave per team flow into the same view as the monday.com project board, so delivery leads see when an upcoming sprint runs into a week where two senior people are out and a third is at eighty percent on another project. Resource conflicts that used to surface on the Friday stand-up surface on the planning page when the work is being scheduled, and the project-margin view ties Timmi hours to the monday.com task they were booked against.

Pair with Calendly

Block Calendly availability from Timmi leave and Poplee onboarding state

Approved Timmi leave and Poplee onboarding windows write back to Calendly availability, so a customer cannot book a slot with an account manager who is on holiday next week or a Customer Success engineer whose first day is still a fortnight away. Recruiters and CS leads stop maintaining two calendars by hand, and the slot a prospect picks lands on a person who is working that day.

Your existing tools

Your data lands in a warehouse. Your BI tools read from it.

You keep the reporting tool you already have. We connect it to the warehouse where your Lucca data lives.

Power BI Microsoft

Fabric Microsoft

Snowflake Data warehouse

BigQuery Google

Tableau Visualisation

Excel Sheets & pivots

Three steps

From Lucca to answers in three steps.

Connect securely

OAuth authentication. Read-only by default. We sign a DPA and your admin keeps the keys.

Land in your warehouse

Data flows into your warehouse on your schedule. Near real time or nightly, your call. You own the data.

Reporting, automation, AI

We build the first dashboard, workflow or AI feature with you, then hand over the keys. Or we stay on for ongoing delivery.

Two ways to work with us

Pick the track that fits how you work.

Track 01

Self-serve

We set up the foundation. Your team builds on top.

Lucca connector configured and running
Warehouse set up in your cloud account
Clean access for your Power BI, Fabric or Tableau team
Documentation on what's in the data model
Sync monitoring so you're warned before reports break

Best fit Teams that already have a BI analyst or data engineer and want to own the build.

Track 02

Done for you

We build the whole thing, end to end.

Everything in Self-serve
Dashboards built to the questions your team actually asks
Automations between your systems
AI workflows scoped to real tasks your team runs
Custom apps where a dashboard does not cut it
Ongoing delivery at a pace that fits your team

Best fit Teams without in-house BI or dev capacity. You tell us what you need and we deliver it.

Before you book

Frequently asked questions.

Who owns the data?

You do. It lands in your warehouse, on your cloud account. We don't resell or aggregate it. If you stop working with us, the warehouse stays yours and keeps running.

How fresh is the data?

Near real time for most operational systems. For heavier sources we schedule hourly or nightly. You pick based on what the reports need.

Do I need a warehouse already?

No. If you don't have one, we help you pick one and set it up as part of the first delivery. Common starting points are Snowflake, Microsoft Fabric, or a small Postgres start.

Which Lucca tables land in the warehouse?

The connector pulls the Poplee people register with custom fields, departments and offices, Timmi leave requests, types and policies, Timmi project and timesheet entries where licensed, Cleemy expense reports with categories and approvals, and Pagga payslip metadata where the payroll module is enabled. Bloom at Work survey results land where the engagement module is in use. Authentication runs through a Lucca service-user API token scoped to your tenant.

Do we need every Lucca module to make this useful?

No. Lucca is sold à la carte and the connector reads what you have licensed. A customer running only Poplee and Timmi gets the headcount, onboarding and leave-versus-capacity dashboards on day one; adding Cleemy lights up the expense-policy drift view, and adding Pagga and Bloom at Work fills out the loaded-cost-per-FTE and engagement-versus-attrition cuts. Each module added expands the joins available across the warehouse, without forcing a re-platform of the existing pieces.

How are Pagga payroll and other sensitive Lucca fields handled?

Salary, social-security equivalents and Pagga payslip detail can be kept in restricted schemas that only HR, finance and reward roles reach, while the directory, headcount, leave and onboarding data powers the dashboards the rest of the business uses. Access is enforced in the warehouse, not in each dashboard, so a new operations report cannot accidentally surface a Pagga line it should not see.

GDPR-compliant

Data stays in the EU

You own the warehouse

A first deliverable live in four to six weeks.

We review your Lucca setup and the systems around it. Together we pick the first thing worth building.

Book a call See our other connectors