NORMAN DEVELOPERS
Connect Norman with n8n, Make and MCP
Build HTTP workflows with the Norman REST API or connect AI assistants through the hosted MCP server and Norman authorization.
Connect n8n or Make
Use an HTTP request step to connect directly to this REST API. The n8n card in Norman’s Integrations area also offers an MCP connection for AI workflows.
- Create a Norman key with the scopes the workflow needs, then store it in the tool’s credential store.
- Add an HTTP Request node in n8n, or an HTTP → Make a request module in Make.
- Choose
GETandhttps://api.norman.finance/api/v1/companies/. Configure theAuthorizationheader asBearer YOUR_KEYusing the credential store. - Run the step. Map
results[0].publicIdinto the company path of subsequent client, invoice or document requests. - For writes, use JSON with
Content-Type: application/json; for file uploads, use multipart. Configure pagination and an error branch before scheduling the workflow.
Start with a scheduled transaction export or a CRM-triggered invoice draft. Keep created Norman IDs in the source system so reruns update the same records. Public event subscriptions are not included in this version; use scheduled reads for synchronization.
n8n HTTP Request documentation ↗ · Make HTTP documentation ↗
Connect an AI assistant with MCP
The hosted Norman MCP server lets compatible AI clients discover tools and work with your Norman company. The MCP tool catalogue is separate from this REST API reference.
https://mcp.norman.finance/mcp- Log in to Norman and open Automations → Integrations. Choose your AI client and follow its connection instructions.
- For a compatible custom client, add the hosted server as a remote Streamable HTTP connection and complete Norman authorization through OAuth.
- Ask the assistant to list your companies and confirm the one you want to use. Start by asking for unpaid invoices or recent transactions.
- Review the company, recipient and amounts before approving a write. A draft and a sent invoice are different steps.
The hosted connection uses Norman sign-in. You do not need to paste a REST API key into a conversation. Client availability and workspace policies can affect the setup options.
MCP setup guide · MCP server documentation · Automations in Norman
Create an account or log in, select your company, then open Automations → Integrations → Public API to create a key and choose its permissions.