GearDock provides executable connection profiles across PIM, commerce, CMS, cloud-file, spreadsheet, API, webhook, and SFTP workflows. A registered profile is not the same as an activated customer connection: credentials, mappings, scope, and destination behavior are reviewed for each organization.
The Connection Model
Choose the Authorized Source or Destination
Define the account, site, store, folder, API, or endpoint the organization is permitted to use.
Review Scope and Mapping
Confirm which records may move, how external fields map to GearDock, and which direction the connection supports.
Run Inside the Organization Workspace
Jobs, checkpoints, delivery evidence, and errors remain scoped to the organization that owns the connection.
Apply the Content Boundary
Outbound profiles create drafts, unpublished records, disabled records, or atomic file drops. A connector does not approve or release content.
Provider Proof Levels
- Development-store proven
- The Shopify profile completed real provider interaction against a development store. Its outbound boundary remains DRAFT only.
- Real local-provider proven
- WordPress, WooCommerce, and Magento completed real HTTP interaction against controlled local provider instances. This is stronger than a contract test but is not a public production connection.
- Protocol tested
- The profile completed its transport and behavior contract using controlled protocol fixtures. Customer credentials and a qualified endpoint are still required.
- Contract tested
- The provider-specific request, response, mapping, and non-live publication contract is implemented and tested without a live customer account.
Public Production Activation Is Off
Durable and Controlled Execution
- Background jobs use bounded retries, provider-aware rate limits, and idempotency controls.
- Checkpoints cover completed pages so work can recover after a crash without silently restarting from the beginning.
- Dead-letter handling keeps exhausted work visible for operator review.
- Provider bulkheads prevent one failing provider from consuming every execution slot.
- Tenant-fair scheduling prevents one organization from monopolizing the shared worker plane.
- Inbound and outbound webhooks preserve delivery state and append-only operational evidence.
What a Connector Cannot Do
A connector cannot make an identity decision, approve a draft, release content, bypass the Claim Firewall, cross an organization boundary, or convert an unsupported field into operational truth. It moves data within the authority already established by the product workflow.