Wolfpack

The Wolfpack connector integrates with a Wolfpack source to synchronize product items into the Orisha Commerce Platform (OCP). It retrieves item metadata and supports downloading product images via direct URLs.

Connector	Supported Features
Items	✅ Attributes   ✅ Name   ❌ Family code   ❌ Unit of Measures   ✅ Images   ❌ Attachments
Prices	❌ Not supported
Stock	❌ Not supported
Orders	❌ Not supported
Customers	❌ Not supported

Synchronization

Item Sync

• Retrieves item codes and item details from the Wolfpack data source.
• Maps item attributes and categories into OCP item models.
• Supports image assets via absolute URLs.

Images

• Downloads images using their absolute URLs.
• Determines content type from file extension (.png, .jpg, .jpeg, .gif).
• Falls back to application/octet-stream for unknown extensions.
• Resolves a filename from the URL path; if missing, uses a fallback pattern like <ItemCode>_<Position>.<ext>.
• Skips invalid or empty URLs and logs warnings.

Settings

Configure the following fields in the OCP App when setting up the Wolfpack connector:

• BaseUrl: Base API URL for the Wolfpack environment.
• TokenEndpoint: OAuth2 token endpoint used to obtain access tokens.
• ClientId: OAuth client identifier issued by Wolfpack.
• ClientSecret: OAuth client secret. Store securely and rotate periodically.
• Scope: OAuth scopes required to access product APIs.
• ProductsChannel: Channel identifier to select the product channel (required by Wolfpack API).
• ProductsScopeId: Scope identifier used for product selection/filtering (required by Wolfpack API).

Notes:

• A connector-specific database context stores Wolfpack products, categories, and images.
• Image downloading relies on accessible absolute URLs; ensure hosting allows access from OCP.
• The internal Id is generated automatically and is hidden from configuration.

Limitations

• Attachments are not supported.
• Only absolute image URLs are processed; relative URLs are skipped.
• Unit of measures and family code are not provided by this connector.

Usage in Flows

• As a source: provides items (including attributes and images) for ingestion into OCP.
• As an enrichment: can supply images and attribute data to enhance items sourced from another connector.