Description

@aurentiaai/n8n-nodes-aurentia

This is an n8n community node. It lets you use Aurentia in your n8n workflows.

Aurentia is the AI-native business OS for entrepreneurs — CRM, tasks, databases, social media, projects, finance, a website builder, AI agents and more, all in one place.

n8n is a fair-code licensed workflow automation platform.

Installation
Operations
Credentials
Compatibility
Ready-to-import workflows · Guide français

Usage
AI Agent tool usage
Trigger
Resources
Development
Version history

Installation

Upgrading to 0.5.0: review downstream forecast and website-template
expressions first. Forecast reads prefer the workbook (input: null, use
businessPlan and indicators); generation returns workbookId, filledCells
and creditsCharged. Native template checkout debits Aurentia credits and
grants an acquisition directly, without creating a new Stripe session.
Operation identifiers remain stable. See CHANGELOG.md.

Follow the installation guide in the n8n community nodes documentation.

• Self-hosted: Settings > Community Nodes > Install and enter @aurentiaai/n8n-nodes-aurentia.
• n8n Cloud: once the node is verified, search for Aurentia directly in the nodes panel.

Operations

The package ships two nodes: Aurentia (actions) and Aurentia Trigger (polling events).

Curated core resources

Seven hand-built resources with the richest UX (searchable resource pickers, “Simplify” output, “Return All” pagination):

• Account — Get Profile, Get Credit Balance
• Contact (CRM) — Create, Get, Get Many, Update, Delete
• Deal (CRM) — Create, Get, Get Many, Update, Delete
• Project — Get, Get Many, Update, Archive
• Record (Bases / databases) — Create, Get, Get Many, Update, Delete
• Social Post — Create, Get, Get Many, Update, Delete, Schedule, Publish
• Task (Kanban) — Create, Get, Get Many, Update, Delete

Full Aurentia coverage

Beyond the curated core, the node exposes the Aurentia tool registry used by its AI agents and bots. These operations are generated from Aurentia’s internal tool registry, so rebuilding and publishing a release synchronizes its catalog with the product. Registry coverage is checked by npm run coverage:audit; it is not a claim that every operation has been tested against a live account. Available domains include:

Agents · Assistant & conversations · Automations · Booking & calendar · Brand DNA & brand identity · Clips · Close (sales calls) · Collaborators · CRM (advanced) · Dashboard · Drive · Email · Finance & forecasting · Forms · Import · Integrations · Marketplace · Missions · Modules · Notes · Notifications · Playbooks · Projects (advanced, incl. create) · Prospection · Quotes & contracts · Recommended tools · Resources · Routines · Site builder · Social media (advanced) · Tasks (advanced) · Tools · Whiteboards · Workspace databases · and more.

> Some generated operations trigger AI generation and consume Aurentia credits (documents, media, prospection, agent runs). When your balance is empty the node returns a clear, actionable error.

Credentials

You need an Aurentia account. The node offers two authentication methods (select one on the node’s Authentication field):

API key (simplest)

1. In Aurentia, open Settings > Integrations.
2. Generate an API key (starts with aur_). It is shown once — copy it.
3. In n8n, create an Aurentia API credential and paste the key.

The Base URL defaults to https://entrepreneurs.aurentia.fr and normally does not need changing (use http://app.localhost:3000 only for local development).

OAuth2 (no key to copy/paste)

1. In Aurentia, open Settings > Integrations > OAuth clients and register a client with your n8n instance’s callback URL (shown in the n8n credential screen, e.g. https:///rest/oauth2-credential/callback). You receive a Client ID and Client Secret (the secret is shown once).
2. In n8n, create an Aurentia OAuth2 API credential, paste the Client ID/Secret, and click Connect my account. You will be asked to authorize the connection in Aurentia.

Both methods carry the same permissions — an Aurentia credential can access everything your account can. You can revoke an API key or an OAuth client at any time from Settings > Integrations.

Compatibility

The workflow templates are exercised in n8n 2.39.7 against a local API simulator (API-key and OAuth bearer credentials). This tested n8n runtime and the E2E command require Node.js 24+.

For AI Agent tool usage: on n8n 2.x no extra configuration is needed. On n8n 1.x (>= 1.79), set N8NCOMMUNITYPACKAGESALLOWTOOL_USAGE=true on the instance.

Usage

> This node is data-in / data-out — never interactive. Every operation is a
> plain API call (the same surface Aurentia’s own AI agents use). There is no
> onboarding, wizard or UI step: anything the app walks a human through, you do
> here as a sequence of data operations.

Capture a lead from a form into your CRM
Form Trigger → Aurentia: Contact – Create (pick your project, map name/email) → Aurentia: Deal – Create (link the new contact, set a title) → Aurentia: Task – Create (a follow-up card).

Announce a published post
Aurentia Trigger (Post Published) → your Discord/Slack/email node with the post link.

Weekly pipeline digest
Schedule Trigger (Mondays) → Aurentia: Deal – Get Many (Return All) → your email node with a summary.

Create a project and generate its content — no onboarding
The app’s project onboarding is just a UI over the API. From n8n it is a data flow:
Aurentia: Create Project (send name + one-sentence idea + optional details → returns the project id) → Aurentia: Generate Project Modules (and/or Generate Markets / Targets / Category) → poll Aurentia: Get Generation Status until ready. Same content, same power, zero clicks.

AI Agent tool usage

The Aurentia action node is usableAsTool: true: connect it to an AI Agent node’s tool input and the agent can operate Aurentia in natural language — e.g. “create a contact Jane Doe at ACME in project X, then add a follow-up task”. On n8n 1.x, enable N8NCOMMUNITYPACKAGESALLOWTOOL_USAGE=true (see Compatibility).

Trigger

The Aurentia Trigger node polls Aurentia and starts your workflow on:

• New Contact, New Deal, New Task, New Base Record, Post Published.

Polling latency depends on your interval and the time needed to read the source. Activation establishes a baseline; later polls read all pages and emit unseen IDs. Failed/incomplete scans never advance progress. The ID ledger is retained across polls and resets when you change the watched scope. Manual tests return the latest sample without changing progress.

API requests scale with source size and stored state scales with observed IDs. Items created and deleted between polls remain invisible, and already observed post IDs are not emitted again on republication. See polling and retry behavior.

Resources

• n8n community nodes documentation
• Aurentia

Development

npm install
npm run dev          # builds + runs a local n8n on :5678 with the node loaded (hot reload)
npm run lint         # official n8n community-node linter
npm run build        # compile + copy icons into dist/
npm run generate     # regenerate the full-coverage operations from the Aurentia tool registry
npm run generate:check   # determinism + build + catalog + all unit/contract tests
npm test                # run after build; includes trigger and template regressions
npm run test:e2e         # real n8n engine + local HTTP simulator (downloads n8n if needed)

The curated resources live in nodes/Aurentia/actions//; the generated ones in nodes/Aurentia/actions/generated/ (do not edit by hand — run npm run generate).

Version history

0.1.0

• Initial release. Two nodes (Aurentia, Aurentia Trigger), API key + OAuth2 authentication, curated core (7 resources) plus full generated coverage (58 resources / 766 operations), usableAsTool support.

Usage measurement

Requests from this node identify the integration as n8n and classify their purpose as operation, poll or setup. Aurentia records this only after successful Bearer authentication, without workflow names, payloads or credentials. These are API requests, not successful workflows: pagination and polling can create multiple requests. Older clients remain visible with an unspecified purpose. No additional network request or LLM invocation is added by the node.