Skip to content
Checkout.com logoWedof logo

Connect Checkout.com to Wedof

Move data between Checkout.com 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.

Checkout.com triggers
2
Checkout.com actions
7
Wedof triggers
28
Wedof actions
45

Automation ideas

What you can build with Checkout.com and Wedof

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

  • Payment Events in Checkout.com creates Lister les statistiques des partenaires in Wedof

    Trigger order fulfillment when payment is approved.

  • Nouveau dossier de formation in Wedof creates Create Customer in Checkout.com

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

  • Payment Events in Checkout.com creates Récupérer un dossier de formation in Wedof

    Trigger order fulfillment when payment is approved.

  • Nouveau dossier de formation in Wedof creates Update Customer in Checkout.com

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

  • Payment Events in Checkout.com creates Rechercher un ou plusieurs dossiers de formation in Wedof

    Trigger order fulfillment when payment is approved.

  • Nouveau dossier de formation in Wedof creates Create Payment Link in Checkout.com

    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 Checkout.com 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.