Skip to content
SPEIA

Automation

What your tools do on their own, every day.

A useful automation is a written rule that runs at a fixed time and gets noticed when it stops. Here are the ones in service — in our clients' tools and on our platform.

In short

  • Stock and expiry alerts every morning at 8 a.m.
  • Receipts issued on payment
  • One backup per application, every night
  • Monitoring every 5 minutes

Facts checked on 11 November 2026.

At our clients

In the tools in service.

Each line links to its reference: the context, what was delivered, the technologies.

  • Alerting before the shortage

    Every morning at 8 a.m., an e-mail lists low stocks and products close to expiry.

    ODS Logistique
  • Reminding without thinking about it

    Every morning at 9 a.m., the training extranet sends its automatic reminders.

    AGIR 93 extranet
  • Issuing the receipt on payment

    The receipt is issued as soon as the rent is collected; rent calls are launched in batches; the INSEE revision indices are tracked automatically.

    Odimo
  • Expiring, initialling, purging

    In our management tool: an overdue quote expires on its own, the pages of a contract signed online are initialled automatically, and connection traces older than twelve months are purged every night.

    Gestion SPEIA
  • Producing the document

    Delivery notes, receipts, contracts, invoices, accounting exports: generated by the tool, not retyped by hand.

    All references
  • Reading for you

    When a rule is no longer enough — reading a scanned invoice — AI takes over, under control.

    AI in your tools

In-house

On the platform that hosts your tools.

What we no longer do by hand, because a repeated gesture ends up being forgotten.

  • Monitoring

    Every 5 minutes, each address in service is checked. Two failures in a row trigger an alert; a message confirms the return to normal; a summary goes out every morning at 8 a.m.

  • Backing up

    Every night, one backup per application, kept for 14 days. A backup more than 26 hours old triggers an alert.

  • Going live

    One command: the candidate version is built, started alongside the one in service, checked, then put into service. If a step fails, the old one comes back on its own.

    Hosting & support
  • Creating a project

    One command creates the repository, the preview address, the certificate, the monitoring and the first deployment. It can be re-run without breaking anything.

  • Renewing certificates

    HTTPS certificates renew on their own; an alert goes out if one of them has fewer than 14 days left.

  • Checking what is left to do

    A pending action carries, whenever possible, its automatic check: it is replayed every morning, and the line is removed once it is done.

Method

How we automate.

  1. Code first, AI second

    Every automation listed here is a programmed rule. A model only steps in to read free-form content.

  2. It gets noticed when it stops

    Scheduled jobs and backups are monitored: one that stops running triggers an alert.

  3. Replaying doubles nothing

    A message relayed by our platform carries a key: replaying it does not send it twice.

  4. The decision stays human

    An automation prepares, warns, produces. What commits you — approving a quote, signing, paying — remains a person's gesture.

FAQ

Frequently asked questions

What can be automated in a small business?

Whatever is repetitive and governed by a rule: follow-ups, reminders, threshold alerts, recurring documents, exports. We start from the way you work, not from a catalogue.

Do you need AI to automate?

Rarely. The automations in service listed on this page are all programmed rules. AI is useful when free-form content must be read — a scanned invoice, a letter.

What happens if an automation stops?

It is monitored: a scheduled job that stops running or a missing backup triggers an alert.

What if we started from the way you work?

One first conversation is enough to know whether SPEIA can help.