Integrations

Integrations for the systems around production work.

Connect Konfi Cloud to the external systems production and service teams already use for marketplaces, invoices, courier work, tenant email, and private provider workflows.

Create a Free workspace View supported integrations

Pro connectors

Allegro, Fakturownia, Google storefront, InPost, Polkurier, and Resend start on Pro.

Enterprise path

API-token providers and dedicated-instance bridges are scoped for Enterprise.

Governed setup

Plan and deployment checks decide which integrations can be configured.

Supported connectors

What Konfi supports through integrations.

Each connector has a defined setup model, plan requirement, and deployment boundary. Pro covers the self-serve connectors; Enterprise covers private provider and dedicated-instance paths.

Marketplace

Allegro

OAuth setup for marketplace order and offer workflows.

Connect Allegro through OAuth instead of storing marketplace passwords.

Support marketplace order and offer workflows inside the Konfi runtime.

Keep integration access governed by the workspace plan and tenant boundary.

PlanPro

SetupSelf-serve

Provider

API-token provider

Operator-managed connector model for providers that require private API tokens.

Handle providers that require long-lived API tokens or private credentials.

Scope implementation and support before credentials are accepted.

Keep setup operator-managed for Enterprise customers.

PlanEnterprise

SetupOperator-managed

Dedicated

Dedicated instance bridge

Dedicated bridge for isolated runtimes, private networks, or customer-specific credentials.

Connect isolated Konfi deployments when hosted SaaS is not the right boundary.

Support private-network or customer-specific credential requirements.

Keep the integration path tied to a dedicated Enterprise deployment.

PlanEnterprise

SetupOperator-managed

Accounting

Fakturownia

Tenant-owned Fakturownia credentials for invoice and customer workflows.

Use the tenant's Fakturownia API token.

Support invoice workflows and customer lookups.

Store credentials encrypted and keep them out of browser responses.

PlanPro

SetupSelf-serve

Storefront

Google storefront

Public Google storefront settings for reviews and Tag Manager.

Store only Place IDs and Tag Manager container IDs per storefront channel.

Use Konfi Cloud-managed Places access without tenant API keys.

Enable reviews and storefront tags independently for each channel.

PlanPro

SetupSelf-serve

Shipping

InPost

Tenant storefront parcel-locker picker setup.

Use the tenant's public InPost GeoWidget token.

Enable Paczkomaty selection in the Konfi storefront checkout.

Keep parcel-locker setup scoped to the tenant workspace.

PlanPro

SetupSelf-serve

Shipping

Polkurier

Tenant-owned courier credentials for shipping operations.

Use the tenant's Polkurier login and API token.

Support courier orders, labels, shipment statuses, and pickup points.

Keep shipping setup connected to the tenant workspace.

PlanPro

SetupSelf-serve

Payments

Przelewy24

Tenant-owned Przelewy24 checkout credentials for storefront payments.

Use the tenant's POS ID, API key, and CRC.

Verify tenant-specific payment notifications before order updates.

Keep payment credentials encrypted and scoped to one workspace.

PlanPro

SetupSelf-serve

Resend

Tenant-owned email sending through a verified Resend sender.

Use a restricted Resend API key owned by the tenant.

Send transactional email from a configured sender address.

Support domain hygiene with SPF, DKIM, and DMARC before production sending.

PlanPro

SetupSelf-serve

Payments

Stripe

Tenant-owned Stripe checkout credentials for storefront payments.

Use the tenant's Stripe secret key and webhook signing secret.

Support tenant-specific checkout, refunds, and payment webhooks.

Keep Stripe secrets encrypted and hidden from browser responses.

PlanPro

SetupSelf-serve

Availability

Plan and deployment requirements stay explicit.

This table is driven by the same integration catalog used by onboarding and plan checks.

Integration	Required plan	Setup type	Deployment	Management
Allegro	Pro	OAuth	Hosted SaaS, Dedicated	Self-serve
API-token provider	Enterprise	API token	Hosted SaaS, Dedicated	Operator-managed
Dedicated instance bridge	Enterprise	Dedicated instance	Dedicated	Operator-managed
Fakturownia	Pro	API token	Hosted SaaS, Dedicated	Self-serve
Google storefront	Pro	Public config	Hosted SaaS	Self-serve
InPost	Pro	Public config	Hosted SaaS, Dedicated	Self-serve
Polkurier	Pro	API token	Hosted SaaS, Dedicated	Self-serve
Przelewy24	Pro	API token	Hosted SaaS, Dedicated	Self-serve
Resend	Pro	API token	Hosted SaaS, Dedicated	Self-serve
Stripe	Pro	API token	Hosted SaaS, Dedicated	Self-serve

Operational model

Built for real operational ownership.

Konfi treats integrations as workspace capabilities with clear ownership, plan checks, and deployment boundaries.

Credential ownership

Tenant-owned secrets are accepted through controlled setup flows and stored encrypted before use.

Runtime boundary

Self-serve connectors run through Konfi Cloud, while private provider paths are scoped for Enterprise.

Plan-aware access

Plan entitlements and deployment modes decide which connectors can be configured.

Integration path

Start with the operational workflow, then connect the systems around it.

Create a workspace to evaluate the core workflow, then move to Pro or Enterprise when the integration path is ready.

Create a workspace Compare plans