A Hebrew dashboard is a control panel where headings, dates and amounts read right to left, in the format an Israeli team reads without effort, and which refreshes automatically from the business’s own systems. What separates it from an ordinary dashboard is less the charts and more the details: text direction, date format, the shekel sign and field names.
Those details look minor, but they decide whether managers trust the dashboard or keep asking for “that thing in Excel”.
What is different about a Hebrew dashboard compared with an English one?
A Hebrew dashboard differs from an English one in four areas: reading direction (right to left), date and number formats, the language of labels and field names, and how mixed Hebrew and English text is handled. The charts and calculations are the same. What suffers when these details are ignored is trust: a manager who sees a reversed date or a currency sign in the wrong place stops believing the numbers.
A dashboard exists to replace a question that keeps coming back, such as “where are we this month?” or “how many tickets are open?”. If the reader has to decode the screen to get the answer, the dashboard is not doing its job.
How do you make a dashboard display correctly right to left?
To make a Hebrew dashboard display correctly, set right-to-left direction for the whole page or sheet, not as a fix applied cell by cell or card by card. The layout should follow: the most important column of a table on the right, and the main filter in the top-right corner, where the eye starts.
A few traps come up again and again:
- Mixed text. A name like “Order #1042 - Acme” makes punctuation jump to unexpected places. The simple fix is to put identifiers and English names in a column of their own.
- Fonts. A font without Hebrew letters is silently replaced by another font mid-cell, and the screen looks uneven. Choose a font with full Hebrew support.
- Time axis in charts. Check whether the time axis runs right to left or left to right, decide deliberately, and keep it consistent across the dashboard.
The only reliable test is real data: load actual customer names, including ones with quotation marks and hyphens, and see what happens.
How do you show dates, shekels and numbers in the Israeli format?
An Israeli dashboard shows dates as day-month-year, amounts in shekels with the ₪ sign and a thousands separator, and decides in advance whether amounts are shown before or after VAT. These decisions are made once, in the data layer, so every card and chart shows the same thing.
A few things worth fixing up front:
- A date stored as a real date. The date 03/04 reads differently in the United States and in Israel. When a date is stored as a date rather than as text, sorting and filtering work correctly in every view.
- The working week. In Israel the week starts on Sunday. A dashboard that summarises “by week” must say so explicitly.
- Holidays. If the business is affected by seasons and holidays, mark them on the timeline so a dip in a given month is not read as a problem.
- Foreign currency. If there are invoices in another currency, keep the original currency and the date of the exchange rate next to the shekel amount.
Where does the dashboard’s data come from, and how does it refresh?
A Hebrew dashboard refreshes automatically when an n8n workflow pulls the data from the source systems, cleans it, and writes it to a single place the dashboard reads from. The sources can be a CRM, an invoicing system such as Morning (Green Invoice), Google Sheets, or website forms. The workflow runs on a schedule you set, for example hourly or once a day, depending on what the business decision requires.
This is where most of the real work happens, and where the Hebrew comes in. Different systems record the same thing in different ways:
- Statuses such as “חדש”, “בטיפול” and “New” have to be mapped to a single list.
- Phone numbers arrive in different formats, and are unified before customers are counted.
- The same customer’s name is written two ways, and you decide which field is the identifier.
Without the cleaning step, the dashboard will display wrong numbers beautifully.
Which type of dashboard suits my business?
A business can choose among four types of dashboard: a Google Sheets spreadsheet, a BI tool connected to a database, a custom-built web page, or a daily summary in a WhatsApp message. The choice depends on the number of data sources, the number of people viewing, and whether they need to filter and drill into detail.
| Dashboard type | Suits you when… | What to check in Hebrew |
|---|---|---|
| Google Sheets spreadsheet | One or two data sources, a small team, and a need to start quickly | Sheet direction, font, date format |
| BI tool over a database | Many sources and many viewers, with filtering and drill-down | Right-to-left support in every component type, tested on real data |
| Custom web page | You need a distinctive look or per-user permissions | Full control over design, with maintenance as your responsibility |
| WhatsApp summary | A manager wants a few numbers in the morning without opening a system | The Hebrew wording of the message and the send time |
In most cases you start with the smallest option that answers the questions. Once the data is already clean and refreshing on its own, moving to a heavier tool only swaps the display layer.
Which metrics belong on the dashboard?
A business dashboard shows the metrics that lead to a decision, not everything that can be measured. Give each role a handful of metrics, and write one definition in Hebrew for each, so everyone understands it the same way.
Examples to start from:
- Sales: new leads, leads in progress, deals closed.
- Service: open tickets, tickets that have been waiting longest.
- Finance: invoices issued, invoices not yet paid.
A definition such as “a new lead is an enquiry that came in during the last 24 hours and has not been answered” prevents arguments later. A metric without a written definition will be interpreted differently by each manager.
What happens when a data source goes down or changes?
When a source system goes down or changes structure, a well-built dashboard does not quietly keep showing old data. It displays the time of the last successful update, and the n8n workflow sends an alert about the failure to whoever is responsible. Without that, the dashboard keeps showing numbers that look fine and are out of date, which is the most expensive mistake.
For that reason every workflow gets error handling: a retry, and if it fails, an alert by email or WhatsApp. Simple checks are added too. If zero rows were pulled from a source that normally returns rows, or a field the mapping depends on has disappeared, that is a signal to stop and investigate. This is how we build monitored automations in environments with security and regulatory requirements, and the same approach fits a small business dashboard.
How long does it take to set up a Hebrew dashboard?
Setting up a Hebrew dashboard depends mainly on the number of data sources and the quality of the data in them, and less on the design. A dashboard over a single clean source can be stood up quickly. A dashboard that unifies several systems with inconsistent data first needs metric definitions and data cleaning.
The right order is: define which questions the dashboard answers, connect the sources, clean and unify, build the display, and finally add monitoring and alerts. The setup steps themselves are covered in the guide to setting up a BI dashboard.
If you would rather have it built around your business, including the connections, the monitoring and the Hebrew, the details are on our page for automated reporting and BI.
Frequently asked questions
Can I receive the dashboard on WhatsApp instead of opening a link?
Yes. An automated workflow can send a daily summary of a few metrics as a WhatsApp message through the WhatsApp Cloud API. A message the business initiates outside the service window must be sent as an approved template, so the summary is built as a template with variables the workflow fills in each morning. It should go to recipients who have agreed to receive it.
Do I need a developer to build a Hebrew dashboard?
A simple dashboard over a Google Sheets spreadsheet can be put together without a developer. The real difficulty is not drawing the charts but the data layer: connecting the sources, unifying statuses and definitions, and monitoring that alerts you when something breaks. The more sources there are, the more it is worth having someone who understands automation run that layer.
How do I control who sees which data in the dashboard?
Split the view by role and do not share the raw data sheet with everyone. Each user gets only the summarised view relevant to them, and sensitive data such as salaries or customers' identifying details stays outside the dashboard. This is the same least-privilege principle used in banking systems.
What is the difference between a dashboard and a monthly report?
A monthly report is a snapshot sent at the end of a period, while a dashboard answers the question "where are we right now" at any moment. Many businesses need both. When the data layer is built properly, the same source feeds both the dashboard and the report, and nobody has to assemble the numbers again each month.