Configure and verify integrations EN
Check ownership, credentials, environment and downstream results before enabling a real data flow.
An integration listed in the catalogue is not necessarily configured, enabled or covered by your provider contract. First agree which system owns each kind of data and who can approve writes to it. Module availability, credentials and provider capability are separate prerequisites.
Find the connection
Open Integrations (/admin/integrations) in the correct store. The list and
catalogue help locate connections. The Topology view shows configured service
relationships and health signals; it is not proof of end-to-end acceptance.
Monitoring (/admin/integrations/monitor) brings together failed integration
calls, webhooks and queue work. Workflow connectors under Workflows are
separate from system integrations: a generic HTTP or messaging connector is not
proof that a complete accounting or stock integration exists.
Some settings open a dedicated payment, shipping, finance or other configuration page. Follow the connection's own setup links. UI layout may vary by version; confirm against the deployed admin rather than relying on an old screenshot.
Configure a controlled flow
- Identify store, provider account, environment and data owner. Avoid mixing production credentials with an unapproved test flow.
- Open the connection's Connection tab and confirm the selected store again.
- Enter credentials through the authorised settings or dedicated secret handoff, not through chat, notes or support messages.
- Save and inspect the connection overview and applicable enablement settings.
- Test one explicitly authorised scenario with synthetic or agreed test data.
- Inspect both Kaduno and the destination. Compare identifiers, quantities, states and financial responsibility, not just a green connection indicator.
Store-specific provider credentials are managed for that store. Some centrally provided services use separately managed platform credentials; do not infer the same setup or ownership model for every integration. The credential-management flow encrypts stored secrets and reports whether values are configured rather than redisplaying them. Credential changes require appropriate administrator access.
Removing a connection is consequential: it can remove stored credentials and stop the flow. It is not a routine troubleshooting step or a promise that historical records in either system will be erased.
Real-time calls and background work
Direct adapters handle some interactive work such as payment, shipping quotes and search. PullPush supports configured synchronisation workflows and remains in beta. Do not assume every integration, every data object or every action runs through PullPush. Confirm the actual route, field mapping, trigger, error owner and retry behaviour for the selected flow.
Use the integration directory to identify documented options, and the Visma order-export handover for a concrete, bounded implementation example. It is not evidence that your store has passed acceptance.
Diagnose before retrying
| Symptom | Check before acting |
|---|---|
| Not configured | Correct store, required credentials and permitted provider account |
| Access denied | Credential validity, environment, provider permissions and store enablement |
| Timeout | Whether the destination already received or executed the operation |
| No recent activity | Whether a trigger actually ran; quiet does not necessarily mean broken |
| Export failed | Latest matching attempt, error details and downstream identifiers |
A retry can create an order, invoice, shipment or message. Check the destination first and preserve idempotency/deduplication controls. Marking an issue resolved is not the same as completing its underlying business action. Do not rotate credentials, widen permissions or repeat a transfer without identifying the cause.
Record the timestamp with timezone, safe references, expected/actual result and redacted error details. Never attach secrets or complete customer exports. See webhook receiver design and launch and support.