Plugs into the stack you already run.
MedRep isn’t an island. It connects to your identity provider, your ERP, your payments, your CRM, your analytics and your messaging — so your field platform is part of your business, not another silo beside it.
Connections, grouped the way you think about your stack.
A curated, supported set of integrations across the categories that matter to a field operation — each one configured per tenant.
Single sign-on and directory
Your people sign in with the credentials they already have, governed by the directory you already run.
Microsoft 365 / Entra ID
Workforce SSO and identity for staff, with directory-backed roles and provisioning.
Sell, charge and fulfil
Take payments, sync your CRM and marketing, and keep e-commerce orders flowing into one record.
Stripe
Payments and billing, with charges and statuses reconciled back into the platform.
HubSpot
Two-way CRM sync so accounts, contacts and activity stay aligned with your pipeline.
Klaviyo
Marketing automation fed by clean, consented audience and event data from the field.
Shopify
E-commerce and order capture, with orders surfaced alongside field activity.
One system of record for stock
Keep your ERP authoritative while reps see live availability in the field.
Cin7 Core
Inventory and ERP system of record, syncing products, stock levels and movements.
Reporting your leaders already trust
Embed the dashboards your business runs on, right inside the platform.
Power BI
Embedded analytics and dashboards, scoped per tenant and per role.
Reach people where they reply
Transactional email and conversational messaging, delivered through providers you choose.
WhatsApp Business
Conversational messaging for reminders, confirmations and field-team comms.
Resend
Transactional and branded email, selectable per environment for deliverability.
Azure Communication Services
The default email channel, integrated with the rest of your Azure footprint.
Answers grounded in your own content
AI that reasons over your documents and data — never the open web — with search and OCR built in.
Azure OpenAI
Hosted large language models powering assistants and generation, inside your tenant boundary.
Azure AI Search & Document Intelligence
Vector search over your library plus OCR for scanned PDFs, so AI answers cite your sources.
Keep the tools that work. Connect the ones that should talk.
You shouldn’t have to rip out a working ERP or re-train your team on a new CRM to adopt a field platform. MedRep meets your stack where it is — your ERP stays the system of record, your identity provider stays in charge of access, and your dashboards keep telling the story your leaders already read.
- Your ERP remains authoritative for stock and products
- Your identity provider governs who gets in
- Each integration configured and isolated per tenant
- Secrets held in a managed key vault, never in code
New integrations arrive through a clean adapter layer.
Every connector implements the same well-defined interface, so the platform doesn’t learn the shape of each external system — it asks the adapter. That keeps additions contained, testable and safe.
One interface
Each provider sits behind a consistent adapter contract, so the core stays simple as the list grows.
Isolated & audited
Connectors run inside tenant boundaries with credentials in the key vault and access on the audit trail.
Added without disruption
A new integration is a contained piece of work — no forks, no rewrites, no churn to your live tenants.
Configured per tenant
Turn each integration on for the customers that need it, with their own settings and scope.
Integration questions we hear most.
Often, yes. Connectors are built on a clean adapter layer, so adding a new system is a contained, well-understood piece of work rather than a rewrite. Tell us what you run and we’ll scope it honestly.
Always. Connected systems are configured per tenant, and data flowing in or out is scoped to that tenant under the same row-level isolation as everything else. One tenant’s integration can never reach another’s data.
In a managed key vault, fetched at runtime by identity. Integration secrets are never stored in code or shipped in builds, and access is auditable and revocable.
Azure Communication Services is the default, with Resend available as an alternative selected per environment for deliverability. Both send under your branded sender and templates.
No — it grows. New providers are added through the adapter layer over time, so the platform keeps fitting your stack as it evolves rather than forcing your stack to fit the platform.
Tell us what’s in your stack
Bring your ERP, identity provider, payment and messaging tools to the table. We’ll show you exactly how MedRep connects to them — and what it would take to add anything that’s missing.