Connections
The tools Barda reads from. Their records stay in each tool.
Invoice Ninja
API connected- Service address
- https://invoice-ninja.demo.invalid
- Key
- Saved on the server, ends in …demo
- Last check
- Read 19 clients, 214 invoices and 61 expenses. · 4 minutes ago
Disconnect Invoice Ninja
Barda stops reading Invoice Ninja. Linked records stay for review; to reconnect, enter the key again.
Replace key or address
Replacing this connection stops existing linked-record reads until you verify those source references again.
- In Invoice Ninja, open Settings → Account Management → API Tokens and add a token named Barda.
- Paste the token below, review the connection and browser addresses, then press Connect.
Invoice Ninja tokens can do anything your account can. Barda only reads with it. The key stays on this server and is never shown again. Barda’s records-and-uploads ZIPs exclude keys.
InvenTree
API connected- Service address
- https://inventree.demo.invalid
- Key
- Saved on the server, ends in …demo
- Last check
- Read 46 stock items in 8 locations. · 4 minutes ago
Disconnect InvenTree
Barda stops reading InvenTree. Linked records stay for review; to reconnect, enter the key again.
Replace key or address
Replacing this connection stops existing linked-record reads until you verify those source references again.
- In InvenTree, create a dedicated user with view access to stock, parts and locations, then create its API token. The connected preset can provision this account and token; other installations need their own.
- Paste the token below as the API key, review the connection and browser addresses, then press Connect.
Inventory stays in InvenTree. Barda shows assets linked to each property and unit. Damaged stock requires review even if InvenTree counts it as available.
Equipment creation account
Equipment creation is not approved. Existing inventory reads are unchanged.
This setup approves a separate account for supported equipment creation. Editing, moving and retiring items need separate support. This page does not create equipment or verify a successful save.
Keep the existing read account. Use a separate active account with the reviewed parts and stock creation roles and location read access. InvenTree also grants change access and inherited BOM actions with these roles. Barda exposes only the two equipment creation actions; it does not expose those broader source operations. Staff, administrator and other role grants are not accepted.
Twenty
API connected- Service address
- https://twenty.demo.invalid
- Key
- Saved on the server, ends in …demo
- Last check
- Read 19 people and 6 companies. · 4 minutes ago
Disconnect Twenty
Barda stops reading Twenty. Linked records stay for review; to reconnect, enter the key again.
Replace key or address
Replacing this connection stops existing linked-record reads until you verify those source references again.
- In Twenty, open Settings → APIs & Webhooks, choose Create key and name it Barda. Copy the key when it is shown.
- Paste the key below, review the connection and browser addresses, then press Connect.
Use a role with view access to People for residents and Companies for linked vendors. Connect checks People; linked Company reads check their own access.
DocuSeal
API connected- Service address
- https://docuseal.demo.invalid
- Key
- Saved on the server, ends in …demo
- Last check
- Read 19 signed leases. · 4 minutes ago
Disconnect DocuSeal
Barda stops reading DocuSeal. Linked records stay for review; to reconnect, enter the key again.
Replace key or address
Replacing this connection stops existing linked-record reads until you verify those source references again.
- In DocuSeal, open Settings → API and create a key.
- Paste the key below, review the connection and browser addresses, then press Connect.
Barda reads linked submission status; signing and template administration stay with DocuSeal.
Trilium · Optional
API connected- Service address
- https://trilium.demo.invalid
- Key
- Saved on the server, ends in …demo
- Last check
- Read 12 property notes. · 4 minutes ago
Disconnect Trilium
Barda stops reading Trilium. Linked records stay for review; to reconnect, enter the key again.
Replace key or address
Replacing this connection stops existing linked-record reads until you verify those source references again.
In Trilium, open Options → ETAPI and create a token. Barda reads linked note details and text on demand. Trilium is a single-user notebook; its token has broad access.
Frigate · Optional
Account connected- Service address
- https://frigate.demo.invalid
- Account
- demo
- Custom role
- viewer
- Last check
- Read 2 cameras and 14 events today. · 4 minutes ago
Disconnect Frigate
Barda stops reading Frigate. Linked records stay for review; to reconnect, enter the account again.
Replace account or address
Replacing this connection stops existing linked-record reads until you verify those source references again.
- Use Frigate’s authenticated HTTPS address, normally port 8971, with a trusted certificate.
- Create a dedicated account with a custom role such as barda_common, limited to approved common-area cameras. Built-in admin and viewer roles are not accepted.
- Enter that account’s exact username, password and custom role below, then press Connect Frigate.
Frigate is optional. Barda checks native sign-in and reads mapped camera health and recent activity. Passwords and sessions stay on this server. Camera and hardware setup stays in Frigate.