Magento 2 integration

What it does

The Magento 2 integration lets you run ecommerce automations on behalf of any client whose Magento 2 or Adobe Commerce store you manage. Connect a store once, then list and create products, push price and stock updates, route fresh orders into fulfillment workflows, cancel orders that fail downstream checks, search customers by attribute, browse the category tree, and react to live store events without writing any code.

Connect a Magento 2 store

1. In TaskJuice, open Settings -> Connections and choose Add connection -> Magento 2.
2. Enter the full store URL including https:// and without a trailing slash (for example https://shop.example.com). The integration calls the REST API at {storeUrl}/rest/V1/... and HTTPS is required.
3. In the store's Magento admin, open System -> Extensions -> Integrations and click Add New Integration. Give the integration a recognizable name (such as "TaskJuice"), set the API resources scope to the catalog, sales, and customer endpoints you need (or grant all resources for full coverage), and save.
4. Click Activate next to the new integration. Magento displays the Access Token once on activation. Copy it into the Integration access token field in TaskJuice. The token is sent as Authorization: Bearer <token> on every outbound request.

The connection is read- and write-capable across products, orders, customers, and categories within the resource scope you granted on the integration. Rotate the token by clicking Reactivate on the integration, or revoke it by deleting the integration entirely.

Triggers

• magento-rest/order-created. Fires when a new sales order is placed in the store.
• magento-rest/customer-created. Fires when a new customer registers or is created by an admin.

Both triggers verify the inbound POST against an HMAC-SHA256 base64 digest of the request body. Configure the deliveries in Stores -> Settings -> Configuration -> Adobe Services -> Webhooks, paste the TaskJuice incoming webhook URL into the URL field, paste the shared secret shown in the TaskJuice connection screen into the signing-key field, subscribe the hook to observer.sales_order_place_after and observer.customer_register_success respectively, and Magento signs every delivery in the magento-webhook-signature header. Adobe Commerce Webhooks are available on Magento Open Source and Adobe Commerce 2.4.6 and later.

Actions

• magento-rest/list-products. List products with Magento's searchCriteria contract (filter by SKU, status, name, or any product attribute). Paginated by currentPage.
• magento-rest/get-product. Look up a single product by SKU.
• magento-rest/create-product. Publish a new product with SKU, name, price, attribute set, status, visibility, and weight.
• magento-rest/update-product. Patch an existing product (name, price, status, weight) by SKU.
• magento-rest/list-orders. List orders filtered by status, increment ID, customer email, or any order attribute. Paginated by currentPage.
• magento-rest/cancel-order. Cancel an order by its entity ID (for orders still in a cancelable state).
• magento-rest/search-customers. Search customers via the searchCriteria contract (by email, name, or any customer attribute).
• magento-rest/list-categories. Retrieve the category tree starting from the supplied root, with optional depth.

Known limitations

• Magento enforces a maximum page size of 100 on REST list endpoints. TaskJuice stops paginating after 100 pages by default; raise the ceiling on the action if you need a deeper sweep.
• The integration access token inherits whichever API resources you granted on the Magento integration. If an action returns 403, broaden the integration's scope in System -> Extensions -> Integrations and reactivate.
• Cancel order only succeeds for orders in cancelable states (pending or processing without invoiced items). Magento rejects cancellations on completed, invoiced, or already-cancelled orders.
• The list-categories endpoint returns the tree as a nested children_data object rather than a flat collection, so paginate on the client side if you need a flat list of leaf categories.
• Adobe Commerce Webhooks ship with Magento 2.4.6 and later. Stores on 2.4.5 or earlier can drive the same flows by polling list-orders with a custom watermark on updated_at and a Loop node downstream.