Automations: start here
Find your way around Rules, Workflows, Agents and Integrations, and choose how to connect Norman to your tools.
Updated
Where to start
Open Automations in Norman. This is where you manage repeatable work and connections to other tools. Check the selected company before changing a rule or connecting a service.
The tabs you see depend on the features available to your account. A missing tab does not mean that you need to create another company or account.
What each tab does
| Tab | Use it for | A first task |
|---|---|---|
| Rules | Apply defined conditions and actions to recurring bookkeeping situations. | Set up a rule for a supplier you pay regularly, then check its matches. |
| Workflows | Manage processes with several steps. Some steps may use AI or require review. | Open an available workflow, inspect its steps and configure it for your company. |
| Agents | See available AI agents and their activity. | Review what an agent completed and which tasks need attention. |
| Integrations | Connect external services, AI clients and your own software. | Connect a service or create an API key for a reporting script. |
Start with one task and review its result in the relevant invoice, transaction or document. Check execution history and any pending approvals. A configured workflow is not proof that every step has finished. Usage limits, plan requirements and review steps still apply.
Choose your connection
- Connect an existing service: use the provider's card in Integrations. Start with the service connection guide.
- Connect a CRM, dashboard or script: use the Public API. Your software makes specific requests using an API key.
- Work from an AI assistant: use MCP. The assistant discovers Norman's tools and uses them during your conversation.
- Build a visual automation: use n8n or Make. An HTTP step can call the Public API; compatible AI workflows can use MCP.
- Work in a terminal: see the Norman CLI guide.
Try one complete process
For example, connect the service that supplies your transactions, review the first imported records, and then create a rule for a recurring expense. If a CRM should prepare your invoices, start with one client and one draft through the API before scheduling repeated runs.
Keep source record IDs when synchronizing systems. Check for an existing transaction or invoice before repeating a failed run. Connecting two feeds for the same data can create duplicates.
The Integrations section of the help center brings these guides together. For endpoint details and executable examples, use the developer documentation.
Norman handles the operational finance work
Invoicing, receipts, bookkeeping, and taxes in one workflow: start for free.