In Diskussion Workflow Error While Automating Game Update Notifications

[Hande]

Hi everyone,
I've been testing JTL Workflows with product imports from an external source. The products are related to gaming apps/mod files, and I noticed that the workflow doesn't always trigger when new items are synced.

For example:

• Imported product has all fields (title, description, SKU).
• Workflow condition set to trigger when a new product is created.
• But sometimes the workflow doesn't execute, especially when data comes from CSV/API imports.

Has anyone faced this issue before? Do I need an additional condition (e.g., status update or attribute field) to make sure the workflow always triggers?
Thanks in advance for your help!

 

[Björn Ponsen]

Guten morgen,

es wäre super, wenn du hier einmal deinen Workflow postest, damit man sich ein genaues Bild davon machen kann, wie dein Workflow aufgebaut ist.

 

[Hande]

Hi everyone,
I've been testing JTL Workflows with product imports from an external source. The products are related to gaming apps/mod files, and I noticed that the workflow doesn't always trigger when new items are synced.

For example:

• Imported product has all fields (title, description, SKU).
• Workflow condition set to trigger when a new product is created.
• But sometimes the workflow doesn't execute, especially when data comes from CSV/API imports.

Has anyone faced this issue before? Do I need an additional condition (e.g., status update or attribute field) to make sure the workflow always triggers?
Thanks in advance for your help!

I’ve faced something similar before — JTL Workflows sometimes skip triggers when data is imported via API or CSV because the system doesn’t always register those as “manual” creations.


One workaround that helped me was adding an extra condition, like “Product active status = Yes” or a custom attribute update step right after import. That small change usually forces the workflow to detect the new entry.


I actually ran into this while setting up product syncs for gaming apps like nullsbrawll — and tweaking the trigger conditions fixed it.


Try testing with one product first and check if the workflow logs record it properly.

 

[zakran]

Guten morgen,

es wäre super, wenn du hier einmal deinen Workflow postest, damit man sich ein genaues Bild davon machen kann, wie dein Workflow aufgebaut ist.

I’d first check whether the import is actually creating a new item or updating an existing one. JTL treats those workflow events differently, so an import that updates an existing product may not fire a “created” workflow. If the API/import process is under your control, JTL also provides a way to trigger an item workflow event manually, including the Created / Changed / Deleted events.



For CSV/API imports, I’d test with one new product and one existing product and check the workflow log. If the existing product is being updated rather than created, use a Changed trigger or trigger the workflow event explicitly after the import. That should be more reliable than adding an unrelated status or attribute condition.

 

[gogepay]

Hi,

I think the issue might be related to how JTL handles imported products. Sometimes, products added through CSV or API imports may not trigger the same workflow events as products created manually, depending on the import process and workflow settings.

I would first check the import settings and workflow execution logs to see whether the products are being treated as newly created items or existing products being updated. You could also test a condition based on a status change or a specific attribute, but I’d recommend testing it with a few sample products before changing the main workflow.

By the way, I also share useful online guides and information on my website: https://gogepayservice.com/

Hope you find a solution!

 

[Markus Schmid | StoreSchmide]

Hi Hande,

this pattern is common with CSV/API imports: the row is often treated as an update to an existing item (same SKU/EAN), not as a new item. A workflow on “article created” will then not run, even though it feels like a new product on your side.

What to check first

1. Import one test SKU that definitely does not exist yet → does the workflow fire?
2. Re-import the same SKU with changed data → use a workflow on “article changed” instead of (or in addition to) “created”.
3. Open Workflow log in Wawi for the time window of the import and see whether the event was skipped or the condition failed.

If you control the import pipeline (custom connector / API): after upsert, trigger the workflow event explicitly. In JTL’s ERP API there is POST /items/{itemId}/workflow/{workflowEventId} (events 1/2/3 = created/changed/deleted – see Trigger Item Workflow). That is more reliable than bolting on unrelated attribute conditions.

If you can share your trigger type (created vs changed) and whether the import creates or updates items, others can narrow it down further.

Best regards

Die storeSchmi.de · storeSchmi.de – JTL-Servicepartner Platinum