Back to all integrations

Automation

Lineman and n8n

Build your own workflows on Lineman data with the community n8n node.

What this gets you

The Lineman community node puts your AI-coding spend, savings, allowance and cost alerts into an n8n workflow, and lets you change budgets, cost centres and alerts from an automation. You install it from n8n's community-nodes screen as @lineman-io/n8n-nodes-lineman, then add a Lineman API credential using a key created on the Keys page of your Lineman dashboard. The credential can do only what its owner can do: an administrator or auditor sees company-wide figures, anyone else sees only their own spend.

What people use it for

  • Act on a cost alert

    The Lineman Trigger node starts a workflow when a new company cost alert fires. The rest of the workflow can pass it to the chat channel, tracker or rota your team already uses. If you need faster delivery than the trigger gives you, point Lineman's alert webhook at an n8n Webhook node instead.

  • Scheduled spend and savings reports

    Run the Lineman action node on a schedule and read the Spend and Savings resources. A query window caps at 92 days and a longer range is rejected, so split a bigger export into chunks. Every amount comes back twice: use the _usd field to display it, and the _micro field when you are summing and care about rounding.

  • Change budgets from another system

    The node writes as well as reads, so a workflow can change a member's budget, a cost centre or an alert. Admin operations need a credential owned by an administrator. Note that a budget of null means the member inherits the company default, not that they may spend nothing.

More in Automation

Set up n8n

The documentation walks through connecting it, what Lineman reads and writes, and the settings worth knowing about.

Read the setup guide

Looking for something else?

Every integration in one place, searchable by name and filterable by what it does.

View all integrations