Product Publication
Flow that allows publishing, unpublishing or archiving products on Shopify, updating only the status of individual products without acting on other fields.
Payload – Single SKU
Payload used to manage product status starting from a single variant:
{
"sku": "BGSM001C210", // Unique code of one of the existing variants
"status": "DRAFT"
}
The specified sku ifield must correspond to a variant.
Once found, the status change operation applies to the entire product to which that variant belongs, not just to the single variant.
Possible values for the status field
| Value | Description |
|---|---|
DRAFT | The product is saved as a draft and is not visible in the shop. |
ACTIVE | The product is published and visible in the shop. |
ARCHIVED | The product is archived. It is no longer visible but remains in the Shopify catalog. |
UNLISTED | The product is published, but a direct link is required to view it. |
Behavior in case of non-existent SKU
- If at least one SKU exists → the product status is updated and, barring Shopify-side errors, the operation will go to success.
- If all SKUs do not exist and the specified
statusisDRAFTorARCHIVED→ the operation is considered successful (success). - If all SKUs do not exist and the required
statusisACTIVEorUNLISTED→ the operation is considered unsuccessful (error).
Destination configuration
Configure a Shopify destination for the single-SKU payload.
| Field | Value | Notes |
|---|---|---|
Destination Type | Shopify | |
Operation | Product status | POST /egress/sync-status-to-shopify |
GraphQL endpoint URL | https://SHOPIFYURL.myshopify.com/ | Shopify Admin GraphQL endpoint URL |
Admin API access token | shpat_CODICEALFANUMERICO | Or Client ID (API key) + Client secret — see Authentication |
Client ID (API key) | YOUR_CLIENT_ID | |
Client secret | YOUR_CLIENT_SECRET |
Deprecated — previous configuration (HTTP Adapter)
Configuration via HTTP Adapter with Base Url, Resource Path, and x-api-key header in Settings Override is deprecated. Use the Shopify destination configuration described above.
In addition to the basic data flow configuration, the following Settings Override settings were required:
| Field | Value | Notes |
|---|---|---|
Base Url | https://adapter.flowlyze.io | Adapter URL |
Resource Path | /api/adp/shopify/egress/sync-status-to-shopify | Adapter path for synchronizing product status |
Headers :: x-api-key | ********** | API key for endpoint interaction verification |
Headers :: x-shopify-graphql-url | https://SHOPIFYURL.myshopify.com/ | Shopify shop URL to connect to |
Headers :: x-shopify-access-token | shpat_CODICEALFANUMERICO | Secret of the custom app created for integration |
Payload – SKU List
Payload used to manage product status through a list of variant SKUs:
{
"skus": [
"BGSM001C210",
"BGSM001C210-0",
"BGSM001C210-1",
"BGSM001C210-2"
], // Unique codes for the variants included in the product
"status": "DRAFT"
}
The sku may contain the list of SKUs of the product’s variants.
Once the product is identified, the status change applies to the entire product, not just the single variant.
Behavior in case of non-existent SKU
- If at least one SKU exists → the product status is updated and, barring Shopify-side errors, the operation will go to success.
- If all SKUs do not exist and the specified
statusisDRAFTorARCHIVED→ the operation is considered successful (success). - If all SKUs do not exist and the required
statusisACTIVEorUNLISTED→ the operation is considered unsuccessful (error).
Destination configuration
Configure a Shopify destination for the SKU list payload.
| Field | Value | Notes |
|---|---|---|
Destination Type | Shopify | |
Operation | Many products status | POST /egress/sync-products-status-to-shopify |
GraphQL endpoint URL | https://SHOPIFYURL.myshopify.com/ | Shopify Admin GraphQL endpoint URL |
Admin API access token | shpat_CODICEALFANUMERICO | Or Client ID (API key) + Client secret — see Authentication |
Client ID (API key) | YOUR_CLIENT_ID | |
Client secret | YOUR_CLIENT_SECRET |
Deprecated — previous configuration (HTTP Adapter)
Configuration via HTTP Adapter with Base Url, Resource Path, and x-api-key header in Settings Override is deprecated. Use the Shopify destination configuration described above.
In addition to the basic data flow configuration, the following Settings Override settings were required:
| Field | Value | Notes |
|---|---|---|
Base Url | https://adapter.flowlyze.io | Adapter URL |
Resource Path | /api/adp/shopify/egress/sync-products-status-to-shopify | Adapter path for synchronizing product status |
Headers :: x-api-key | ********** | API key for endpoint interaction verification |
Headers :: x-shopify-graphql-url | https://SHOPIFYURL.myshopify.com/ | Shopify shop URL to connect to |
Headers :: x-shopify-access-token | shpat_CODICEALFANUMERICO | Secret of the custom app created for integration |
Possible values for the status field
| Value | Description |
|---|---|
DRAFT | The product is saved as a draft and is not visible in the shop. |
ACTIVE | The product is published and visible in the shop. |
ARCHIVED | The product is archived. It is no longer visible but remains in the Shopify catalog. |
UNLISTED | The product is published, but a direct link is required to view it. |