autario

n8n community node for autario: search, query and export datasets, append rows to your own tables and refresh connectors over the autario REST API.

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 1.0.1
Author: autario

Documentation

n8n-nodes-autario

The autario node for n8n: search, query and export datasets, append rows to your own tables and refresh connectors from a workflow, over the documented autario REST API at https://autario.com/api/v1.

autario is the data layer for data apps: one account holds the tables your connectors write (ad platforms, shops, analytics, CRM, invoicing), your uploads and roughly eight thousand normalized public datasets, and every table is reachable through the same API. This node puts that API into n8n without an HTTP Request node per call.

Documentation: https://autario.com/developer/docs/n8n

Install

In n8n open Settings > Community Nodes > Install, enter n8n-nodes-autario, accept the prompt and the node appears in the node picker as Autario. Community nodes install on self-hosted n8n; on n8n Cloud the node is available once n8n has verified it.

For an image-based install the package name is the same:

npm install n8n-nodes-autario

Credentials

Create an API key at https://autario.com/account under API keys. The key and the secret (shown once) go into the Autario API credential; n8n sends them as the x-api-key and x-api-secret headers. The credential test calls GET /me/datasets, which lists only the tables you own.

Operations

Every operation is one documented path of the autario OpenAPI document (https://autario.com/api/v1/openapi.json).

Resource Operation Calls
Dataset Search GET /datasets?q=&limit=&offset=&mine=
Dataset Get GET /datasets/{id}
Dataset Get Schema GET /datasets/{id}/schema
Dataset Query GET /datasets/{id}/query?filters=&fields=&sort=&limit=&offset=&overlay=
Dataset Get Many GET /me/datasets?brand=&instances= (every table you own, with a CSV URL per row)
Dataset Export CSV GET /datasets/{id}/export (the whole table as CSV text in csv)
Dataset Create POST /datasets
Row Append POST /datasets/{id}/rows (max 10000 rows per call)
Row Clear DELETE /datasets/{id}/rows (keeps schema and ID)
Connector Get Many GET /connectors (one item per instance)
Connector Get GET /connectors/{id}
Connector Refresh POST /connectors/{id}/refresh

Filters on Query are written one per line as column:op:value with the operators eq, neq, gt, lt, gte, lte and like, and travel as the repeatable filters parameter. Call Get Schema first to know the column names; the schema also carries one semantics sentence per column.

Things the API refuses are passed through as they are: a dataset that is not yours answers 404, a dataset an app owns answers 409 app_owned_dataset on Append, a connector refresh under ten minutes after the last run answers 429 with retry_at.

Example

A schedule trigger, a node that produces rows (a database, a sheet, an HTTP call), Autario > Row > Clear on your dataset, Autario > Row > Append with {{ $json.rows }}, then Autario > Dataset > Query to read the fresh table back into a message. The dataset ID stays the same, so every chart and app on autario that reads it keeps working.

Development

npm install
npm run build      # tsc + copies the icon and codex into dist/
npm run lint       # eslint with n8n's community node rules
npm test           # vitest: one pinned request per operation

The node is declarative: every operation is a routing entry on the node description, and the only code is the CSV post-processing that turns the export body into { csv }.

Links

License

MIT

Discussion