What record does your process actually leave? Ten questions to ask
Choosing an automation tool from its feature list is like choosing a car by the length of its brochure. The questions that matter only surface the day somebody asks you to account for something.
Here is the grid we would use in your place. It ranks no tool — it gives you what you need to question them, including us.
A correction, first
You sometimes read that mainstream automation platforms do not keep successful runs. That is false. Zapier, Make and n8n all document an execution history that includes successes, with timestamps and step-by-step detail.
So the right question is not “is there a history”. It is: what does it contain, for how long, and can you hand it to a third party in a form they can understand?
The ten questions
1. Where are the data and the backups processed?
The answer should be a city, not a country, and it should cover backups and disaster recovery too. Some platforms fix the region when the organization is created, with no way to change it afterwards — check before you create the account, not after.
2. Does a successful run leave a file someone can read?
Not just a technical log: a record someone other than you can open and understand.
3. What data is kept, masked or excluded?
Some platforms offer a confidential mode that keeps the fact of the run without the payload. That is useful — and it is also a loss of information to accept knowingly.
4. For how long, and on which plan?
Retention varies sharply between plans at every vendor. An answer that does not name the plan is not an answer.
5. Can an action be tied to a person, a rule, an approval and a version of the process?
This is the question that separates a technical log from supporting evidence. Knowing an action happened says nothing about who authorized it, or against which version of the procedure.
6. Can you export a readable file without administrator access?
The day your legal advisor, your insurer or a professional order asks to see, they will not be issued credentials.
7. Does a replay clearly distinguish the original from the new attempt?
Recovery after an incident is when duplicates are born. Ask to see a real replay, not a description.
8. Who operates the infrastructure, and who answers for backups and incidents?
Self-hosting gives control of the instance and transfers the responsibilities: encryption, updates, backups, monitoring, pruning policy. It is a legitimate choice — not a saving.
9. How is usage billed, and what happens on overage?
Tasks, credits, executions: the units differ and do not compare directly. Ask for the cost of 100, 1,000 and 10,000 files in your scenario.
10. Have the claims been verified in a comparable configuration?
Ours included. A performance claim must rest on adequate testing done beforehand — that is what section 74.01 of the Competition Act requires, and it is also simply honest.
What we do not claim
We will not claim to be the only tool offering an audit trail: that would be false. We will not publish a quantified comparison with these platforms until we have run the same control process in each, with plan, region, settings and screenshots documented.
What we believe we can demonstrate — and will document before asserting publicly — fits in one sentence: automation platforms mostly document technical execution; we aim to organize the business-process file and its supporting evidence. Until the comparative test is run, that is an intention, not a fact.
Our own answers to questions 1, 3 and 4 are published in our privacy policy. Ask us the other seven.
Probaro does not guarantee compliance with any law or standard. This article provides general information as of the date shown; it is not legal advice and does not replace analysis by a qualified advisor who knows your situation. Characteristics of the third-party products mentioned come from their public documentation consulted on 21 August 2026 and may change. We have no affiliation with those vendors.
Frequently asked questions
Do Zapier, Make and n8n keep successful runs?
Yes. All three document an execution history that includes successes, with timestamps and step-by-step detail. Retention and level of detail vary by plan and settings.
Where do these platforms host data?
Per their public documentation as of 21 August 2026: Zapier states it provides its service from servers in the United States unless otherwise agreed; Make has the organization choose a United States or European Union region at creation, with no change afterwards; n8n Cloud states infrastructure in the European Union, and self-hosting leaves the choice to the customer.
Does self-hosting guarantee data stays with you?
No, not on its own. You control the instance, but processes generally call third-party services, and the installed edition may transmit licensing or telemetry data depending on its configuration.
Sources