We would rather hear about a problem than leave it on the site. This page is the route for corrections, outdated or broken sources, accessibility issues, privacy requests, and considered technical feedback on anything we have published about n8n, Make, or Zapier.
How to reach us
Write to the editorial team at contact@metaflowkit.com.
Contact method: email only. MetaFlowKit does not currently use a contact form. Email is the channel for everything described on this page.
We read what arrives and act on substantive reports, but we do not promise a response time and we cannot reply to every message individually. Correction reports and accessibility issues are prioritised over general enquiries.
Reporting a correction
Automation platforms change their interfaces, limits, and pricing without notice, so pages drift out of date. A short, specific report is far more useful to us than a general note that something looks wrong. Where possible, include:
- The page URL on this site where the problem appears.
- The disputed statement, quoted or described closely enough that we can locate it on the page.
- The current primary source that contradicts it — official platform documentation, release notes, a status page, or the product interface itself.
- The relevant date or version, such as the platform version, plan, region, or the date you observed the behaviour.
That last item matters more than it looks. Two people can both be right about a platform’s behaviour and still disagree, because they are on different plans, versions, or regions. A date and version usually resolves it quickly.
Material errors are corrected and meaningful changes are recorded, as set out in our Editorial Policy. The standards we apply to evidence are described in our Source Policy.
What not to send us
Please do not send credentials or sensitive records. That includes passwords, API keys and tokens, webhook URLs or signing secrets, OAuth client secrets, database connection strings, private customer or employee records, health information, and payment or card details.
If you need to show us a workflow, an execution log, or an error message, redact the sensitive values before sending. Placeholder text in place of a real key is fine and does not reduce how useful the report is. If you have already sent something sensitive, rotate the affected credential on the platform side rather than waiting for us.
Privacy and accessibility
Privacy questions and requests relating to information handled by this site can be sent to the same address. How we handle information, and which requests we can act on, is described in the Privacy Policy.
If a page is difficult to use with a screen reader, keyboard, or magnification, tell us which page and what failed. Accessibility reports are treated as defects, not suggestions.