CRM & Sales · 69 pre-built actions
CRMConnect integration with Nexus
Run CRMConnect sales, billing and stock steps under control. Client, contact, order, contract, invoice, expense, ticket, goal, item and warehouse actions let CRMConnect take part in governed processes with other systems.
Pre-built actions
What you can automate
69 pre-built CRMConnect actions, grouped by what they work on.
69
PRE-BUILT ACTIONS
- 01Clients, Contacts and Orders actions keep commercial records current from any workflow step.
- 02Contracts, Contract Types and Invoices actions support contract and billing processes.
- 03Expenses and Expense Categories actions record and organise spend.
- 04Items, Item Categories, Units of Measure, Warehouse and Inventory actions cover product and stock data.
- 05Tickets and Goals actions track support work and targets.
Workflow
How it fits into a Nexus workflow
CRMConnect steps run as pre-built actions. A run that uses them starts from a webhook, a schedule, a request in Nexus or another system's trigger source.
A trigger source starts work. A connector action performs work. Both run inside the same governed execution.
Beyond pre-built actions
When the pre-built action is not enough
Move down one step: an API, protocol or database call, then custom logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript with any library. Every step uses the same secrets, approvals, history and audit.
01
Call the CRMConnect API with the HTTP Request node, or use GraphQL, SOAP or a database node where the system exposes one.
02
Write custom integration logic in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript, with the libraries your team already uses.
03
Direct calls and code use the same vault-backed secrets, approvals, run history and audit as pre-built actions.
Examples
Workflow examples
Order to invoice
A validated order in CRMConnect is invoiced, with orders outside policy paused for a finance owner first.
Contract setup with approval
A new contract is created with the right contract type after the commercial owner approves its terms.
Stock check before order confirmation
Items and inventory are checked before an order proceeds, and shortfalls go to the warehouse owner.
Expense recording
Approved expenses are recorded in CRMConnect under the correct expense category.
Client ticket follow-up
A client ticket is opened and progress is tracked, with escalation to a named owner when it stalls.
Deployment, trust and audit
Governance, audit and deployment
Deployment
Nexus runs on-premises, in private or sovereign cloud, or air-gapped. The step needs network reach to the system it calls, and nothing else changes.
Secrets and identity
Credentials are referenced through vault-backed secret handling and role-based access, never embedded in workflow logic.
Audit
Inputs, outputs, approvals and outcomes are written to the execution history for every run.
Industry use cases
Processes that use CRMConnect
Enterprise
CRMConnect order to ERP workflow
CRMConnect orders and contracts become validated SAP sales orders and invoices.
Enterprise
CRMConnect invoicing to accounting
CRMConnect invoices are recorded and reconciled in Xero with exceptions approved.
Enterprise
CRMConnect ticket escalation
CRMConnect tickets that need IT or operations become owned ServiceNow cases.
Enterprise
CRMConnect warehouse coordination
CRMConnect stock and orders stay aligned with Odoo, with shortages raised to owners.
FAQ
CRMConnect connector questions
- Which CRMConnect actions are pre-built?
- Nexus includes 69 pre-built CRMConnect actions across Clients (4), Contacts (5), Orders (4), Contracts (4), Contract Types (4), Invoices (6), Expenses (6), Expense Categories (5), Tickets (5), Goals (5), Items (5), Item Categories (5), Units of Measure (5), Warehouse (5) and Inventory (1).
- Can CRMConnect start a workflow?
- Runs that use CRMConnect start from a webhook, a schedule or another trigger source. CRMConnect steps run as actions inside the workflow.
- What if the operation I need is not pre-built?
- Use the CRMConnect API through the HTTP Request node, or write the step in Python, Bash, Go, Java, .NET, PHP, PowerShell or JavaScript/TypeScript. It runs in the same workflow with the same approvals and audit.
Related reading
Continue from here
- Salesforce connector
Leads, accounts, opportunities and cases.
- Human-in-the-loop
Where approval belongs in a running workflow.
- When there is no connector
API, protocol and code steps in one run.
- Integration patterns
How systems work together in a complete process.
Integration review
Discuss how CRMConnect fits your process.
Bring the operation you need. We will map it to a pre-built action, or to the API, protocol or code step that covers it.