-
The model that stopped existing
The code did not change. The key changed. And a model that the provider still listed as available turned out to be available to nobody new.
Read it → -
Your privacy policy is part of the codebase
Nobody edited the privacy policy. The software moved, and three sentences in it became false.
Read it → -
Knowing a flow did the right thing
Completion and correctness are two different claims, and most automation tools only measure one of them.
Read it → -
Someone else's automation runs with your credentials
Exporting a flow is safe. Importing one is a different question, and the asymmetry is easy to miss.
Read it → -
Webhooks arrive out of order
The events describe a sequence. The delivery does not preserve it. Build for the second fact, not the first.
Read it → -
The build that succeeded at nothing
Every deploy was green. The site was up. The content was three days old. Nothing errored, because nothing ran.
Read it → -
How to run a script on a schedule without a server
The twenty-line script is never the work. Six questions the code does not answer, and four honest ways to answer them.
Read it → -
The flow that ran and did nothing
A flow that errors gets fixed within the hour. A flow that succeeds at nothing runs for months.
Read it → -
If it only runs while a tab is open, it is not automation
Browser-only execution is a real trade, not a lesser product. Here is what each side of it actually costs.
Read it → -
Testing row-level security for what should fail
Restrictive mistakes break the demo. Permissive mistakes break nothing at all, which is the problem.
Read it → -
Merchant of record vs payment gateway, for Indian software businesses
A gateway moves the money and hands you the compliance question. An MoR takes the liability. The difference matters more than the fees.
Read it →
Flows that run without youScheduled workflow automation on our servers, not in a browser tab. 51 connectors, visual builder, free tier included.
Open the app