Get Lime CRM analytics in plain language. Connect Lime CRM (Lundalogik) to Ronja in four steps. Once connected, Ronja auto-discovers your installation's schema, maps standard objects (Companies, Persons, Deals, Activities) and your custom limetypes, and lets anyone on the team ask sales questions and get answers traced back to source. No exports, no spreadsheets, no data engineering.
How to analyze Lime CRM data with Ronja
Setup is two parts: a one-time admin step in Lime to generate an API key, then a few minutes to paste the key and base URL into Ronja.
Step 1: Connect Lime CRM to Ronja
Just ask Ronja to connect to Lime CRM. Ronja surfaces a form for your Lime CRM base URL and API key. The key is generated by a Lime admin in the LISA admin interface. Ronja stores both securely and starts analyzing your sales data. Cloud deployments work out of the box.
Step 2: Let Ronja auto-discover your Lime schema
Lime CRM is heavily customizable. Different installations look completely different. Ronja calls Lime's metadata discovery API on connection to learn exactly which object types exist in your installation. Standard objects (Companies, Persons, Deals, Activities, Offices) are mapped automatically. Any custom limetypes you have configured for your industry or workflow are detected and mapped without any manual schema work.
Step 3: Ask your first question in plain language
With your data mapped, ask anything. "What's our deal velocity this quarter versus last?" "Which sales reps have the most open activities without a follow-up scheduled?" Ronja runs the query against the mapped tables and shows exactly which Lime records the answer came from. Every number traces to source.
Step 4: Combine Lime CRM with the rest of your stack
Lime CRM alone gives you sales pipeline analytics. Combined with Fortnox accounting (invoice reconciliation against sales pipeline), call data, or marketing tools (campaign-to-deal attribution), it's transformative. Ronja unifies all your sources into a single governed layer, so questions like "show invoiced revenue by Lime sales rep this quarter" run in seconds.
Just ask
Questions you can answer with Lime CRM data
Ask in plain language. Get answers traced to source. No analysts, no dashboards, no waiting.
What Lime CRM data Ronja maps
When you connect Lime CRM, Ronja's agents auto-discover your installation's schema and map the following into the governed analytics layer:
- Companies: primary B2B accounts
- Persons and Contacts: individuals linked to companies
- Deals and Opportunities: sales pipeline with stages and values
- Activities and History: interaction log (calls, meetings, emails, notes)
- Offices: location records
- Custom limetypes: any object types configured for your business (industries, relationship types, workflows), auto-discovered via Lime's metadata API
Key takeaways
- The Lime CRM connector works for cloud and on-premise installations
- Setup needs an API key from your Lime admin and your Lime base URL
- Ronja auto-discovers your custom limetypes via Lime's metadata API. No manual schema definition
- Rate limited to 3,000 requests per 5 minutes (cloud) on the Lime side
- Combines with Fortnox, call data, marketing tools, and 100+ other sources for cross-system revenue analytics
- All answers trace back to the underlying Lime records, every query audit-logged
Frequently asked questions
How long does it take to connect Lime CRM to Ronja?
Before you start: a Lime admin generates an API key for an API user in the LISA admin interface (Databases → Security → Users → "Create API key"), and you note your Lime CRM base URL. Most teams then complete the connection in under 10 minutes. Ronja stores the credentials, calls Lime's metadata discovery API, maps standard and custom objects, and starts analyzing data.
Is Lime CRM cloud or on-premise, and how does that affect the connection?
Lime CRM can be cloud-hosted or installed on-premise. Cloud deployments work out of the box once you provide the API key and base URL. On-premise installs need the Lime API endpoint reachable from Ronja, either by exposing it externally with proper security or via a local gateway.
What Lime CRM data does Ronja have access to?
Standard objects: Companies, Persons, Deals and Opportunities, Activities and History, Offices. Plus any custom limetypes you have configured. Lime CRM is heavily customizable, and Ronja calls Lime's metadata discovery API on connection to learn the exact schema of your installation, so custom objects map automatically.
How does Ronja handle GDPR for Lime CRM data?
Ronja reads Lime CRM data according to the permissions of the API user the key was generated for, and every query is audit-logged in Ronja's governance layer. For tighter data minimization, you can restrict the API user's permissions in Lime, or configure Ronja's masking rules to redact specific fields. Standard GDPR data-subject rights are honoured by the same processes you already use for Lime.
Can I combine Lime CRM data with Fortnox or other systems?
Yes. Combining Lime CRM sales pipeline with Fortnox invoicing for revenue reconciliation, or with call data and marketing tools for end-to-end attribution, is a common Lime use case. You can ask cross-system questions like "show invoiced revenue by Lime sales rep this quarter" and get a unified answer.
Does Ronja modify any data in Lime CRM?
No. The connector reads data into Ronja's own governed analytics layer. Your Lime CRM records remain unchanged.