↑↓ selectEnter openEsc close

    1. Elbuz

    How to combine price lists, catalog and export in one flow

    4 min readUpdated

    Elbuz chains several operations: imports price lists, updates the catalog, exports products to chosen marketplaces and sends a summary. The chain starts with a button, on a schedule or on an event.

    When you need this:

    • Update prices for Rozetka and Prom every morning — the ready-made flow does it in your order.
    • See where it stopped — the “Execution log” shows each block's status and totals.
    • Another system starts processing — the flow starts on an event, like an API-created document.
    • Call the customer after an order — the “AI call” block calls and explains why.

    Where to start: Directories → Flows → “From template” → “Activate”.

    What a flow can do

    How a flow differs from a schedule

    The “Flows” window combines several operations into one chain: every morning, import price lists from all suppliers, update the base catalog, export products to Rozetka, Prom or your site, and send a notification with a summary. Steps are blocks on the diagram; the order is set by the arrows between them.

    The start block decides when the flow begins: “Manual trigger”, “Schedule” or “On event”.

    Flows window with the “Ready-made flows” dialog open on the supplier price list card
    1Ready-made flow card
    2Activate button
    1. From template — opens the list of ready-made flows.
    2. The card “Load supplier price lists and update site/marketplaces” with its description: import, catalog update, export, notification.
    3. Activate — creates your own copy of the flow.
    4. Blocks palette — the building blocks for flows, visible behind the dialog.

    The “Processing price lists” schedule can also do “price lists → catalog → export” with two switches (night chain). The difference is what gets exported: the schedule generates all enabled templates, while in a flow you decide which templates to export and in what order, and you see the progress of each step.

    How to set up the ready-made “price lists → catalog → marketplaces” flow

    1. Open Directories → Flows and click “From template”. In the “Ready-made flows” window, on the “Load supplier price lists and update site/marketplaces” card, click “Activate”. A copy of the flow opens on the diagram and appears in the “My flows” list. Clicking “Activate” again doesn't make a second copy; it opens the existing one: “This flow is already activated — opened the existing one”.
    2. The copy's diagram: “Manual trigger” → “Import price lists” → “Update base catalog” → “Export” → “Notification” → “End”.
    3. Click the “Import price lists” block. In “Properties” on the right there's the “Supplier (0 = all)” field: 0 imports price lists from all suppliers.
    4. In the “Export” block, choose an “Export template”. One block, one template. For Rozetka and Prom, add two “Export” blocks in a row, each with its own template, or one “Export all templates” block. A block without a template doesn't fail; it's skipped with the entry “Export skipped — no export template selected”.
    5. To make the flow run every morning on its own, replace the start block. Drag the “Schedule” block from the “Blocks” palette, delete “Manual trigger” (a diagram can have only one trigger, otherwise you get “More than one trigger — keep one”) and connect the new start to “Import price lists” with an arrow.
    6. In the “Schedule” properties, fill in “Schedule (cron)”: the default 0 3 * * * means every day at 03:00, 0 6 * * * means every day at 06:00. “Next run” with a date and time appears below the field; an invalid expression shows “Invalid cron expression”.
    7. In “Flow settings”, check the “Flow is active” toggle and click “Save”. A disabled flow isn't started by the schedule or by events — only a manual run works. A new flow built from scratch is saved disabled.

    “Check” validates the diagram before a run: “Schema is valid” or a list of errors — no start block, an unconnected block. “Run” starts the flow at once, without waiting for the schedule. Progress is in the “Execution log” at the bottom: each block's status and totals — records in the price lists, products added and updated, products exported.

    How to make a flow call a customer

    The “Actions” group of the palette has the “AI call” block: a voice AI employee calls the customer and says why it's calling. Its properties are “Call purpose” (what to say or find out, in your own words), “Customer (contact ID)” (usually “On event → Contact ID”), “Source document (ID)” and “Number (if not from the card)”.

    The number is taken from the “Number” field or from the customer's card. If an order is specified, Elbuz adds its number, status, payment, delivery and to the purpose.

    The block succeeds when the call has gone out or, outside calling hours, has been queued. In that case the “Queued until working hours” output equals 1, and the call goes out when working hours begin.

    The block fails if no outgoing line is set up or the customer has no phone number. The flow doesn't wait for the call's outcome: the summary goes to the call log and “Pulse”. The line, the hours and ready-made purpose texts are described in the article about the voice AI employee.

    Scenarios

    Import price lists every morning and export to Rozetka and Prom

    What to turn on. Activate the ready-made flow. In “Import price lists”, leave “Supplier (0 = all)”; in the “Export” block, choose the Rozetka template and add a second “Export” block with the Prom template. Replace “Manual trigger” with “Schedule” set to 0 6 * * *, turn on “Flow is active” and save.

    What you get. Every day at 06:00, price lists from all suppliers are imported, the catalog is updated, and exactly these two templates are generated, one after the other. The summary arrives as a notification.

    An external system needs to start the flow

    What to turn on. The “On event” start block. The external system creates a document or a contact via the (api/scope/add), and an automatic rule for that event with the “Run flow” action starts the flow. You create the rule from the document or contact list: header menu → “Automatic rules” (how to set it up).

    What you get. The document data is available to the flow's blocks as outputs of the “On event” start block.

    What to do when you see “Flow is already running”

    One flow can't have two runs at the same time. While the previous run has the “Running” status, “Run” replies “Error: Flow is already running”, and the window picks up that run and shows it in the “Execution log”. A scheduled run in this situation is skipped until the next time the schedule matches.

    • The run is alive but long. Check in the “Execution log” which block it's on: a large price list import takes a while, and that's normal. Wait for it to finish or click “Stop”. Stopping takes effect between blocks: the current block finishes, the next ones don't start, and the run gets the “Stopped” status. The button stops a run you started yourself with “Run”; it doesn't stop a scheduled run or one started by a colleague.
    • The run has been “stuck since morning”. Elbuz treats the start of the next block as a sign of life. If more than 30 minutes have passed since the current block started, the background job queue watchdog marks the run as an error with the entry “Run marked as error: no signs of life for over 30 minutes (process interrupted)” and releases the lock — after that “Run” works again.
    • The lock is held longer than 30 minutes. The watchdog runs together with the job queue worker, which starts every minute — but only if the previous worker has already finished. While a long background job is running, such as product enrichment, the every-minute starts are skipped.

    The watchdog counts 30 minutes from the block's start, not the last log line. An “Import price lists” block loading all suppliers for over 30 minutes is marked as failed mid-import, and the next run can start on top of it. For slow imports, split suppliers across several “Import price lists” blocks with different “Supplier (0 = all)” values.

    FAQ

    Can I start a flow with an incoming webhook — a URL another system sends a POST to?

    There is no incoming webhook, but API v2 starts a flow: POST /api/v2/flows/{flow_id}/run with a key that has access to the flows window (API). The flow is placed in the background job queue, and the response returns job_id. Another way is to create a document or a contact via the API, and an automatic rule with the “Run flow” action will start the flow.

    Can a flow send a POST to a third-party service on its own?

    An outgoing is available only as the “Call webhook” tool in the AI agent block.

    A scheduled flow doesn't start, but the button works. Why?

    The “Flow is active” toggle is off: the schedule and events don't start such a flow. A new flow built from scratch is saved disabled.

    Can I stop a run that started on a schedule?

    No, the “Stop” button stops only a run you started with “Run”. The watchdog clears a stuck scheduled run after 30 minutes without signs of life.

    How many copies of a ready-made flow can I activate?

    One. Clicking “Activate” again opens the existing copy with the message “This flow is already activated — opened the existing one”.

    Where to find it and who has access

    Menu
    Directories → Flows — the “Flows” window
    Access right
    the “Flows” window in group permissions; without it, saving, running and stopping don't work
    Prepare
    configured price lists and export templates

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free