PrestaShop integration

What it does

The PrestaShop integration lets you run ecommerce automations on behalf of any client whose PrestaShop store you manage. Connect a store once, then list and look up products, route fresh orders through fulfillment workflows, update order status when shipments leave the warehouse, monitor abandoned carts, and pull customer records into your CRM without writing any code.

Connect a PrestaShop store

1. In TaskJuice, open Settings -> Connections and choose Add connection -> PrestaShop.
2. Enter the full store URL including https:// and without a trailing slash (for example https://shop.example.com). HTTPS is strongly recommended because the webservice key is sent on every request via HTTP Basic.
3. In the store's Back Office, open Advanced Parameters -> Webservice and confirm the webservice is enabled. Click Add new webservice key, give the key a recognizable description (such as "TaskJuice"), and grant view, modify, add, and delete permissions on every resource the workflow touches (at minimum: products, orders, customers, carts, order_states). Click Save.
4. Copy the generated key into the Webservice API key field in TaskJuice. Leave the Password (leave blank) field empty. PrestaShop's webservice protocol requires the API key as the HTTP Basic username and an empty password.

The connection is read- and write-capable across the resources the API key was granted under. Rotate or revoke the key from the same Advanced Parameters -> Webservice page at any time.

Triggers

• prestashop/order-updated. Polls the orders endpoint for entries created or updated since the previous poll cycle. Emits one activation per cycle wrapping every observed order in an items array; drop a Loop node downstream to process each order individually.

PrestaShop's core webservice does not publish first-party webhooks, so order monitoring runs as a watermark-based polling trigger over /api/orders with the filter[date_upd] directive. Tune the poll interval and the per-cycle ceiling under the trigger's Polling section.

Actions

• prestashop/list-products. List products in the store with filters for SKU reference and active flag. Paginated via the offset,limit query.
• prestashop/get-product. Look up a single product by ID, with full or partial field selection via the display directive.
• prestashop/list-orders. List orders with filters for current state, customer, and last-updated window. Paginated via the offset,limit query.
• prestashop/get-order. Look up a single order by ID, with the order rows association expanded.
• prestashop/list-customers. List customer records with filters for email and active flag. Paginated via the offset,limit query.
• prestashop/list-carts. List shopping carts with filters for customer and last-updated window. Useful for abandoned-cart workflows.
• prestashop/update-order-state. Move an order to a new state (for example mark as shipped or cancelled) by sending the order ID and the target order-state ID.

Known limitations

• The PrestaShop webservice does not ship first-party webhooks in core. Real-time notifications require a third-party module; TaskJuice ships the polling trigger as the supported, in-envelope alternative.
• API key permissions are scoped per resource. If a workflow returns a 403 from a resource it was working against, re-open the key in the Back Office and grant the missing verb on that resource.
• HTTP Basic authentication sends the API key on every request. Serve the store over HTTPS so the key is not transmitted in plaintext.
• The PrestaShop webservice returns XML by default. TaskJuice sets the Output-Format: JSON header on every request so responses come back as JSON; if you embed the connection in a custom action remember to keep that header.
• Order-state IDs are store-specific and configurable under Shop Parameters -> Order Settings -> Statuses. Confirm the numeric IDs for your client's store before wiring the prestashop/update-order-state action into a workflow.
• The webservice exposes resource listings without a total count; TaskJuice stops paginating after 100 pages by default. Raise the ceiling on the action if you need a deeper sweep.