Business process automation that takes manual work off your team
A new lead, a paid order or a booked appointment sets off the next steps without anyone pressing a button: a WhatsApp message to the customer, a CRM record, an invoice, a task for your team. We build these workflows in n8n or code, and a person steps in only where judgement is needed.
- Built in Netanya, Israel
- n8n or custom code, whichever fits the process
- Failure alerts on every workflow
What is business process automation, and what do we build?
Business process automation connects your tools so that one event (a new lead, a paid order, a booked appointment, a no-show) sets off the next steps without copy-paste: a WhatsApp or email message to the customer, an update in your CRM or Google Sheets, an invoice, a task for your team. DDreamLab, a software company in Netanya, builds these workflows in n8n or custom code, connected to the tools you already use, with alerts so nothing fails silently.
Where is manual work eating into your week?
Leads copied by hand from one system to another
Enquiries come in through your website form, a Facebook ad and WhatsApp, and each one lands somewhere different. Someone copies them into Excel or the CRM in the evening, a few slip through, and the person who wrote on Thursday afternoon hears back on Sunday.
Reminders depend on whoever remembers
Someone on your team calls every client the day before their appointment. In a busy week it doesn't happen, gaps open up in the calendar, and nobody sends the no-show a link to rebook.
Month-end starts with a pile of invoices
Every paid order means issuing an invoice, emailing it and updating the spreadsheet. Then your accountant asks for supplier invoices, and you dig through three inboxes to find them.
An old automation that quietly broke
Someone once set up a Zap or wrote a script. It stopped working after a password change, and nobody noticed until a customer called to complain.
How we automate a process, step by step
Map the manual work
On a call or in a meeting we go through what your team does by hand: who does it, in which system, how often and where things slip. You come away with a ranked list of what to automate first and what is better left manual.
Pick the first workflows
We start with the two or three processes that hurt most, not the whole business at once. For each one we agree what triggers it, what the steps are and what happens when something is missing: a wrong phone number, a customer without an email, a declined payment.
Build and test
We build in n8n or code, connect to your accounts with the minimum permissions needed, and test on sample data and on real past cases. Customer-facing messages are written together with you, in Hebrew, Russian or English, depending on each customer's language.
Run in parallel, then switch over
For the first stretch the workflow runs alongside the manual process, and you compare the results. Only when they match do you hand the work over and stop doing it by hand.
Monitor and support
Every workflow alerts the person in charge when a step fails, and every run is logged. You get plain-language documentation: what runs, where, and how to stop it. After launch you can stay with us for support, fixes and new workflows.
What you get
- A ranked process map: what to automate first and what stays manual
- Workflows in n8n or code, connected to the systems you already use
- WhatsApp message templates submitted for Meta approval, plus automated emails: confirmations, reminders, invoices
- Reminder and follow-up sequences with stop rules, for example when the customer replies or pays
- Failure alerts to the right person, and a log of what ran, when and with which data
- Plain-language documentation: what runs, where, and how to switch each workflow off
Typical scenarios in Israeli businesses
A Facebook lead that doesn't wait until morning
Someone fills in your ad's lead form at 11 pm. The lead goes into the CRM, a WhatsApp welcome goes out in the language they chose (if they agreed in the form to be contacted there), and a task with all the details opens for a sales rep. In the morning the rep starts with a conversation, not a search through messages.
Studio or clinic: fewer gaps in the calendar
The day before an appointment the client gets a reminder with an option to confirm or cancel, and anyone who cancels or doesn't show gets a link to rebook. For clinics we handle booking and reminders only: anything that touches medical information needs a legal check first.
Online shop: from payment to invoice
A paid order creates an invoice in your invoicing system (Morning, for example, through its API), emails it to the customer and adds a row to Google Sheets for your accountant. If something doesn't go through, you get an alert instead of finding out at month-end.
Office: supplier invoices in one place
Supplier invoices that arrive by email are collected into one folder and a sheet organised by supplier and month. Your accountant gets everything in order, and nobody chases files on the last day of the month.
Follow-up sequences over WhatsApp and email
A sequence is a series of scheduled messages that stops as soon as the customer responds: a reminder before an appointment or a payment date, a follow-up on a quote that went unanswered, a note to customers you haven't heard from in a while. A reminder about an appointment the customer booked is a service message. A promotional offer counts as advertising under Israel's anti-spam law (section 30A of the Communications Law), so it goes only to people who opted in beforehand.
- Reminders before an appointment, a payment date or a subscription renewal
- Quote follow-ups: a gentle nudge after a few days, stopped the moment the customer replies
- Re-engaging past customers, only those who agreed to receive marketing
- Marketing messages are labelled as advertising and include an easy way to unsubscribe
- Anyone who opts out is removed from every channel, not just one
n8n, custom code or an off-the-shelf tool?
n8n is a workflow tool where every step is visible on screen. It can run in n8n's cloud or on your own server, and it suits most business processes. When the logic is complex, the volume is high or a system has no ready-made connector, we write code. And when an off-the-shelf tool or a feature already in your CRM does the job, we'll tell you, even if that means you don't need us.
- n8n: workflows that are easy to see, test and change, with a self-hosted option
- Custom code: complex logic, high volumes and systems without a ready connector
- Zapier or Make: when the process is simple and usage-based pricing works for you
- A built-in feature of a system you already have: sometimes that's all you need
Tell us about one task your team does by hand every week, and we'll sketch how it would run as a workflow.
Tools and channels we connect
- WhatsApp Business API
- n8n
- Google Sheets
- Google Calendar
- Gmail
- Facebook Lead Ads
- Morning (Green Invoice)
- PayPlus
- Webhooks
- REST API
If a system has an API, we can usually connect it. If it doesn't, we'll tell you upfront.
How a project with us runs
The same four steps, whether it's a bot, an integration or a whole system.
Short call
You tell us what's slowing you down and how you work today. We ask questions — and if a ready-made tool fits, we'll say so.
Your partDescribe the task in your own words
Written proposal
Scope, stages and a cost estimate in writing, including who owns the code, the accounts and the data.
Your partReview, ask questions, decide
Build in stages
You see working parts early and try them on real cases. Your feedback goes straight into the next stage.
Your partTest and give feedback
Launch and support
We launch, watch how it behaves in real use and stay on for fixes and improvements.
Your partUse it and tell us what to improve
What drives the cost?
- How many workflows, and how complex each one is: steps, conditions, exceptions
- Which systems we connect, and whether they have a documented API
- Volume: how many runs and messages per day and per month
- Where it runs: n8n cloud, your own server, or custom code in the cloud
- WhatsApp messages: Meta sets its own fees by message type, billed separately from development
- How many languages customer messages are written in
- Support after launch: monitoring, changes and new workflows
Every process is different, so the price is set once we understand yours. Call or WhatsApp us at 050-854-2579, tell us what you do by hand today, and we'll come back with a written estimate.
Ownership, privacy and accessibility
Your code and data
Ownership of the code and data is agreed in writing before we start: who owns the source code, the accounts and the information is in the agreement — not something you find out at the end.
Privacy by design
We build with Israel's Privacy Protection Law and Amendment 13 in mind: we collect only what's needed, keep secrets on the server and agree with you where the data is stored.
Accessibility built in
Interfaces built with IS 5568 and WCAG AA in mind: keyboard navigation, contrast, screen-reader labels and right-to-left layouts.
Questions about business automation
How much does business automation cost, and how long does it take?
It depends on how many workflows we build, how many systems are involved, whether they have APIs and how many messages go out. One workflow between two well-known tools is a very different project from a full setup with a CRM, invoicing and WhatsApp. That's why we don't publish a price list: tell us about the process on a call or on WhatsApp, and you'll get a written estimate with scope and timeline.
Can you connect the systems we already use, like Morning, iCount, Priority or our CRM?
Usually, yes, if the system has an API or a data export. Morning, for example, has a documented API; other systems we check before committing. Where there's no API, there are alternatives: data by email, scheduled file exports and, as a last resort, browser automation. We explain the risk of each option up front, because a shaky connection breaks at exactly the wrong moment.
What happens when a workflow breaks or a system changes?
Sooner or later it will: a vendor changes its API, a password gets reset, a customer types a wrong phone number. So every workflow we build alerts the person in charge when a step fails, retries where that is safe, and logs every run, so you can see exactly where it stopped. After launch you can stay with us for ongoing support, or take the documentation and maintain it yourselves.
Who owns the workflows and the data, and what about privacy?
We recommend opening the accounts (n8n, WhatsApp Business, Google) in your business's name, so access stays with you. Ownership of the code and workflows is agreed in writing before we start. We build with Amendment 13 to Israel's Privacy Protection Law in mind: each workflow passes only the fields it needs, each connection gets minimal permissions, and logs don't keep personal data they don't need.
Can you add AI to a workflow?
Yes, as one step inside it: sorting incoming requests by topic, pulling details out of a PDF invoice, drafting a reply. AI can be wrong, so wherever money or a customer is involved, a person approves before anything goes out. When the AI isn't sure, the request goes to a human. If you need an agent that acts on its own inside your systems, that's our AI agents service.
Will customer messages read well in Hebrew? And in Russian or English?
Message texts are written by people, together with you, and you approve each one before it goes live. The workflow picks the language from what it knows about the customer (a CRM field, or the language they wrote in) and sends Hebrew, Russian or English accordingly. WhatsApp templates for messages you initiate are approved by Meta separately for each language; we prepare and submit them.
Which manual task should we start with?
Message us on WhatsApp or call 050-854-2579: what the task is, who does it today and in which systems. We'll suggest how to turn it into a workflow, or tell you honestly that it isn't worth automating.
Tell us about one task your team does by hand every week, and we'll sketch how it would run as a workflow.
Prefer to talk? Call050-854-2579