Connect AppStruct to n8n.
Start with one verified read.

A SMALL FIRST CHECK

Manual trigger → list your AppStruct projects.

The starter uses the community node’s project-list operation. Run it when you are ready, then compare the returned id and projectName values with your Apps library. There is no email, Slack notification or third-party webhook in this example.

If your library is empty, an empty result can be correct. Create a separate practice app in AppStruct, run the workflow again and check that its name appears. A successful node execution with the expected project is a useful connection check; importing the file alone is not.

01 · INSTALL THE COMMUNITY PACKAGE

Use an n8n instance that permits npm community nodes.

Your n8n administrator needs to allow community packages. Follow n8n’s installation guide and install the package named below. An administrator may need to restart the instance after installation.

n8n-nodes-appstruct

Review the AppStruct node source and package instructions before installing. Community nodes run inside your n8n instance and use its network access. This walkthrough covers the npm installation route on self-hosted n8n; it does not imply an official n8n partnership or a verified Cloud listing.

02 · IMPORT, CONNECT, CHECK

Keep account credentials in n8n’s credential store.

1. Import the starter JSON. Use the workflow editor’s import-from-file option. Confirm there are two nodes and the AppStruct node selects Resource: Project, Operation: Get Many.
2. Choose an AppStruct credential. In the AppStruct node, create or select the AppStruct API credential. The current package asks for your AppStruct account email and password. Enter these only in an n8n instance you trust.
3. Run the manual workflow. Inspect the AppStruct node’s output. Compare an actual returned project name with your Apps library. Keep execution results private because they can contain your project names and IDs.
4. Resolve the first failing step. An unknown-node error points to package installation. Authentication errors point to the selected account credential. An empty list calls for checking the account and library before changing the workflow.

The workflow performs a read, but the account credential is not limited to reads. Review any additional node operation before executing it. When sharing an exported workflow, remove credential references and execution data; see n8n’s import and export documentation.

03 · CHOOSE ONE BUSINESS TASK

Use the connection for a workflow you can check.

A service-request app is one possible starting point. Build the request form and saved records in AppStruct, then use n8n to read the relevant table. Check a small set of fictional requests before connecting a destination or scheduling a run.

For a notification workflow, define which records qualify, which fields the destination needs and how repeated runs avoid sending the same request twice. Configure those rules explicitly; the two-node starter does not supply a production notification system.

AppStruct and n8n: common questions.

What can the AppStruct n8n node do?

List App Builder projects; list, create and delete tables; read table schemas; read, create, update and delete records; and add columns. Start with a read before configuring changes.

Does this work on n8n Cloud?

This guide uses installation of a community package from npm on a self-hosted n8n instance. n8n Cloud only supports verified community nodes; this guide does not establish AppStruct as verified or promise Cloud availability.

Does the node use a Docs, Sheets or Slides MCP key?

No. This node connects to App Builder projects and tables using an AppStruct account email and password saved in n8n credentials. Docs, Sheets and Slides have separate MCP endpoints and product-specific API keys.

Does importing the example change my data?

The example is inactive, has a manual trigger and selects Project → Get Many. It lists project IDs and names when you run it. Its credential can authorize other node operations too; the example does not create a restricted read-only account.

Working with documents, spreadsheets or presentations through an AI assistant instead? Use the separate Docs, Sheets and Slides MCP connection guide.