
PTO requests, policy questions, pay queries, and onboarding workflows handled in Slack from live Lucca data. No developer. No portal. No HR ticket.
Lucca's own AI works inside the platform. Employees asking questions in Slack get nothing from it.
Slack and Teams show who's out and sync leave status. Employees can't ask questions or submit requests there.
Poplee records the hire. IT access, other app provisioning, and the day-1 checklist are still manual.
Employee asks in Slack. Workativ reads from Lucca, takes the action, and confirms all in the same thread.
Live leave balance read from Lucca's Timmi Absences API
Leave request submitted through Lucca's Figgo approval workflow
Manager approves in Slack Lucca record updated on approvall

Lucca fires the event. Workativ handles Okta, Azure AD, ServiceNow, and Slack. HR sets it up once.
Triggered by new hire event in Lucca's Poplee module no manual kickoff
Okta profile set up with the correct role and group memberships
The checklist reaches the new hire in Slack before their first day begins

“ Our AI Bot Orion has become a critical enabler of employee self‑service. The quality of responses is fast, comprehensive, and highly reliable, allowing employees to find accurate answers without needing to escalate to HR or IT. What really sets Workativ apart is the visibility into question trends, resolution rates, and where AI is genuinely reducing operational workload. ”
Vice President, HR Operations


A no-code builder, agentic RAG, workflow automation, and security all without a separate implementation project.

Lucca leave, payslip, personal updates, and expenses all configured point-and-click
Hands off to a live agent the moment employees need a real HR conversation
Lucca module permissions set by HR, not an implementation consultant
Lucca AI is an opt-in add-on for tasks inside Lucca itself. Workativ brings the same data into Slack and connects Lucca events to your full stack.
What matters to HR | ||
|---|---|---|
Where employees interact | Inside the Lucca platform | |
Submits Leave requests | In-platform task assistance only | |
Updates employee records | Depends on the specific in-platform task | |
Cross-system automation | ||
New hire onboarding trigger | ||
Policy Q&A with source citation | Varies by configured task |
When Lucca AI is enough:Your team only needs help with specific in-platform tasks and doesn't need employees to act from Slack.
When to add Workativ:Employees ask in Slack and expect the action to happen not just an answer inside Lucca. New hires need Okta provisioned from Poplee. Terminations need Azure AD disabled the same day. Workativ and Lucca AI run alongside each other Lucca stays your system of record.
One Lucca AI agent in Slack leave, pay, expenses, and onboarding workflows coordinated across Lucca and every connected system.

80% of HR queries handled without HR involvement. Onboarding running from Lucca events.
Lucca AI agent frequently asked questions
A Lucca AI agent connects to your Lucca account and lets employees check leave balances, submit absence requests, access payslips, update personal details, and get HR policy answers all in Slack, without logging into Lucca. Lucca AI itself is an opt-in add-on that operates inside the Lucca platform. Workativ's Lucca AI agent takes action in Slack: it submits requests through Lucca's approval workflow, updates records, routes manager approvals, and coordinates connected systems like Okta and ServiceNow from a single Lucca trigger.
No. Lucca AI is an opt-in feature that operates inside the Lucca platform itself. Lucca's separate Slack and Teams integration, known as Lucca Office, syncs calendars and leave status showing who's out and updating Slack status automatically but does not let employees ask questions or take action from Slack. Workativ deploys a Lucca-connected AI agent natively in Slack that answers questions and submits requests, which neither Lucca AI nor Lucca Office currently does.
Lucca AI is an EU AI Act-compliant, opt-in add-on built into the Lucca platform for specific in-platform tasks. It does not extend into Slack, Teams, or systems outside Lucca. Workativ connects to Lucca's modules Figgo and Timmi Absences, Poplee, Pagga and brings the same self-service experience to Slack, plus extends action-taking into Okta, ServiceNow, and 100+ other apps that Lucca AI doesn't reach. Workativ and Lucca AI are complementary Lucca remains your system of record.
Workativ connects to Lucca via its public REST APIs including the Timmi Absences API for leave management using API key authentication and role-based access controls. Once connected, Workativ reads from Lucca modules like Figgo, Poplee, and Pagga, and writes back: submitting leave requests, updating personal details, and triggering onboarding workflows. No developer required.
Yes. Employee asks in Slack. Workativ reads their live leave balance from Lucca's Figgo module via the Timmi Absences API, confirms availability, and submits the request through Lucca's approval workflow. Manager receives an approval card in Slack one tap to approve. Lucca record updated. Employee confirmed in the same thread. Lucca Office can sync the resulting leave status to Slack; Workativ submits the request itself and closes the loop.
Workativ automates three core Lucca workflows: new hire onboarding (a Poplee new hire event triggers Okta provisioning, an IT access ticket in ServiceNow or Jira, and a day-1 Slack checklist), leave approval (employee requests in Slack, manager approves in Slack, Figgo record updated), and offboarding (a Lucca termination event triggers Okta disable, Azure AD suspension, and an equipment return notification in Slack).
Yes. Lucca is built for multi-country HR compliance, particularly French labor law, and serves over 7,800 clients across 130 countries. Workativ is GDPR compliant, ISO 27001 certified, and connects to Lucca without adding a separate compliance layer the AI agent respects the same country-specific leave policies and approval workflows already configured in Lucca.
Yes. When a new hire is added in Poplee, Workativ triggers the full onboarding workflow: creates the Okta identity account with correct role and groups, raises an IT access ticket in ServiceNow or Jira, and delivers a day-1 checklist to the new hire in Slack before they start. Lucca remains the system of record. HR sets the workflow up once it runs for every new hire without manual steps.
Yes. Employees update their address, emergency contacts, or bank details by asking in Slack. Workativ verifies their identity and writes the change directly to Lucca. No portal login. No HR ticket. Lucca record updated and confirmed in Slack.
Yes. Workativ connects to Lucca using API key authentication with role-based access controls. The AI agent only reads and writes what it has been explicitly permitted to access. Lucca data is never used to train models. PII is masked in all conversation logs. Every Lucca action is logged to an immutable audit trail. Workativ is SOC 2 Type II, ISO 27001, GDPR, and HIPAA compliant.
3 to 5 days for standard HR self-service leave requests, pay queries, personal updates, HR policy Q&A. No developer required. No implementation project. Workativ's no-code platform connects Lucca, configures the AI agent, and deploys it to Slack. Most teams using Lucca configure and go live without involving IT.
No. Lucca AI remains useful for the in-platform tasks it was built for. Workativ extends the Lucca experience to Slack, where Lucca AI has no presence, and connects Lucca events to systems outside the platform Okta, ServiceNow, Azure AD, and more. The two run side by side, with Lucca staying your system of record.