Using n8n with MendriX

n8n is a low-code workflow automation tool. This guide sets up the foundation every other n8n guide in this portal builds on: a reusable credential, the HTTP Request node, pagination and error handling. Each integration guide also ships an importable workflow JSON under /n8n/.

These guides use synced tabs

Every guide shows each step as a Manual (REST) / n8n tab pair, and your choice is remembered site-wide. This page focuses on the n8n side; the Manual tab points you at the equivalent REST material.

Step 1 — Credential + login node

MendriX authentication is a two-step flow: your long-lived API token is exchanged for a short-lived access token (JWT) which authenticates the actual API calls — see Authentication. In n8n that means: one credential holding the API token, and one login node at the start of every workflow.

Manual (REST)

On the manual path you log in once and use the returned access token:

export MENDRIX_ACCESS_TOKEN=$(curl -s -X POST \
  "$MENDRIX_BASE/account/login-api-token" \
  -H "Content-Type: application/json" \
  -d "{\"token\": \"$MENDRIX_API_TOKEN\"}" | jq -r '.data.items[0].access')

curl "$MENDRIX_BASE/client/clients/" \
  -H "Authorization: Bearer $MENDRIX_ACCESS_TOKEN"

n8n

Create the credential once:

1. Credentials → New → Custom Auth.
2. Name: MendriX API token.
3. JSON:

   { "body": { "token": "YOUR_API_TOKEN" } }

4. Save.

Then start every workflow with an HTTP Request node named Get access token:

• Method: POST
• URL: https://<your-client-name>.api.mendrix.cloud/api/account/login-api-token
• Authentication: Generic Credential Type → Custom Auth → MendriX API token (injects the token into the request body).

Its output contains data.items[0].access — a JWT that is fresh for the duration of the run, so workflows never need refresh handling. Using a credential (rather than pasting the token into the node) keeps the secret out of your workflow JSON when you export it.

Step 2 — The HTTP Request node

Manual (REST)

The manual equivalent is a single HTTP call. See Your first integration for curl and JavaScript.

n8n

1. Add an HTTP Request node after Get access token.
2. Method: the endpoint’s verb (GET, POST, PATCH, …).
3. URL: https://<your-client-name>.api.mendrix.cloud/api/<path>.
4. Headers: add Authorization = Bearer {{ $('Get access token').first().json.data.items[0].access }}.
5. For GET, add Query Parameters (limit, cursor, sort, since).
6. For POST/PATCH, set Body Content Type to JSON and provide the body. Add a Content-Type: application/json header.

Step 3 — Page through results

Manual (REST)

Follow the cursor as described in Pagination & sync.

n8n

The HTTP Request node has built-in pagination:

1. In the HTTP Request node, enable Pagination.
2. Pagination Mode: Response Contains Next URL if the API returns one, otherwise Update a Parameter in Each Request and set the cursor query parameter from the previous response’s cursor field.
3. Stop condition: when no cursor is returned.
4. Set limit to 1000 to minimise the number of requests.

Tip

If you prefer explicit control, use a Loop with an IF node that stops when the response no longer contains a cursor.

Step 4 — Handle errors

Manual (REST)

Check the status code and read the body on failure — see Errors & conventions.

n8n

1. On each HTTP Request node, open Settings.
2. Set On Error to Continue (using error output) so a failure does not abort the whole run.
3. Wire the error output to an IF/Switch node: retry 429/5xx with a Wait node and back-off; route 4xx to a notification/log.
4. Enable Retry On Fail for transient errors.

Importable workflows

Every guide links its own workflow JSON. Import any of them via Workflows → Import from File, then attach your MendriX API token Custom Auth credential to the Get access token node and replace <your-client-name>:

• first-integration.json — list clients
• client-crm-sync.json — incremental client sync
• order-intake.json — submit an order (SOAP XML)
• order-status-tracking.json — receive order webhooks
• invoices-accounting.json — pull invoices, post payments