n8n-nodes-gereft

An n8n community node for the Gereft API.

The node is generated from Gereft's OpenAPI spec, so it covers the whole API: each API section (Invoice, Note, Rfq, …)
is a Resource, and each endpoint is an Operation. Required parameters are shown directly. Optional ones are
under Additional Fields, and only the fields you add there are sent. Nested objects and arrays in a request body
are entered as JSON.

The node can also be used as a tool by n8n's AI Agent.

Installation

From the n8n UI (recommended)

1. In n8n, open Settings → Community Nodes.
2. Click Install, enter n8n-nodes-gereft, accept the risk notice, and click Install.
3. The Gereft node now appears in the node panel.

To update, open Settings → Community Nodes and click Update on the package.

Community nodes are only available on self-hosted n8n. The n8n server needs access to registry.npmjs.org. If it
doesn't have that access, use the manual install below.

Manual install (offline / no npm access)

1. Download the package on a machine with internet access:

   npm pack n8n-nodes-gereft
   

2. Copy the .tgz file into the n8n container and install it:

   docker cp n8n-nodes-gereft-<version>.tgz <n8n-container>:/tmp/
   docker exec -u node <n8n-container> sh -c \
     'mkdir -p ~/.n8n/nodes && cd ~/.n8n/nodes && npm install /tmp/n8n-nodes-gereft-<version>.tgz'
   

3. Restart n8n: docker restart <n8n-container>.

Credentials

Create a credential of type Gereft API:

• API Key: a server API key. It has full access, but requests are not tied to a user. Endpoints that depend on the
  current user (for example /auth/me or "my" lists) won't work with it.
• Bearer Token (JWT): a Gereft user's token. Requests run as that user, with that user's permissions. The token
  expires and then has to be replaced.

Limitations

• File uploads (multipart/form-data endpoints such as POST /media/upload) aren't supported. Use n8n's
  HTTP Request node for those.

License

MIT