Create Product

magento.create_product
ActionBusiness appsconnection required

Calls the Magento API with the connection's credentials.

Create a catalog product from its SKU, name and price.

Connection

Required
Yes — the node will not save without one
Auth type
Bearer token
Providers
Magento
Secret shape
the integration access token, or {"access_token": "…"}
Config it needs
base_url, store_code
Resolved by
config.connection_id, else node.connection_id

Configuration

9 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
sku
The new product's SKU, which must be unique in the catalog.
stringYes——SKU-1
name
The product name shown in the catalog.
stringYes———
price
The product's price in the store's base currency.
numberNo—0–1000000000—
attribute_set_id
The attribute set to create the product in; a standard install numbers its Default set 4.
numberNo41–1000000—
type_id
The product type to create.
stringNosimpleone of "simple", "virtual", "downloadable", "configurable", "bundle", "grouped"—
status
1 enables the product, 2 disables it; the store's default is used when this is left empty.
numberNo—1–2—
visibility
1 not visible individually, 2 catalog, 3 search, 4 catalog and search; the store's default is used when this is left empty.
numberNo—1–4—
product
Any further product attributes to merge in, for example 'custom_attributes', 'extension_attributes' or 'media_gallery_entries'.
objectNo———
save_options
Persist the custom options carried in the product object as well.
booleanNofalse——

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "attribute_set_id": 4,
  "save_options": false,
  "sku": "SKU-1",
  "type_id": "simple"
}

Output

One shape.

result

FieldTypeExample
id
The product's entity id.
number—
sku
The product's SKU, which every product route takes.
string—
name
The product's name.
string—
price
The product's price in the store's base currency.
number—
status
1 when the product is enabled, 2 when it is disabled.
number—
visibility
1 not visible, 2 catalog, 3 search, 4 catalog and search.
number—
type_id
The product type, for example 'simple' or 'configurable'.
string—
attribute_set_id
The attribute set the product belongs to.
number—
custom_attributes
Any EAV attributes the store added to products.
array—
{
  "attribute_set_id": 0,
  "custom_attributes": [],
  "id": 0,
  "name": "",
  "price": 0,
  "sku": "",
  "status": 0,
  "type_id": "",
  "visibility": 0
}

See Create Product run in a workflow.

In a technical demo we add the Magento connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.