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.
kartik-mem0
84a1318f71