Skip to content
DIMO logoWedof logo

Connect DIMO to Wedof

Move data between DIMO and Wedof the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

DIMO triggers
9
DIMO actions
38
Wedof triggers
28
Wedof actions
45

Automation ideas

What you can build with DIMO and Wedof

A few flows teams run between DIMO and Wedof. Use one as a starting point, or build your own from scratch.

  • Battery is Charging Trigger in DIMO creates Lister les statistiques des partenaires in Wedof

    Triggers when vehicle battery charging status changes (True/False).

  • Nouveau dossier de formation in Wedof creates Attestation : Create VIN VC in DIMO

    Se déclenche lorsqu'un nouveau dossier de formation est créé (non traité)

  • Battery is Charging Trigger in DIMO creates Récupérer un dossier de formation in Wedof

    Triggers when vehicle battery charging status changes (True/False).

  • Nouveau dossier de formation in Wedof creates Device Definitions : Decode VIN in DIMO

    Se déclenche lorsqu'un nouveau dossier de formation est créé (non traité)

  • Battery is Charging Trigger in DIMO creates Rechercher un ou plusieurs dossiers de formation in Wedof

    Triggers when vehicle battery charging status changes (True/False).

  • Nouveau dossier de formation in Wedof creates Device Definitions : Lookup in DIMO

    Se déclenche lorsqu'un nouveau dossier de formation est créé (non traité)

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in DIMO and acts in Wedof, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.