Trendyol integration | Zervanor
← All connectors

Trendyol

Also an agent tool
ecommerce

Trendyol — Turkey's largest e-commerce marketplace. Seller/Marketplace Integration API (orders & shipment, products, price & inventory, returns/claims, finance, customer Q&A) over HTTP Basic auth; production + sandbox (stage) environments.

26 actions · 4 triggers

The Trendyol integration lets you connect Trendyol to your automations with 26 actions and 4 triggers — and every action is also a tool an AI agent can call. Examples: Get Orders, Update Package Status, Update Tracking Number, Update Box Info, Notify Unsupplied Items. No blank-canvas wiring — connect it and use it in your workflows.

Every action below is also a tool an AI agent can call — the same pack powers your workflows and your agents.

Triggers 4

Events in Trendyol that can start a workflow.

webhook

Order Created / Updated

Fires when an order package is created or changes status (polling get_orders).

webhook

Customer Question Created

Fires when a customer asks a question (polling get_questions).

polling

New / updated Trendyol order

Fires when an order package is created or changes status. Filter status=Created for new orders.

polling

New Trendyol customer question

Fires when a customer asks a question on your product.

Actions 26

What Zervanor can do in Trendyol.

GET

Get Orders

List order shipment packages (the flagship order trigger source).

PUT

Update Package Status

Update a shipment package status (e.g. Picking, Invoiced).

PUT

Update Tracking Number

Set the cargo tracking number for a package.

PUT

Update Box Info

Set desi/box quantity for a package.

PUT

Notify Unsupplied Items

Flag order line items as unsupplied (cannot fulfil).

POST

Split Shipment Package

Split a package by order line ids.

POST

Change Cargo Provider

Change the cargo provider for a package.

POST

Send Invoice Link

Attach an e-invoice link to a shipment package (the flagship's invoice → Trendyol step).

POST

Create Products

Create products (async batch → returns batchRequestId; poll get_batch_request_result).

PUT

Update Products

Update products (async batch → batchRequestId).

GET

Filter Products

List/filter the seller's products.

POST

Update Price & Inventory

Update price + stock (async batch → batchRequestId).

GET

Get Batch Request Result

Poll a batch (create/update/price-inventory) result; items[].status holds per-item outcome.

GET

Get Brands

List Trendyol brands.

GET

Get Category Tree

Fetch the full product category tree.

GET

Get Category Attributes

Fetch required/optional attributes for a category.

GET

Get Claims

List return/claim requests (iade).

GET

Get Settlements

List settlement (finance) transactions.

GET

Get Other Financials

List non-settlement financial transactions.

GET

Get Customer Questions

List customer questions (Q&A).

POST

Answer Customer Question

Post an answer to a customer question.

GET

Get Supplier Addresses

List the seller's warehouse/return/invoice addresses. Safe auth-only read.

GET

Get Cargo Providers

List available cargo providers.

POST

Create Webhook

Register a Trendyol push webhook (account-config; the push itself is unsigned, so Zervanor consumes orders via polling).

GET

List Webhooks

List registered webhooks.

DELETE

Delete Webhook

Delete a registered webhook.

Automations using Trendyol

📖 Blog: Trendyol in the Zervanor Engine: Orders, e-Invoice and SMS →

Frequently asked questions

What can I automate with Trendyol?

26 actions are available — for example: Get Orders, Update Package Status, Update Tracking Number, Update Box Info, Notify Unsupplied Items, and more.

Which Trendyol events can start a workflow?

4 triggers — for example: Order Created / Updated, Customer Question Created, New / updated Trendyol order, New Trendyol customer question.

Can Trendyol be used as an AI agent tool?

Yes. Every Trendyol action automatically becomes a tool an AI agent can call — the same pack powers both your workflows and your agents.

How is the Trendyol integration modelled?

Trendyol is modelled as a versioned connector pack, and the steps that need reasoning fall to first-party agents hosted in the same runtime as the workflows.