---
title: "Use Augure with n8n"
description: "Use Augure's Canadian, OpenAI-compatible API in n8n workflows and AI Agent nodes through an OpenAI credential with a custom base URL."
tool: "n8n"
category: "automation"
canonical: "https://augureai.ca/docs/integrations/n8n"
updated: "2026-10-26"
verified: false
---
# Use Augure with n8n

You get Augure models in n8n's OpenAI node and in the OpenAI Chat Model node that powers AI Agent and LLM Chain workflows, with inference on Canadian infrastructure.

## Prerequisites

- n8n (cloud or self-hosted) with permission to create credentials.
- An Augure API key (`aug_sk_live_…`) from the [developer dashboard](https://chat.augureai.ca/developers/dashboard). Plans and pricing: [augureai.ca/developers](https://augureai.ca/developers).

## Configure

### 1. Create the credential

n8n's OpenAI credential has a base URL field, so no custom HTTP node is needed.

1. Go to **Credentials** > **Create** and choose **OpenAI**.
2. Fill in:

```text
API Key:          aug_sk_live_...
Organization ID:  (leave empty)
Base URL:         https://api.augureai.ca/v1
```

3. Save. n8n tests the credential by listing models on the base URL.

### 2. Use it in a node

- **AI Agent** or **Basic LLM Chain**: attach an **OpenAI Chat Model** sub-node, select the Augure credential, and pick a model. The dropdown is loaded from `/v1/models`; if it only shows OpenAI names in your version, switch the field to **ID** or an expression and type `rosedale-1`.
- **OpenAI** node (Message a Model): select the same credential and set the model the same way.

The node's **Maximum Number of Tokens**, **Sampling Temperature** and **Response Format** options map directly to `max_tokens`, `temperature` and `response_format`.

### Alternative: HTTP Request node

For full control, call the API with an **HTTP Request** node: method `POST`, URL `https://api.augureai.ca/v1/chat/completions`, a `Header Auth` credential with name `Authorization` and value `Bearer aug_sk_live_...`, and a JSON body:

```json
{
  "model": "tofino-3",
  "max_tokens": 64,
  "messages": [{ "role": "user", "content": "Say hello in one short sentence." }]
}
```

The reply text is at `{{ $json.choices[0].message.content }}`.

## Pick a model

| Model | When to use |
| --- | --- |
| `ossington-5` | Flagship reasoning. 256K context, 32,768 max output. Hard classification, drafting, analysis steps. |
| `rosedale-1` | Premium reasoning, up to 1M context on paid plans, Canadian inference. AI Agent nodes with tools, long documents. |
| `tofino-3` | Fast everyday model, 256K context, 16,384 max output, no thinking. High-volume extraction and routing steps. |

`auto` lets the gateway pick. On `ossington-5`, `reasoning_effort: "none"` turns thinking off; the OpenAI Chat Model node has a **Reasoning Effort** option in recent n8n versions, but its choices may not include `none`. For fast mechanical steps, use `tofino-3`, or set `reasoning_effort` in the HTTP Request body. Full list: [/docs/models](https://augureai.ca/docs/models).

## Verify it works

Run the HTTP Request node above from a Manual Trigger, or check from any terminal:

```bash test
curl -s https://api.augureai.ca/v1/chat/completions \
  -H "Authorization: Bearer $AUGURE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"tofino-3","max_tokens":64,"messages":[{"role":"user","content":"Reply with the single word OK."}]}'
```

The JSON ends with an `_augure` block, for example `"_augure": {"gateway_region": "ca-montreal-1", "inference_region": "ca-on-toronto", "request_id": "..."}`. `inference_region` tells you where the model ran. In the HTTP Request node it is `{{ $json._augure.inference_region }}`. Inference is on Canadian infrastructure first, with disclosed failover to vetted EU partners under zero data retention, never the US.

## Notes

- AI Agent nodes rely on tool calling; Augure supports it, and `rosedale-1` or `ossington-5` are the models to use for agent steps.
- The OpenAI node's image, audio and assistant operations target OpenAI-specific endpoints and are not covered here; `image_url` and PDF `file` parts work through the HTTP Request node.
- OpenAI model aliases are accepted (`gpt-4o` to `ossington-4`, `gpt-4o-mini` to `tofino-3`), so existing workflows keep running while you switch to explicit Augure ids.

## See also

- [API reference](https://augureai.ca/docs/api)
- [Models](https://augureai.ca/docs/models)
- [MCP server](https://augureai.ca/docs/mcp)
- [IDE setup](https://augureai.ca/docs/ide)
- [Pricing](https://augureai.ca/pricing)