Our documentation pages
Every app on WEXTL gets a documentation page at /apps/<app>/docs that follows the same shape. That consistency is deliberate — once you know how to read one app's page, you know how to read all of them. The sections are:
- Requirements
- Get your credentials
- Connect the app in WEXTL
- node modules
- Templates
- Explore alternative apps
- References
Sources we compile from
Each page is authored from three sources, not written from scratch by hand: our own integration code, our internal integration specs, and the vendor's own official API documentation.
Every field name, module name, input/output shape, and connection requirement shown on a docs page comes directly from one of these:
- Our internal integration source code — the actual module and connection definitions WEXTL runs when you use the app.
- Our internal integration specs — the structured parameter, scope, and authentication metadata each integration ships with.
- The official vendor API documentation — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
Where AI helps
AI technologies help draft the connecting prose — the About paragraphs, section lead-ins, and the plain-English summary of what a connection requires. The field labels, help text, module names, types, and every link are authored data pulled straight from the sources above, never generated. The prose can occasionally be imprecise; the underlying data it describes is not.
How we validate
Every WEXTL apps documentation page is human-authored, not generated. Field names, module names, input and output shapes, connection requirements, and scope lists are compiled directly from our own integration source code and our internal integration specs, then cross-checked against the vendor's official API documentation. That's why the same field on the same module reads the same on our /apps/<app>/docs pages as it does inside the workflow builder: it's the same data, not a paraphrase.
The connecting prose — the section lead-ins, the plain-English summary of what a connection requires, and the disclaimer at the top of every page — is drafted with AI assistance. The underlying data it describes is authored, verified, and served straight from those three sources, so the prose can occasionally be imprecise while the field-level content it wraps around is not.
When we link to a vendor's own documentation, we periodically re-check the link against the vendor's current site so it keeps pointing somewhere useful.
Reporting mistakes
Spotted something wrong — a stale field, a broken link, a step that no longer matches the vendor's UI? Use the in-app support/feedback option (or your account's support channel) to flag the app and page; we prioritize documentation fixes the same way we prioritize integration bugs.