BlackLine
Connect AI agents and workflows to BlackLine: load balances and transactions, follow reconciliations and close tasks, and post journal entries.
Book a demoBlackLine for AI agents and workflows.
engini lets your AI agents and workflows work in BlackLine, the financial close platform: load general ledger balances and bank or subledger transactions from your ERP, follow account reconciliations and close tasks, read matching results, create journal entries for the ERP, and start a workflow when a task or reconciliation changes. The close gets its data on time, and the ERP gets its entries back. Connect from Claude, ChatGPT or Cursor over MCP, from your code, or build in Workflow Studio.
Cursor, your code
audit log
in engini
What your agent can do in BlackLine. Every tool is one you allow or leave out.
The BlackLine tools in engini, grouped by what they change. Read tools are safe to hand out widely. Write and delete tools go only to the agents that need them.
Read
Read reconciliations with balance, status and preparer.
Read close tasks, owners and due dates.
Read matched and unmatched transactions.
Read journal entries prepared in BlackLine.
Write
Load trial balance data from the ERP for the period.
Load bank or subledger transactions for matching.
Prepare a journal entry for posting to the ERP.
Mark a close task done or add a comment.
Any endpoint
Call any BlackLine API, with the sign-in added for you.
Triggers
Reconciliations that changed status.
Close tasks past their due date.
A trigger starts a workflow, and a workflow can include an AI agent step. In Code, a trigger delivers the event to your own endpoint.
Connect your AI agent to BlackLine. Four ways in, one set of permissions.
Claude, ChatGPT, Cursor
Create an MCP server in engini with your BlackLine connection and only the tools you choose. Add its address to your client and sign in through engini. There is no key to copy.
MCP client setup →Python and TypeScript
Hand your agent a toolset of BlackLine tools. The SDK gives OpenAI and Anthropic models the tools in the format they expect and runs the ones they pick.
SDK guide →For coding agents
The engini CLI connects BlackLine and runs its tools from a terminal, with machine-readable output, so an AI coding agent can drive it without getting stuck.
CLI guide →Any language
Every BlackLine tool is an endpoint. Call it with exact inputs from a scheduled job or a sync, with no model in the loop.
API reference →.cursor/mcp.json. Claude Code: claude mcp add.// .cursor/mcp.json: Cursor, connected to BlackLine through engini
{
"mcpServers": {
"engini-blackline": {
"url": "<your engini MCP server address>"
}
}
}
Create the MCP server in engini with your BlackLine connection and the tools this agent may use, then paste its address. The client signs in through engini on first use. Claude, VS Code and other clients take the same address: see the MCP client setup guide.
Each request runs through the BlackLine tools in the agent's toolset or MCP server. If a tool is not allowed, the agent cannot call it.
What teams build on BlackLine. Agents and workflows, across systems.
Balances in BlackLine on day one
At period end, trial balances from NetSuite, SAP or Oracle load into BlackLine automatically, so preparers start on time.
Bank transactions ready to match
Bank transactions from Plaid or bank files load into BlackLine matching every morning.
Entries back to the ERP
Journal entries prepared in BlackLine are posted to the ERP, with the ERP document number written back.
Close status without chasing
An agent in Teams answers which tasks and reconciliations are late, and pings the owners. Its toolset holds read tools only.
Every integration runs both ways, so any of these flows can also run in reverse. These are examples, not the limit: any flow between BlackLine and another system engini connects is available.
You decide what each agent may do in BlackLine. engini enforces it on every call.
Only the tools you allow
A toolset lists the BlackLine tools an agent may call and the connection each one uses. Give one agent read tools only and another the write it needs. engini refuses any call outside the toolset.
Scoped when you set them up
An MCP server exposes only the connections and tools chosen when it is created, and engini shows who uses each server.
Whose permissions apply
Connect a person's own BlackLine account and engini acts as that person, with their BlackLine permissions. Use a shared integration account and it acts as that account. Every run is recorded under the user who started it.
Kept out of prompts
Your agent never needs your credentials: engini stores them and adds them when it runs each call, so keys stay out of prompts and tool inputs.
Every call on record
Every call lands in History and the audit log, which you can export or stream to your SIEM.
Test before production
Workspaces keep teams apart, and development, staging and production environments keep a test agent away from live data.
Connect BlackLine in three steps. Then decide what each agent may do.
Sign in to BlackLine
In BlackLine, create an API client for engini with only the scopes the workflows need, then add a BlackLine connection with your tenant, client ID and secret.
Choose the tools
Add the connection to an MCP server or a toolset with only the tools each agent needs.
Build or ask
Use the connection as a step in a workflow, or ask your agent to work in BlackLine from Claude, ChatGPT, Cursor or your own code.
BlackLine and engini. Straight answers.
Can an AI agent write to BlackLine, or only read?
Both. engini has tools to import balances and transactions, create journal entries and update close task status. Whether a given agent may use them is up to you: give it a toolset or an MCP server with read tools only, and it cannot call the rest.
Does the agent act as me in BlackLine?
It acts as the BlackLine API client behind the connection, with the scopes it was given. Every run is recorded under the person who started it.
Can a change in BlackLine start work?
Yes. Scheduled triggers check for reconciliations that changed status and close tasks that are overdue. A workflow can include an AI agent step.
What if the tool I need is not listed?
Use Send API Request to call any BlackLine API endpoint through the same connection, and give it only to the agents that need it.