Process automation

The problem

Every week, the same gestures: chase unanswered quotes, prepare the Monday report, create a folder for each new customer, tell the team when a form has been filled in. These are simple rules executed by humans.

What I do

I write the rule down with you, then have it executed by an automation tool (Make, n8n or Zapier depending on your environment) or by a script when the tool is not enough. You stay in control: every scenario is readable, editable, and you know how to stop it.

A rule written in black and white: what triggers it, the condition, the actions. Cases that need judgement go to a person instead of being guessed.

Real examples

• Notion

  A completed HubSpot form creates the contact, assigns it to the right salesperson by region, notifies the Slack channel and opens the follow-up page in Notion.

• 

  Pennylane invoices overdue by 7, 15 and 30 days trigger three Brevo reminders in different tones, then a task for the person in charge.

• Notion

  The weekly report is assembled by Make on Monday at 7 a.m. from three Notion databases and posted in Slack, without anyone opening a file.

• 

  A new customer in Odoo triggers, through n8n, the creation of the shared folder, the Slack channel and the kick-off invitation.

Questions about this service

Make, n8n or Zapier: which one?

The one that fits your environment: Zapier if you already have it and volumes are low, Make for most SMEs, n8n if you want to host it yourself. The quotation explains the choice and its monthly cost at the publisher.

Can I change a scenario myself?

Yes. That is why each one is built to be readable, with named steps and a written rule next to it. The training session covers exactly that.

What happens when a scenario fails at night?

It retries, then sends an alert with the step that failed and a link to rerun it. Nothing is silently lost.