84a1318f71
Both pages opened with an endpoint table and left the reader to work out setup themselves. Restructure them the way the stronger integration pages read: problem statement, prerequisites with API-key links, a Steps-based setup with a verification callout, a runnable quickstart, then the field reference, then troubleshooting. Every documented field is checked against the source rather than a schema: the Zapier action input fields come from src/creates and src/searches, and Wait for Completion is correctly documented as off by default there (it is on by default in n8n). Adds the n8n self-hosted-only prerequisite and the Zapier App Directory availability note, both of which users hit first.
Mintlify Starter Kit
Click on Use this template to copy the Mintlify starter kit. The starter kit contains examples including
- Guide pages
- Navigation
- Customizations
- API Reference pages
- Use of popular components
Development
Install the Mintlify CLI to preview the documentation changes locally. To install, use the following command
npm i -g mintlify
Run the following command at the root of your documentation (where mint.json is)
mintlify dev
Publishing Changes
Install our GitHub App to auto-propagate changes from your repo to your deployment. Changes will be deployed to production automatically after pushing to the default branch. Find the link to install on your dashboard.
Troubleshooting
- Mintlify dev isn't running - Run
mintlify installit'll re-install dependencies. - Page loads as a 404 - Make sure you are running in a folder with
mint.json