Platform integrations

Integrations that fit the systems you already run

Innovation work does not sit on its own. It depends on your identity provider, your project tools, your reporting systems and wherever your people already spend their day. Qmarkets connects to all of them.

See what we connect to

How it works

Four ways to connect

Most connections are configured rather than built. Where something genuinely needs development work, the API and our team cover it.

Native apps and connectors

Microsoft Teams has its own Qmarkets app. SSO, HR and reporting connections are configured during setup rather than developed from scratch.

REST API and webhooks

A documented REST API supports retrieving and updating information in both directions. Webhooks push events to your systems the moment they happen, so nothing has to poll for changes.

Automation platforms

Use Zapier or your iPaaS of choice to connect Qmarkets to thousands of applications with no code. This is how most organizations handle the long tail of tools that do not warrant a dedicated connector.

Integrations we build for you

Where none of the above fits, our team scopes, builds and supports the integration as part of the implementation. That includes the systems with no public API, which is usually where the difficulty sits.

Integration library

What Qmarkets connects to

These are the areas customers ask about most. Pick one to see what it does and which systems it covers.

Authentication and user provisioning

A standard SAML 2.0 based integration to your identity provider (Microsoft Entra ID, Okta or other) lets people sign in to Qmarkets with the credentials they already have, with no separate username or password to manage.

Automate user provisioning using the standard SCIM protocol or automated daily files, so people who join, move or leave are reflected in the platform without anyone maintaining a list by hand.

For external audiences, use social sign-in with LinkedIn, Facebook and others.

Also covers

Microsoft Entra ID
SAML 2.0
ADFS
SCIM
Google Workspace
Secure FTP sync
Social sign-in

Anything with a documented API can be connected, whether or not it appears here.

For your IT reviewer

What IT will want to know

The questions that come up once an evaluation moves past the innovation team and into an architecture review.

API security and governance

API access is filtered by the calling user's permissions, so it only ever returns what that user is allowed to see.

Two-way data sync

Data stays consistent in both directions rather than being pushed once and left to drift. Where a system is the master for a given field, it stays the master.

Import, export and backup

Data migration during implementation, scheduled backups while you run, and an export of your data on request, including for 60 days after the contract ends.

Who builds it

Our team scopes and delivers the integration as part of the implementation, rather than handing you a specification to build against.

Developer tooling

A documented REST API and webhooks for teams that want to build against the platform directly rather than wait on a connector.

Deployment model

Cloud or on-premise, with configurable data residency. Which one you choose changes what an integration can reach, so it is worth settling early. See security.

Under the hood

Ready to dive deeper

The detail behind the platform, for the stage of an evaluation where finance, IT and procurement get involved.

Features

Every capability across the platform, filterable by area, with an export you can score any vendor against.

Security

Certifications, data residency, encryption, access governance, and the answers your IT reviewer will want in writing.

Pricing

What sits in each tier, and how the cost changes as a program grows from one business unit to the whole company.

Good to know

Frequently asked questions

What does Qmarkets integrate with?

The native Microsoft Teams app lets people submit, comment and act on notifications without leaving the chat environment. Beyond that the platform connects to CRM, ERP, PLM, ALM, HRIS, finance and PPM systems, with a documented REST API and webhooks for anything a standard connector does not cover.

SSO runs through your existing provider using SAML 2.0 with Entra ID, Okta or another identity provider, and SCIM provisioning. Reporting data can be exported on a schedule into Power BI, Tableau or an equivalent.

Does Qmarkets support single sign-on and automated user provisioning?

Yes. Single sign-on uses a standard SAML 2.0 integration and works with Microsoft Entra ID, Okta, ADFS and other enterprise identity providers. People sign in with the credentials they already have and never create a separate Qmarkets password.

Provisioning runs through SCIM against your directory, or through an automated file-based sync over secure FTP where SCIM is not available. Roles and permissions can be mapped from the identity provider rather than maintained separately in the platform.

Is there an API, and what can it do?

Yes. The REST API supports retrieving and updating information in both directions, which covers most of what customers build. Typical uses are surfacing recent ideas or campaigns on an intranet, submitting from an external application, and synchronizing user information from another system.

Webhooks push events to your systems as they happen so nothing has to poll. API access follows the calling user's permissions.

Can we get innovation data into Power BI or Tableau?

Yes. Qmarkets has built-in reporting with configurable KPIs and dashboards, and where your reporting standard sits outside the platform, data can be exported automatically on a schedule you set and consumed in Power BI, Tableau or an equivalent tool.

Do you have a Microsoft Teams app?

Yes. It is a native app rather than a notification relay, so people can submit, comment and act on what they are sent without leaving the tool. Activity feeds inside the channel keep stakeholders current on what is moving through the platform.

For most programs this is the single change that does most for participation, because it removes the step of remembering to go somewhere else.

Can ideas become projects in Jira or our own PPM tool?

Yes. An idea reaching a defined stage can be exported into your project management platform automatically, so nobody retypes it at the handover. Status, progress and budget then flow back into Qmarkets, which is what keeps the innovation portfolio accurate once delivery has started.

What happens if you have no connector for a system we use?

Three options, in the order most customers try them. Zapier will cover a surprising amount with no code. Failing that, the REST API and webhooks handle anything with a documented interface of its own.

Where neither works, and that is usually an older internal system with no public API, our team scopes and builds the integration as part of the implementation.

Who builds and maintains the integration, and does it cost extra?

Integration work is scoped and delivered by our team as part of the implementation. Where something falls outside the standard package we will say so during the evaluation rather than at contract stage.

Which connections are standard for your setup is worth settling early, because it changes the shape of the implementation. See how pricing works.

Talk to us

Send us your stack

Tell us what you run and we will tell you what connects out of the box, what needs the API, and what would take development work. Before you commit to anything.

Get a straight answer on your specific systems
Send an integration requirements list and we will work through it
Or just ask whether we connect to one particular tool

Ask about an integration

Tell us which systems matter and we will come back with specifics.