An on-demand API replaces Make to connect Supabase, Airtable and WeWeb.
Loading...
Loading...
I map processes, define rules and automate exchanges between your business tools.
Response within 24h. No sales follow-up if it's not the right time.
Before automating, we identify triggers, data, owners and exceptions in the process.
Depending on the need, an on-demand API or existing orchestration may suffice. Errors, retries and processing visibility are part of the design.
Two projects illustrate this work on operational processes.
Make connecting Supabase, Airtable and WeWeb
Replaced with an on-demand API hosted on Railway
Cost went from €20/month to a few cents/month for equivalent usage
Customs fee collection at DHL Express NC
Fee calculation, online payment and notifications
Approximately €30k and 250 transactions per week in typical activity
An on-demand API replaces Make to connect Supabase, Airtable and WeWeb.
Customs fee calculation, online payment and parcel tracking.
Identify users, decisions to support, available sources and business constraints.
Define scope, acceptance criteria, access rules and cases requiring human review.
Build incrementally, test failure scenarios and document decisions with the teams.
Prepare go-live, usage monitoring and the measurements needed to evaluate benefits.
This depends on existing interfaces and constraints. I start by mapping exchanges to identify what can be connected and what needs to change.
The mechanism follows the need. In the middleware shown here, Make was replaced by an on-demand API, without a cron job or triggering webhook.
We define failure cases, possible retries and data checks. Structured logs help locate failed processing and organise recovery.
An AI use case to scope, an assistant to integrate or a BA assignment to support? Let’s discuss your needs.
Response within 24h. No sales follow-up if it's not the right time.