Skip to main content
PVology
Sign in

PVology Connect · Integrations & Enterprise Connectivity

Connect PVology to the systems your organization already uses

One secure integration foundation for every PVology application: connect your own systems, exchange files, call the API, receive signed events and prepare enterprise sign-in. Every connector is honestly labelled with what works today.

Integration overview

A platform service, not another application

PVology Connect sits under every application, the way identity, permissions and audit do. It is included wherever your workspace is: there is nothing extra to buy, and organization policies decide which kinds of integration are allowed.

  • Connections to your own systems, each with its own encrypted credential, test, health with reasons and history
  • Mapping, imports and exports with a dry run before anything changes
  • Sync that retries what is temporary, keeps every record that did not go in and never overwrites a conflict silently
  • The PVology API, signed webhooks with event versions, and an event catalog
  • Enterprise identity readiness: single sign-on and SCIM provisioning, switched on together with you

In the app: Menu → Insights & tools → Connect. Managed by organization owners, administrators and Integration Administrators; credentials and identity stay with owners and administrators.

What is included today

  • ConnectionsAvailable
  • Connector catalogAvailable
  • MappingsAvailable
  • SyncAvailable
  • Structured importAvailable
  • Structured exportAvailable
  • PVology API and API clientsAvailable
  • Webhooks (versions, rotation, replay)Available
  • Event catalogAvailable
  • Enterprise identity (single sign-on and SCIM, switched on per organization after a joint test)Beta
  • LogsAvailable
  • HealthAvailable
  • Developer guideAvailable

APIs

The PVology API, for your tools and systems

Read and send data for every PVology application with an API client: a service account for one tool, with only the permissions you choose.

Access you control

Fourteen scopes, none granted by default. API keys or OAuth 2.0 client credentials with 15-minute tokens. Allowed addresses, expiry, rotation with overlap, and revocation from the next request.

Predictable behaviour

Cursor paging, rate limits with headers and Retry-After, one error model with a support reference, and versioning in the path: only additions within v1.

Safe writes

Every write needs an Idempotency-Key and goes through the application's own rules: evidence arrives for review, signals as candidates, KPI actuals through their acceptance rules.

Webhooks and events

Tell your systems when something happens

Choose business events such as a deal won, a milestone overdue, a KPI actual approved or a risk rating changed, and PVology sends each one as a signed request.

  • Signed with a timestamped HMAC; secret rotation keeps the previous secret signing for 24 hours
  • Every event has versions with a fixed list of facts; each endpoint pins the version it understands
  • Retries after 1 minute, 5 minutes, 30 minutes and 2 hours; a delivery log with every attempt; failed deliveries can be sent again with the same event id
  • Incoming webhooks let a form or another system create records in PVology through signed, deduplicated requests

Data exchange

Bring records in and take them out, safely

One import engine and one sync engine for every application, with the same steps everywhere: map, test, dry run, then apply.

Imports, exports and mapping

  • CSV, Excel and JSON files up to 10 MB and 20,000 records
  • Fixed, typed transformations, with dates that stay on their day
  • External references so a second import never duplicates a record
  • Exports with field-level rules and spreadsheet formulas neutralized

Sync

  • On demand or on a schedule, compared field by field
  • An explicit source of truth on every connection; two-way only with one owner per field
  • Failed records and conflicts wait for a person; a partial sync is never shown as complete
  • A change in the other system's fields stops the sync before anything is written

Enterprise identity

Single sign-on and provisioning, switched on together with you

Organizations can prepare single sign-on with an OpenID Connect identity provider, verify their domains and prepare SCIM 2.0 provisioning. These are built and tested, and stay off until PVology switches them on for your organization after a joint test with your provider.

  • Owners always keep password sign-in, so a provider problem never locks you out
  • A verified domain never adds members or rights by itself
  • Role mapping can never grant the Owner role
  • Deprovisioning ends access and never deletes people, their records or the audit trail

Available on request

Enterprise identity is switched on per organization after a joint test. SAML is planned. Tell us which identity provider you use.

Connector framework

Connectors are definitions; connections are yours

Each connector in the catalog is a versioned definition with its authentication, objects, directions, requirements and limitations. Your connection is your own configured instance, with its credential, environment (sandbox or production), owner and history. Applications declare what may come in and go out, and keep every write in their own services.

Today you can connect the built-in sample system and your own system's REST API (the Generic REST connection, Beta). Connectors for named vendors are added only when they work, and are never shown as connected before then.

Security

Built to be safe by default

  • Credentials are encrypted or kept only as fingerprints, shown once, and never appear in logs, e-mails, AI facts or support tools
  • Outgoing calls go to public HTTPS addresses only, checked against internal networks at every call; redirects are not followed
  • The workspace always comes from the credential, never from the request; records of another workspace answer like missing ones
  • Logs hold operational facts only, with a support reference for every operation
  • Integration Administrators run integrations without ever touching credentials or identity
