I’m the maker of AppStruct. We’ve published n8n-nodes-appstruct 2.0.1 for working with App Builder projects, tables and records, and I wanted to share a small polling exercise rather than a notification workflow that hides its failure behavior.
The download contains one AppStruct Trigger plus a setup note. It is inactive, has no downstream destination and contains no credentials or project/table IDs. Select a practice table and your own credential before running it.
The useful checks are:
- Run a manual preview: it can show existing rows without changing the live polling baseline.
- Enable the configured workflow and let the first automatic poll establish a baseline; no change output is expected.
- Add one fictional request after that baseline and inspect the next poll.
- Poll again without a source change and check that the unchanged row is not emitted again.
- Test Updated Row separately: after its baseline, change one existing row’s status and inspect that row’s ID and returned values.
Two limits are worth calling out. Reaching the configured Record Poll Limit fails visibly rather than saving a potentially incomplete snapshot. And snapshot polling is not an exactly-once delivery system: intermediate changes can happen between polls, and a later destination failure needs its own replay and deduplication design.
Package and source: GitHub - AppStructAI/n8n-nodes-appstruct: n8n community nodes for AppStruct App Builder projects, tables and records, with a manual first-read workflow. · GitHub
npm: https://www.npmjs.com/package/n8n-nodes-appstruct
Walkthrough, inactive JSON and 13-check acceptance log: n8n Polling Triggers: Test New and Updated AppStruct Rows | AppStruct Blog
Compatibility: self-hosted n8n 2.47.7+ with Node.js 24+, with community packages enabled. It uses an AppStruct account email/password saved in n8n credentials; that account credential is not read-only. Keep returned records and execution history private. This is App Builder data, not the Docs/Sheets/Slides MCP connection.
The published package has GitHub Actions provenance and passed the automated n8n registry scanner. Its Creator Portal review is IN PROGRESS; it is not presented as an n8n-verified or Cloud-available node.
If you try it, the most useful feedback is your n8n/package version, which check differed from the expected result and a redacted error. Please leave credentials and private row contents out of replies.