Introduction
Any store automation would start with setting up a task.
After opening Developer Console you can select the class of task you want to create. After that you should see blank template where you can insert all your logic with help of Liquid language.
After task is created it is in inactive state. Activate it, from here you can either wait for your store events to trigger the task (if your task responds to webhooks), wait for scheduler to run it, trigger it manually (scheduled task with manual trigger) or by querying autogenerated endpoint (http task).
Tasks can be triggered in number of different ways:
- Automatically - following schedule of your choice (scheduled task with timer trigger)
- Manually - by clicking Run button next to the task name
- Via HTTP call - hitting autogenerated endpoint may trigger the task (and return a response)
- Event in your store - if your tasks responds to any event in your store (e.g. new order).
Each currently running task will appear under Runs section. Here you can also copy run ID or stop the task.
Each task will log certain actions. All logs appear under Logs section. Each log belongs to one of the following categories:
- INFO - simple informational log to tell you what is currently going on
- WARNING - something unexpected happened, however task execution can be continued
- CRITICAL - critical error, task execution is stopped
- ACTION - an action got performed. Actions use credits.
Anytime task performs an action (it can be anything from uploading a file to FTP, adding a tag, creating fulfillment etc.) certain amount of credits will be deducted from your credits quota. Credits quota depends on the plan you are on and renews each new billing period.
Last modified 4mo ago