Connect n8n

Brault has a native n8n node, n8n-nodes-brault, covering nearly every /v1 resource plus a trigger for the full event catalogue. It is a verified community node, so it is available on n8n Cloud without installing anything, and self-hosted n8n installs it from Community Nodes. If you would rather not use a community node, section 4 below still shows the generic Webhook and HTTP Request recipe.

1. Add the node and the credential

On n8n Cloud, search for Brault in the nodes panel of the workflow canvas and drag it into your workflow. If it does not appear, make sure Verified Community Nodes is enabled in your Admin Panel and restart the instance.

On self-hosted n8n, go to Settings → Community Nodes and install n8n-nodes-brault (n8n 1.80 or later).

Then create a Brault API credential: paste an API key from Get an API key and leave the base URL at its default unless Brault support gave you another host.

Scope the key to what your workflow needs, for example files:write to upload files and webhooks:manage for the trigger below. The package README lists the scope each resource needs.

2. Start a workflow from a Brault event

Add a Brault Trigger node and pick one or more events from the Events multi-select list, or * for every event. Activating the workflow registers a webhook endpoint in Brault named n8n · <workflow name>; deactivating the workflow removes that endpoint.

Signature verification is on by default (Options → Verify Signature), so a delivery whose Brault-Signature header does not match is rejected before the workflow runs. See Webhooks for the header and payload shapes.

Each active Brault Trigger workflow needs its own endpoint, and endpoints are capped per plan: Lite 1, Pro 5, Growth 25, Custom 25. See Plans and limits. Webhook deliveries do not count against your monthly request quota; only the calls the Brault node makes do.

3. Call Brault from a workflow

Add a Brault node after any trigger to read, create or update files, boards, comments, shared links and transfers. Three common flows:

• New file to a Slack message with a thumbnail. Brault Trigger (file.created) leads to Brault (File, Get Download URL, rendition Thumbnail), which leads to Slack (Send Message) with the thumbnail URL attached.
• Google Drive file to a Brault upload to a shared review link. Google Drive Trigger (new file) leads to Google Drive (Download File), then Brault (File, Upload, from the downloaded binary), then Brault (Shared Link, Create, type review) with the file ID from the upload step.
• New comment to a Notion task. Brault Trigger (comment.created) leads to Brault (File, Get, for context on the commented file), then Notion (Create Database Page) with the comment text as the task title.

The node exposes Return All and Limit on every list operation, sends an Idempotency-Key header on every create, and retries a single 429 response automatically when Retry-After is 10 seconds or less. It also works as a tool for an n8n AI Agent node, so an agent can call any of its operations directly.

4. Without the native node

If you would rather not install a community node, n8n's own Webhook and HTTP Request nodes reach the same result: register the Webhook node's production URL as a Brault webhook endpoint, and call any /v1 route from an HTTP Request node with a Header Auth credential (Authorization: Bearer bsk_…).

curl -X POST https://us.api.brault.app/v1/webhooks \
  -H "Authorization: Bearer $BRAULT_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 8f14e45f-2222-4c1a-9c1e-n8n-hook" \
  -d '{
    "url": "<the URL n8n gave you>",
    "name": "n8n workflow",
    "events": ["file.created", "comment.created", "transfer.downloaded"]
  }'

POST https://us.api.brault.app/v1/files/import
Authorization: Bearer <your key>
Content-Type: application/json
Idempotency-Key: <a unique value per run, e.g. the workflow execution id>

{
  "url": "https://example.com/exports/hero-v3.psd",
  "name": "hero-v3.psd",
  "library_id": "<library_id>"
}

See Rate limits and Conventions for error handling either way.

5. Package and source

• npm: n8n-nodes-brault — published with npm provenance, no runtime dependencies.
• Source and issues: github.com/Brault-app/n8n-nodes-brault — MIT. The README lists every resource, operation and required scope.

Feature requests and bug reports for the node go in that repository.