Security & Trust

Supported and planned connectors

Honestly labelled, from the product's own catalog

Available and Beta connectors work today. Coming soon ones are built and switched on with you. Planned ones are not available: no partnership, certification or endorsement with any vendor is implied.

Available

8
  • Outgoing webhooks
  • Incoming webhooks
  • PVology API
  • Calendar feed
  • Sample system (sandbox)
  • Structured file import (CSV, Excel, JSON)
  • Structured file export
  • Project schedule files (XML and XER)

Beta

1
  • Generic REST connectionYour own system, your own credential

Coming soon

2
  • Single sign-on (OpenID Connect)Available on request after a joint test
  • User provisioning (SCIM 2.0)Available on request after a joint test

Planned

20
  • Business intelligenceNeeds your account
  • Microsoft 365Needs your account
  • Microsoft Entra ID single sign-onNeeds your account
  • Google WorkspaceNeeds your account
  • ERP and accountingNeeds your account
  • External CRMNeeds your account
  • Meta (WhatsApp Business, Facebook lead forms)Needs your account
  • LinkedInNeeds your account
  • Jira CloudNeeds your account
  • Single sign-on (SAML)
  • Process data feeds
  • SAP and Oracle ERP
  • ServiceNow
  • HR systems
  • Data warehouses
  • Document management systems
  • Automation platforms
  • Live schedule sync
  • Process mining and telemetry
  • Regional data connectors
Every connector with what it does and needs

Developer experience

Documented the same way it is built

The API description is generated from the same contracts the API enforces, so the documentation and the routes cannot drift apart.

OpenAPI 3.1 description

Every endpoint, parameter, request body and answer, public and machine-readable.

/api/v1/openapi.json

Developer guides

Authentication, scopes, paging, idempotency, errors, rate limits, webhooks and their signatures, events, SCIM and building a custom integration.

Developer guides in the Help Center

In-app developer guide and sandbox

Examples, error codes and signature checks in Connect → Developers, and the North River sandbox to try every step with sample data that never leaves PVology.

Open the developer guide (sign in)

Ecosystem benefits

One secure foundation connects every application

Each application exchanges data through the same foundation, with its own rules deciding what may change.

  • PVology ProjectOrbit

    ProjectOrbit can receive approved project data from your other systems.

    Costs, budgets and documents are never sent out; team-only projects only when an owner or administrator grants it.

    What ProjectOrbit exchanges

  • PVology StrategyPulse

    StrategyPulse can consume enterprise KPI sources.

    A missing value is recorded as a source failure, never as 0, and closed periods are refused.

    What StrategyPulse exchanges

  • PVology Dealflow

    Dealflow can exchange customer information with another CRM or a spreadsheet.

    A deal's stage changes from outside only when the other system is set up as the source of truth for it.

    What Dealflow exchanges

  • PVology Governance & Assurance

    Governance & Assurance can receive authorized evidence and indicators.

    An import never accepts evidence, declares a control effective or sets a risk rating; a person decides.

    What Governance & Assurance exchanges

  • PVology OpsCatalyst

    OpsCatalyst can use process signals from your operational systems.

    A signal never becomes an approved improvement or a case by itself.

    What OpsCatalyst exchanges

  • PVology ValueLens

    ValueLens can use approved cost and performance information.

    Approved proposals and the realization ledger are never changed from outside.

    What ValueLens exchanges

Custom integration services

Help from PVology, on request

PVology Integration Services are scoped with you and confirmed in a proposal before any work begins. They are not self-service products and have no published price.

  • Integration assessment

    Which systems hold which records today, where people re-key data, and which source of truth each record should have.

  • Integration advisory

    The integration approach for your landscape: what to connect first, with which direction and which safeguards.

  • Integration setup

    Connections, credentials, mappings and dry runs set up with your team in PVology Connect.

  • Data migration

    Bringing existing registers into PVology through the import engine, with dry runs and a record of what did not go in.

  • API integration

    Help for your developers with API clients, scopes, idempotent writes and webhooks.

  • Custom connector

    Connecting a system that has no connector yet, on the Generic REST connection or as a new connector we scope with you.

  • Enterprise identity setup

    Preparing single sign-on and SCIM provisioning and the joint test with your identity provider.

  • Integration support

    Watching health, failed records and conflicts with you after go-live.

PVology Integration Services

Support and documentation

Help where you need it

Help Center

Step-by-step articles for every Connect task, from creating a connection to resolving a conflict.

PVology Connect help

PVology Academy

A short course, PVology Connect Essentials, is in preparation, with role profiles for administrators, integration administrators, developers, security and support administrators.

PVology Academy

Ask PVology and Support

Ask which integrations need attention or why a sync failed; PVology Support traces any job by its support reference, without ever seeing your credentials.

Ask PVology

Which systems should PVology connect to?

Tell us which systems matter to you. It helps us decide which connectors to build next.

Discuss integrationSee the connectors