Guides

Notify the warehouse only when orders leave tomorrow

A daily check that costs you nothing on quiet days: it searches, counts, and only notifies if the list is not empty.

Before you start

This is the template "Orders leaving tomorrow". You fill in two blanks: the Slack channel and the role to notify. It runs every morning at 08:05, Europe/Madrid. The texts a template writes (messages, task titles, email bodies) are in Spanish as the catalog has them: edit them to your language before you go live.

The template's reference page, with its trigger, steps and requirements: Orders leaving tomorrow.

#StepSetting
TriggerScheduledCron 5 8 * * *, time zone Europe/Madrid.
1«Adjust date»Date = Today, add 1 day. Publishes tomorrow's date.
2Find ordersStatus reserved, starting from tomorrow and until tomorrow (the same day in both).
3«Set variable»Name "Orders leaving tomorrow". Value: the Length function applied to the list of orders.
4«Condition»The list of orders has at least one item. The Else lane is empty.
5«Internal notification»In Then. Style neutral, to a role. Message: the count, with a prompt to check preparation.
6«Post a message»In Then. The count, to the channel you pick.
  1. Start from the template

    «New workflow», «Start from a template», "Orders leaving tomorrow".

  2. Check the time

    Click the trigger. The «Time zone» is written into the template as Europe/Madrid, whatever your company's zone is. Change it if needed.

  3. Fill in the blanks

    Pick the role of «Internal notification» (the people who will see the notification) and the Slack channel.

  4. Test it

    A scheduled workflow has no Run button. To see it work before tomorrow morning, make a reserved order that starts tomorrow, then move the cron to the next minute, publish, and watch the run. You need both: an order without the cron change runs nothing, and the cron change without an order ends quietly after the search. Put the cron back afterwards.

  5. Publish and activate

    «Publish and activate».

  • The workflow searches first and notifies only if the result has at least one item. With no orders, the run ends after step 4, and costs the credits of the steps that ran, not those of the notifications.
  • The dates come from Today, never typed in. A date typed in would be right for one day only.
  • The search returns up to 100 orders, so the count in the message tops out at 100.
  • Compare it with the template for overdue returns, which does the opposite on purpose: it posts a Neo summary every day, even with no delays, while "Orders not returned on time" stays quiet unless there are some.
Tip:

The same pattern is used for overdue tasks, invoices past due, quotes about to expire, low stock and vehicle inspections: change what you search for and the sentence.

Note:

Counting uses the Length function in a Set variable step. If you need the count to appear in two messages, use that variable in both.

  • Build

    Triggers

    A trigger decides when a workflow runs. Every workflow has exactly one, and you can change it in the editor at any time (until you publish, nothing changes for the runs).

  • Build

    Data and expressions

    You do not write formulas in a workflow. You pick values from lists, and Filmo stores what you picked as a structured expression. This page explains what the picker offers and how the values behave when the run executes.

  • Build

    Conditions and operators

    A condition compares one variable with one value. The Condition step sends the run down one of two paths; the Switch step picks the first of several.