Get Timewave field-service analytics in plain language. Connect Timewave to Ronja in four steps. Once connected, Ronja maps your clients, work orders, recurring missions, employees, scheduling, and invoicing (including RUT/ROT tax deduction tagging) into a governed analytics layer. Then anyone on operations can ask scheduling, revenue, and workload questions and get answers traced back to source.
How to analyze Timewave data with Ronja
Setup has two parts: a one-time admin step (request an API key from Timewave support) and a few minutes to paste the key into Ronja.
Step 1: Connect Timewave to Ronja
Just ask Ronja to connect to Timewave. Ronja surfaces a form to paste your Timewave-issued API key. Ronja exchanges the key for a JWT access token via Timewave's /auth endpoint and stores the token securely. Bearer-token auth applies to all subsequent calls. No vendor consent screen; the trust boundary is the API key itself.
Step 2: Let Ronja map your field-service data
Ronja's agents map your clients, work orders, recurring missions, employees, scheduling and gaps, invoices, issues, materials, services, and work areas into structured tables. The Swedish field-service data model is recognized automatically. RUT/ROT tax deduction line items on invoices are preserved as-is so revenue reporting matches what your accountant sees in Fortnox.
Step 3: Ask your first question in plain language
With your data mapped, ask anything. "How many work orders were completed last week, and which employees completed the most?" "Show me scheduling gaps for next week, which work areas have unfilled time slots?" Ronja runs the query against the mapped tables and shows exactly which Timewave records the answer came from. Every number traces to source.
Step 4: Combine Timewave with the rest of your stack
Timewave alone gives you field-service operations analytics. Combined with Fortnox accounting (reconciling operational invoicing against the GL), payroll (workload vs hours paid), or your CRM (customer lifetime value across operations and sales), it's transformative. Ronja unifies all your sources into a single governed layer, so cross-system queries run in seconds.
Just ask
Questions you can answer with Timewave data
Ask in plain language. Get answers traced to source. No analysts, no dashboards, no waiting.
What Timewave data Ronja maps
When you connect Timewave, Ronja's agents map the following field-service data into its governed analytics layer:
- Clients: customer records with addresses and types
- Work orders: the core operational entity (assignments, line items, completion status)
- Missions: recurring service assignments (e.g. weekly cleaning at Client X)
- Employees: staff records, roles, workload
- Scheduling and gaps: available time slots, unfilled slots, work area assignments
- Invoices: invoice records with line items, fees, and RUT/ROT tax deduction tagging
- Issues: reported problems and complaints by type
- Materials and services: supplies used, service types offered
- Work areas and groups: geographic and operational zones
Key takeaways
- Built for cleaning and home-service operations in Sweden, including RUT/ROT invoice handling
- API key is not self-service; request from Timewave support at info@timewave.se
- Connection in Ronja takes under 10 minutes once the key is in hand
- Use a dedicated API key per integration (each /auth exchange invalidates prior JWTs for the same key)
- Combines with Fortnox, CRM, payroll, and 100+ other sources for cross-system operations analytics
- All answers trace back to the underlying Timewave records
Frequently asked questions
How long does it take to connect Timewave to Ronja?
Before you start: request an API key from Timewave support (info@timewave.se). The key is not available self-service from the product UI, so plan for a few business days. Once the key arrives, the actual connection in Ronja takes under 10 minutes. Ronja exchanges the key for a JWT and starts mapping your field-service data immediately.
Why does the Timewave API key require contacting support?
Timewave does not currently offer self-service API key generation in the product UI. Keys are issued by Timewave support on request. Use a dedicated key per integration: each /auth exchange invalidates any previously-issued JWT for that same key, so sharing a key across tools will break those tools.
What Timewave data does Ronja have access to?
Clients, work orders, recurring missions, employees, scheduling and gaps, invoices (with line items, fees, and RUT/ROT tax deduction tagging preserved), reported issues, materials, services, and work areas/groups. Access scope follows your Timewave account permissions.
Do I need a developer or data engineer to use this?
No. You ask Ronja to connect, paste the API key Timewave support sent you, and that's it. No code, no middleware. Once connected, operations managers ask scheduling, invoicing, and workload questions in plain language and get answers in seconds. Timewave's developer docs (developer.timewave.se) and Swagger (api.timewave.se/v3/swagger) exist for teams that want to go deeper.
Can I combine Timewave data with Fortnox or other systems?
Yes. Combining Timewave invoiced revenue with Fortnox accounting (reconciliation between operational invoicing and the GL), or Timewave employee workload with payroll, are common use cases. You can ask cross-system questions like "show invoiced revenue per work area versus payroll cost" and get a unified answer.
Does Ronja modify any data in Timewave?
No. The connector reads data into Ronja's own governed analytics layer. Your Timewave records remain unchanged.