CRM
Nimble
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Nimble, Inc. · nimble.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Nimble at a glance
- Vendor
- Nimble, Inc.
- Headquarters
- Not stated on the vendor’s pages as of 13 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 13 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 13 Oct 2026
- Panel verdict
- The AI panel rates Nimble 2/5, the mean of 6 judges. Nimble is a CRM whose bench scores are strongest on contact management and weakest on pricing transparency and sovereignty. how scores are made
- As of
- Vendor pages captured 13 Oct 2026; evaluated by the panel 15 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Nimble is a CRM whose bench scores are strongest on contact management and weakest on pricing transparency and sovereignty. Contact records carry custom fields on contacts and deals, import merge rules keyed on email then name, a Find/Merge Duplicates option and full interaction history, though we found no public information on field validation, required fields or field-level permissions. Sales pipeline, automation, integrations (4) and data portability sit mid-table: workflow stage-change triggers create activities, notes, tags, messages and sequence enrollment, the REST API writes contacts, notes, activities, deals, pipelines and custom fields, and exports are self-serve CSV delivered by email — but we found no public information on two-way email and calendar sync, webhooks, rate limits, or exporting files and attachments, and the CSV follows a template designed for re-import into Nimble. No sovereignty attributes are on record — nothing on hosting region, a data-processing agreement or subprocessors, with Intercom the only third party named anywhere. Judges' scores clustered tightly, with no substantial splits.
Speaks for it
- Contact management scores at 5-6, backed by custom fields on contacts and deals, import merge rules and a Find/Merge Duplicates option on the record
- Self-serve CSV export covers contacts, deals and activities — tasks, logged calls, events and custom activity types — delivered by email
- The documented REST API writes contacts, notes, activities, deals, pipelines and custom fields
- Workflow stage-change triggers create activities, notes, tags, messages and email-sequence enrollments, with completed runs kept under History
- Multiple customizable pipelines offer default probability by stage, stuck-deal tracking and a filterable Revenue Forecast widget
Held against it
- Pricing transparency sits at 0-1, with no public information on tiers, per-seat prices, billing periods or renewal terms on any captured page
- Sovereignty scores sit at 0-1, with no public information on hosting region, a data-processing agreement or a subprocessor list, and Intercom the only third party named
- Automation is scoped to workflows, with deal automation labelled coming soon and no public information on branching or webhooks as steps
- Exports follow Nimble's own CSV template built for re-import, with no public information on exporting files or attachments
- The data protection reviewer found no consent provenance shown for enrichment of contacts pulled from the open web — the social footprint tab, auto-written summaries and a button that fills in missing contact details
Best for
- You run a small or solo operation and want contact records with custom fields, dedupe and interaction history rather than a flat address book
- Your follow-up process fits workflow stages and email sequences, so stage-change triggers cover the automation you need
- You need to move data yourself — self-serve CSV export plus a write-capable API lets you rebuild your records elsewhere with effort
Avoid if
- You must compute a real invoice before committing — ask the vendor: the public pages we read do not show it
- You hold European personal data and need hosting region, a data-processing agreement or a subprocessor list on record — unanswerable from the public material, per the bench
- Your finance team needs quota tracking, commit categories or a custom report builder — the reporting on record is a forecast widget plus canned reports
- Your compliance review must trace consent behind enrichment features such as the social footprint tab, auto-written summaries and the Search for Contact Info action
The scores
| Criterion | Panel median |
|---|---|
| Contact & data model | 2.5 of 5 |
| Pipeline & forecasting | 2 of 5 |
| Automation & workflows | 2 of 5 |
| Integrations & API | 2 of 5 |
| European sovereignty | 0.5 of 5 |
| Import, export & exit | 2.5 of 5 |
| Pricing transparency | 0 of 5 |
Contact & data model
Show reasoningHide reasoning
How this is scored
Depth and hygiene of the core records — contacts, companies, deals, custom fields, deduplication.
0 — A flat address book; no relations between people, companies and deals.
3 — The standard three objects exist but customization is cosmetic: few field types, no required fields, duplicates accumulate unchecked.
5 — Custom fields across objects, basic dedupe on create, activity history on the record; complex models still need workarounds.
8 — Rich field types with validation, merge and dedupe tooling, relationships beyond the standard model, permissioned field access.
10 — A genuinely modelable system: custom objects or equivalent, bulk hygiene tooling, field-level history — the data model bends to the business, not the reverse.
The Solo Seller
Real records, not a flat address book: custom fields on contacts and deals, a Find/Merge Duplicates option plus merge rules on import, and an Interactions tab keeping activity and note history on the record. I found no public information on field validation or field-level permissions, so hygiene beyond defaults is manual discipline — fine at one seat, shakier past five. 1 2 3
The Data Protection Officer
Records are decently deep — custom data fields, full interaction history, files from three cloud drives, and duplicate handling on import that merges by email or name with a find-and-merge option on the record itself. But we found no public information on field validation, required fields, or field-level permissions, and the record model leans on enrichment: a social digital footprint tab, an auto-written experience-and-influence summary, and a button that fills in missing contact details — profiling of other people pulled from the open web with no consent provenance shown. 1 2
The Sales Ops Lead
Custom data fields, full interactions history on the record, and defined duplicate-merge rules on import plus a find/merge option give the core records real substance. We found no public information on required-field enforcement, field validation, or field-level permissions, so the hygiene discipline a 40-seat team needs stops at the basics. 1 2
The RevOps Integrator
Contact records carry custom data fields, interaction history, files, and company insights, and there is genuine merge tooling plus import-time dedupe rules that differ sensibly by source (email for CSV contacts, phone and name for mobile). We found no public information on field validation, required fields, field-level permissions, or custom objects beyond the standard set, so complex models still need workarounds. 1 2 3
The Migrator
Custom data fields on contacts and deals, interaction and activity history on the record, and documented dedupe — import merge rules keyed on email then name, plus a Find/Merge Duplicates action — clear the hygiene bar. We found no public information on field validation, required fields, or field-level permissions beyond deal privacy, and nothing like custom objects, so complex models still need workarounds. 1 2 3
The Skeptic
Custom fields exist on contacts and deals, import carries merge rules, a Find/Merge Duplicates option sits on the record, and interaction history and a deal changelog are kept — solidly mid-table. But it all stays inside the standard objects: we found no public information on field validation, required fields, field-level permissioning, or anything like custom objects, so complex models still need the workarounds. 1 2 3
Pipeline & forecasting
Show reasoningHide reasoning
How this is scored
Whether the pipeline enforces a process and produces reporting a finance department accepts.
0 — A kanban of deals with amounts; nothing is enforced, nothing rolls up.
3 — Multiple pipelines and stage probabilities exist, but no required fields per stage and only canned reports.
5 — Stage requirements, win/loss capture and standard forecast views; custom reporting is limited or an add-on.
8 — Enforceable process (required fields, stage gates, routing), custom report builder, forecast by team and period with quota tracking.
10 — Forecasting a CFO signs: weighted and commit-based views, historical snapshots, attainment tracking, and reporting composable enough to answer questions the vendor never anticipated.
The Solo Seller
Multiple customizable pipelines with per-stage default probability, stuck-deal flags and a filterable Revenue Forecast widget are real, and canned reports cover revenue, conversion and rep performance. I found no public information on required fields per stage, a custom report builder or quota tracking, so nothing about the process is enforced. 3 4
The Data Protection Officer
Multiple customizable pipelines, stage probabilities, stuck-deal flags and a per-deal changelog give the process shape, and a revenue forecast widget filters open and won deals by user, pipeline and period. What a finance department would interrogate is absent from the captured pages: we found no public information on required fields per stage, stage gates, quota tracking, or a custom report builder beyond the canned overview. 3 4
The Sales Ops Lead
Multiple customizable pipelines with stage-level default probabilities, a deal changelog and stuck-deal tracking are genuine stage hygiene, and the revenue forecast widget filters by user, pipeline and close date. But forecasting is a dashboard widget plus canned reports: we found no public information on required fields per stage, quota or attainment tracking, commit categories, or a custom report builder, so this is not reporting I could hand a CFO. 3 4
The RevOps Integrator
Multiple customizable pipelines with default probabilities by stage, stuck-deal flags, a filterable forecast widget, and conversion and rep-performance reports give a standard forecast view. We found no public information on required fields or stage gates that would enforce a process, and the captured pages list deal automation and activities for deals as coming soon. 3 4
The Migrator
Multiple customizable pipelines with default win probability by pipeline and stage, stuck-deal flags, a per-deal changelog and a Revenue Forecast widget filtered by user, pipeline and period are all evidenced. We found no public information on required fields per stage, a custom report builder, quota tracking or historical snapshots, and deal automation is labelled as coming soon. 3 4
The Skeptic
Multiple customizable pipelines with default probability by stage, stuck-deal tracking, win capture and a revenue forecast widget exist, but the reporting is the vendor's canned set of revenue, conversion and rep performance. We found no public information on required fields per stage, quota tracking, forecast snapshots or a custom report builder — and advanced search, saved segments and deal automation for deals are announced as "coming soon", which I decline to credit. 3 4
Automation & workflows
Show reasoningHide reasoning
How this is scored
Triggers, sequences and routing that remove manual work without a consultant.
0 — No automation beyond email templates.
3 — Simple if-this-then-that on records; no multi-step sequences, no branching.
5 — Multi-step workflows with delays and branching, email sequences, basic lead routing — capped by tier or count.
8 — Full workflow builder across objects with webhooks as steps, round-robin routing, sequence analytics.
10 — Automation as infrastructure: versioned workflows, error handling, per-step logs, and limits generous enough that the feature is not its own upsell.
The Solo Seller
Triggers fire when a contact moves between workflow stages and can create activities, notes, tags, send messages or enroll contacts into email sequences, with results tracked under History. I found no public information on delays, branching or webhooks as steps, and the captured deal page lists Deal Automation as coming soon, so automation today stays workflow-scoped. 5 6 3
The Data Protection Officer
Workflow automations fire on stage changes and can create activities and notes, tag, message, notify, and enroll contacts into email sequences, with results kept under a History view and a genuine two-way link between sequences and workflows. The trigger surface is a single event type, we found no public information on delays, branching, webhooks or lead routing, and the vendor's own pages describe automation for deals and contacts as future releases rather than shipped capability. 5 6
The Sales Ops Lead
Stage-change triggers with filters drive a real action set — activities, messages, notes, tags, notifications and email-sequence enrollment — with completed runs tracked under History. Automation is scoped to workflows with deal automation listed as coming, and we found no public information on branching, round-robin routing, or webhooks as steps. 5 6
The RevOps Integrator
Stage-change triggers with configurable filters can hand contacts into email sequences that can in turn move them between workflow stages, with results kept under History — real multi-step chaining, though scoped to workflows. We found no public information on webhooks as steps, round-robin routing, or sequence analytics, and the pages describe automation for deals, contacts, and messaging as future work. 3 5 6
The Migrator
Stage-change triggers drive real actions — create an activity or note, send a message, assign a tag, browser and mobile notifications, enrollment in email sequences — with completed runs kept under History, and sequences can add or move contacts back into workflow stages. The trigger surface is workflow-stage movement only; automation for deals, contacts and messaging is announced as future, and we found no public information on branching, webhooks as steps or per-step error handling. 5 6
The Skeptic
Triggers fire on workflow stage changes and can create activities, notes, messages, tags and sequence enrollment, with results logged under History, and sequences can feed workflow stages in both directions — a notch above bare trigger-and-action. Still, we found no public information on delays, branching or routing, and automation is confined to Workflows while the captured pages list deal automation as a future feature. 5 6 3
Integrations & API
Show reasoningHide reasoning
How this is scored
Two-way email/calendar sync, native connections, and an API that treats external systems as first-class.
0 — No API, no sync; data enters by CSV and leaves never.
3 — One-way email logging (BCC), a handful of Zapier triggers, a read-mostly API.
5 — Two-way email and calendar sync for the major providers, a documented REST API with sane limits, a modest native directory.
8 — Deep native integrations for the revenue stack, webhooks, OAuth apps, API parity with the UI for core objects.
10 — An ecosystem: public API covering everything the UI does, event streams, a marketplace, and sync so reliable the CRM can be the system of record without being the only system.
The Solo Seller
The REST API is more than read-mostly — contacts, notes, activities, deals, pipelines and custom fields are all writable, with OAuth for third-party developers and public documentation. I found no public information on two-way email and calendar sync, webhooks or a native integration directory, which is the part a solo operator notices first. 7 8 1
The Data Protection Officer
The documented REST API is genuinely write-capable — create, update and delete for contacts, notes, deals, pipelines and custom fields — with OAuth for third-party developers and scoped, admin-issued tokens for ordinary users. We found no public information on two-way email and calendar sync, a native integration directory, webhooks, or documented rate limits, so a documented API alone carries this score. 7 8
The Sales Ops Lead
The documented REST API offers full read/write over contacts, notes, activities, deals, pipelines and custom fields, with API keys, OAuth for third parties, and two-way integrations named as an explicit use case. We found no public information on two-way email and calendar sync, webhooks, or a native integration directory beyond the OneDrive, Google Drive and Dropbox file connections. 1 7 8
The RevOps Integrator
The API is genuinely two-way — create, update and delete across contacts, notes, activities, deals, pipelines, and custom fields, with an explicit intent toward two-way data integrations. But we found no public information on two-way email or calendar sync for major providers, webhooks, or a native integration directory, and OAuth is framed for older accounts and third-party developers rather than the buyer's own stack. 7 8
The Migrator
The documented REST API is the strong side, with read-write coverage of contacts, notes, activities, deals, pipelines, tags and custom fields plus simple and advanced search, over a bearer token or OAuth. We found no public information on two-way email or calendar sync, a native integration directory beyond file links to OneDrive, Google Drive and Dropbox, webhooks, or published rate limits. 1 7 8
The Skeptic
A documented REST API with write access to contacts, notes, activities, deals, pipelines and custom fields clears the read-mostly bar, though the documentation lives on a third-party host, requests go to an app URL rather than a dedicated API host, and end users are steered to admin-generated tokens. We found no public information on two-way email and calendar sync — the headline CRM integration — nor on webhooks, OAuth apps, or a native directory beyond file providers and embeddable lookups. 7 8 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where other people's personal data actually lives and under whose law — entity, hosting, subprocessors, DPA.
0 — US entity, US-default hosting, no public DPA or subprocessor list.
3 — A DPA exists and an EU region is available on request or on top tiers; subprocessor exposure to US CLOUD Act reach is broad and undocumented.
5 — EU hosting selectable at signup, published DPA and subprocessor list; core processing still touches US entities.
8 — EU entity or EU-default hosting with published subprocessors, consent-friendly fields, retention and deletion controls; residual US exposure named and narrow.
10 — European entity, EU-only processing including subprocessors, deletion that provably deletes — sovereignty a DPO can sign off without a caveat file.
The Solo Seller
I found no public information on hosting region, legal entity, DPA or subprocessors — nothing in the captured pages lets a buyer verify where contacts' personal data is processed or under whose law. For anyone holding European data, that question is currently unanswerable from public material. 8
The Data Protection Officer
The captured pages publish nothing a data protection officer could sign: we found no public information on hosting region, a data-processing agreement, a subprocessor list, retention rules, or deletion controls. Worse, the product pages showcase enrichment of other people from the open web — a social digital footprint tab, auto-written experience and influence summaries, filling in missing contact details — and we found no public information on consent fields or lawful basis behind any of it. 1
The Sales Ops Lead
We found no public information on hosting location, a data processing agreement, a subprocessor list, or any EU processing option; the data-export documentation likewise says nothing about residency or deletion. Nothing on record lets a European data protection officer begin a review. 9 10
The RevOps Integrator
We found no public information on hosting region, processing entities, a data processing agreement, or subprocessors — nothing on record speaks to where other people's personal data lives or under whose law. The vendor is presented as Nimble, Inc., and no captured page indicates an EU processing option, so this sits at the floor. 1 8
The Migrator
No sovereignty attributes are on record — we found no public information on legal entity, hosting region, a data-processing agreement, or a subprocessor list. The only third-party processor named on any captured page is Intercom for support; nothing here lets a DPO say whose law the data sits under. 4
The Skeptic
We found no public information on the vendor's jurisdiction, hosting region, DPA, subprocessor list, retention or deletion controls; the only external party named anywhere in the captured pages is Intercom, which runs support. Silence on every attribute this criterion needs leaves it at the floor. 4
Import, export & exit
Show reasoningHide reasoning
How this is scored
Getting in with history intact, and out with everything — the anti-lock-in criterion.
0 — Import is a support ticket; export is contacts-only CSV missing notes, activities and files.
3 — Self-serve CSV import with mapping; export covers main objects but drops activity history, attachments or relations.
5 — Guided migration from major competitors, full-object CSV export, API access sufficient to rebuild the database elsewhere with effort.
8 — Complete export (all objects, history, files) self-serve in open formats, import with dedupe and dry-run, no API metering that prices exit out of reach.
10 — Exit as a feature: documented full-fidelity export, migration tooling both directions, and contractual data-return terms — leaving is a weekend, which is exactly why you can stay.
The Solo Seller
Export is self-serve CSV for contacts, deals and activities (tasks, logged calls, events and custom activity types) delivered by email in a template that re-imports, and the API can pull contacts, tasks and deals to rebuild elsewhere with effort. I found no public information on exporting files or attachments, and notes go unmentioned in the documented activity export. 9 10 2
The Data Protection Officer
Exit exists and is self-serve: contacts, deals and activities each export to a CSV delivered by email, with the activity export covering tasks, logged calls, events and custom activity types, and the write-capable API can move records out with effort. But the export is CSV-only in Nimble's own re-import template, we found no public information on exporting attached files or notes, and we found no public information on guided migration in from other systems. 9 10 2
The Sales Ops Lead
Contacts, deals and activities — tasks, logged calls, events and custom types — all export to CSV with delivery by email, keeping activity history on the way out, and the CSV re-imports under defined duplicate-merge rules. We found no public information on exporting notes, files or attachments, nor on dry-run import or guided migration tooling. 2 9 10
The RevOps Integrator
Contacts, deals, and activities — tasks, logged calls, events, custom activity types — all export to CSV by date range, and the API can read back the same core objects, enough to rebuild elsewhere with effort. The export ships in Nimble's own CSV template framed around re-import into Nimble, and we found no public information on exporting files or attachments or on guided migration from other CRMs. 2 9 10
The Migrator
Exports are self-serve rather than support tickets: contacts, deals and activities each go out as emailed CSV, and the activity export explicitly carries tasks, logged calls, events and custom activity types — the history most vendors drop. Notes are only evidenced through the API, the CSV follows Nimble's own re-import template, and we found no public information on export of file attachments, import dry-runs, or contractual data-return terms. 2 3 8 9 10
The Skeptic
Self-serve CSV export covers contacts, deals and activities — though delivered by email, in a template designed for re-import into the same product — and import carries duplicate merge rules, with a write-capable API able to recreate contacts, notes, activities and deals elsewhere with effort. We found no public information on exporting files and attachments, guided migration from competitors, or API rate limits that would shape the real cost of leaving. 9 10 2 8
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real invoice — per seat, per month, at renewal — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — An entry price exists, but the tiers most buyers need are unpriced, or per-seat maths is obscured by bundles, minimums or mandatory onboarding fees.
5 — Most tiers carry real numbers with billing period and VAT treatment stated, but at least one commonly needed capability hides in an unpriced tier or usage-metered add-on.
8 — Every tier priced publicly including annual/monthly split; limits, seat minimums and overage rules stated; only genuine enterprise contracts are custom.
10 — Complete price computability: every tier, add-on, usage meter and renewal rule public, with a calculator or table that makes the invoice at 3 and 30 seats a two-minute exercise.
The Solo Seller
Not one captured page shows a price, tier, billing period or seat rule, including the onboarding material — I found no public information on what an invoice at three seats would look like. Paying with my own card, an unpriceable product is a non-starter no matter how good the records are. 7
The Data Protection Officer
We found no public information on pricing anywhere in the captured pages — no per-seat figures, no tier list, no billing periods, no renewal or VAT terms. A buyer cannot compute any invoice, at three seats or thirty, from what is published here. 3 5
The Sales Ops Lead
We found no public information on prices, tiers, seat counts, billing periods, VAT treatment or renewal terms on any captured page. No buyer can compute a real invoice — per seat, per month, at renewal — from this material. 3 7
The RevOps Integrator
Across every captured support page we found no public information on pricing — no tier, price, seat count, billing period, or renewal term appears anywhere in the evidence. A buyer cannot compute any part of the invoice from what is on record. 1 8
The Migrator
We found no public pricing information on any captured page: no tiers, per-seat figures, billing periods or VAT treatment. Even the onboarding sessions are announced without a fee, so a buyer cannot compute any invoice from what is public. 7
The Skeptic
We found no public information on tier names, per-seat prices, billing period splits, seat minimums, usage meters or renewal rules across every captured page — nothing from which a buyer could compute an invoice at any seat count. Even the onboarding sessions are documented with a schedule and no fee, so I cannot rule out that the invoice hides there. 1 2 3 4 5 6 7 8 9 10
Questions about Nimble
Is Nimble European?
Not determined: the vendor’s pages as captured do not say where Nimble is based.
Where does Nimble store data?
Not stated on the vendor’s pages as of 13 Oct 2026.
Does Nimble have a free plan?
Not stated on the vendor’s pages as of 13 Oct 2026.
What are the best alternatives to Nimble?
As of 21 Oct 2026, the panel rates Pipedrive (3/5), Bitrix24 (3/5) and HubSpot Sales Hub (3/5) highest among the other 49 CRM products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Pipedrive (EU origin, foreign-owned). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Nimble alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 13 Oct 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- We found no public information on compliance on the pages we read (support.nimble.com/en/articles/3020685-nimble-contact-record-overview, support.nimble.com/en/articles/502827-how-to-merge-duplicate-contacts, support.nimble.com/en/articles/6695934-nimble-s-deal-feature-overview, support.nimble.com/en/articles/6929289-nimble-today-page-revenue-forecast-widget, support.nimble.com/en/articles/6232610-automation-for-workflow, support.nimble.com/en/articles/9682157-using-email-sequences-with-workflows and 4 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 4 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 3 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (10)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Contact & data model — found from sitemap support.nimble.com Checked 13 Oct 2026 Details →
- 2 Contact & data model — found from sitemap support.nimble.com Checked 13 Oct 2026 Details →
- 3 Pipeline & forecasting — found from sitemap support.nimble.com Checked 13 Oct 2026 Details →
- 4 Pipeline & forecasting — found from sitemap support.nimble.com Checked 13 Oct 2026 Details →
- 5 Automation & workflows — found from sitemap support.nimble.com Checked 13 Oct 2026 Details →
- 6 Automation & workflows — found from sitemap support.nimble.com Checked 13 Oct 2026 Details →
- 7 Integrations & API — found from sitemap support.nimble.com Checked 13 Oct 2026 Details →
- 8 Integrations & API — found from sitemap support.nimble.com Checked 13 Oct 2026 Details →
- 9 Import, export & exit — found from sitemap support.nimble.com Checked 13 Oct 2026 Details →
- 10 Import, export & exit — found from sitemap support.nimble.com Checked 13 Oct 2026 Details →