How pxtra scales employee benefits integrations with n8n

Context

pxtra is a B2B SaaS platform that makes employee benefits easy, efficient, and attractive for companies across Germany. Hundreds of organizations, including well known brands like Leica, Lacoste, and Oatly, use pxtra to offer flexible benefits to their employees.

Instead of the traditional top down approach where HR picks one or two benefits and “shoots” them to everyone, pxtra gives each employee a monthly budget and a digital cafeteria system. Through an app, employees can choose the benefits that best fit their life situation, lifestyle, and needs.

Behind the scenes, HR teams struggle with a fragmented tool landscape and a lot of manual work. Many of pxtra’s customers use different HR systems, payroll systems, or even just Excel, creating complexity for data imports, exports, and payroll calculations.

pxtra is currently moving from startup to scale up, which means many projects and rapid feature development in parallel. As founder and CEO Mark Bosold put it, “we really need to have a sustainable use of our resources” to reach break even and grow efficiently.

To support that growth, pxtra adopted n8n and over time expanded it from a personal tool used by the founder into a company wide automation and integration layer, with about 40% of employees using it across departments.

Challenge

pxtra’s core value for customers depends on how quickly and reliably they can connect to each customer’s existing systems. The reality, however, was a very diverse customer IT landscape:

• Every new customer had a different HR system and payroll setup
• Some customers relied on modern SaaS tools, others only had online Excel
• Data had to flow from customer HR into pxtra, and from pxtra into customer payroll

The main use case was always the same:

“You have an HR system, which is not connected already through our connectors, and you want to get employee data into our benefit platform, and you want to get all the benefit data into your payroll system to create the payroll slips.”

Initially, pxtra handled those integrations by writing custom code directly in the SaaS product whenever a large customer needed a new connection. This created several serious issues:

Long onboarding times

• Custom-coded integrations often took 2 to 3 months to complete, depending on data quality, access, and customer collaboration.
• Until the integration was ready, pxtra could not fully onboard the customer or start invoicing.

Complex, fragile codebase

• Customer specific integration logic lived inside the main product code, making it harder to maintain.
• Knowledge about each integration was siloed with the developer who implemented it.

Resource constraints during scale up

As a growing company with many parallel projects, pxtra needed to use engineering capacity very efficiently. They could not afford to keep building bespoke integrations in the core codebase for each new customer.

pxtra needed a way to:

• Decouple customer specific integrations from the main product
• Reuse and adapt existing work quickly
• Reduce onboarding times from months to days
• Turn integrations into a repeatable, scalable service offering

Solution

Mark, whose background is in data, BI, and analytics, had been experimenting with automation tools for years. After trying n8n personally for reporting, BI, and data movement use cases, he realized that:

“Wow, this is really like a modern automation platform. We need to use it in all departments.”

Several aspects made n8n stand out for pxtra:

Combination of low code and real code

n8n allows teams to mix visual workflows with code nodes:

“With n8n, I was like, oh, wow, you can combine low code with really code approaches where you integrate Python, which was my main language as a data nerd, and JavaScript code blocks. So this was a game changer.”

Hosting flexibility and control

Being able to self host and run n8n within pxtra’s own infrastructure was a key requirement for security and compliance.

Architecture and implementation

pxtra migrated customer specific code implementations out of their SaaS product and rebuilt them as n8n workflows, connected to their platform via a REST API. The core pattern is:

• Each customer gets one main workflow for their integration
• Workflows live in clearly named folders by customer, so the team has direct access without digging through GitHub
• Standard building blocks include HTTP Request nodes to pxtra’s enterprise API, code nodes, error workflows, webhooks, and GitHub integration

When a new customer comes in with a “new” integration requirement, the team:

• Looks for similar existing workflows (for example, SFTP similar to WebDAV)
• Duplicates and adapts the workflow in n8n instead of writing new code in the monolith
• Uses internal patterns for error handling and logging

They also introduced internal enablement so non purely technical roles can contribute:

• A “tool school” with Loom videos and internal documentation in Confluence
• Slack channels for questions and sharing best practices
• Key users and “high performance” users who help others adopt n8n

Results

Onboarding time cut from months to days

By moving customer specific integrations into n8n workflows, pxtra reduced the time it takes to get a new customer live:

• Before: 2–3 months for onboarding and custom code integration
• After: a few days to build and adapt workflows in n8n

This has a direct impact on time to value for customers and pxtra’s time to invoicing, since projects no longer get stuck waiting for custom integrations.

Cleaner codebase and fewer bugs

Moving integration logic out of the product code has significantly improved maintainability:

• The main SaaS codebase is cleaner and less cluttered with one off logic
• Reusing existing n8n workflows reduces the risk of duplicate implementations
• Building once with high quality in n8n reduces the number of bugs and errors dramatically

“With n8n, maintaining our codebase has become much easier because we offloaded all the custom scripts. Our code is cleaner now and the number of bugs has dropped significantly.” Denny Kunkel, Team Lead Development, pxtra

Scalable service revenue

With n8n, pxtra turned integrations into a scalable service product:

• Each individual integration can be sold as an additional service on top of the software license
• Thanks to faster and more reusable workflows, they can deliver more projects with the same team
• Over the last six months, pxtra has doubled its service income

Higher employee satisfaction

Before n8n, some customer projects were seen as “black cat” projects that developers dreaded revisiting. With n8n:

• Integrations are visually understandable, modular, and easier to maintain
• Developers and operations staff enjoy working with the platform

“My team is also much happier handling custom integrations this way compared to coding everything themselves.” Denny Kunkel, Team Lead Development, pxtra

Company wide automation mindset

n8n is no longer just an integration tool around the core product. It has become a company wide orchestration layer:

• pxtra connects Slack, Google Workspace, Asana, Stripe, HubSpot, their own platform API, HR systems like Kenjo, and more through n8n
• The leadership team is actively building awareness in departments to recognize recurring processes and automate instead of hiring for every new task