Contact your CSM or let us know for more information regarding the integration.
Manager, API and admin permission level is required in Cinode to set up this integration.
Our Maconomy integration automatically imports and updates customer data from Maconomy into Cinode. This allows organisations to maintain a single source of truth in Maconomy while ensuring Cinode remains fully up to date for sales, delivery, and reporting purposes.
The flow retrieves customers and projects from Maconomy using the configured container, maps fields according to your Field settings, and merges them with existing Cinode records based on the selected entity identifiers.
Prerequisites
Before using this integration, ensure the following are configured:
Maconomy Server URL – base URL to your Maconomy environment.
Maconomy Container – name of the Maconomy container that holds customer data (e.g.,
companycustomercard).Cinode Customer ID – defines whether customers match by External ID or Internal ID.
Customer Fields – mapping definitions specifying which Maconomy fields sync to which Cinode fields.
Customer Refresh Schedule – determines how often the synchronisation runs.
Getting Started
1. Configure the Company Connection
This step establishes the technical connection between Cinode and Maconomy.
Log in to your Prismatic account. If you do not have one, contact support@cinode.com
Open the Cinode Marketplace and select the Maconomy integration.
Run the Configuration step in Prismatic.
This creates the secure link between Cinode and your Maconomy environment.
You only need to complete this step once per company.
When prompted, connect to Cinode.
A green indicator confirms that the connection is active.
Click Next to continue.
2. Customer Setup
In this stage, you define how customers should sync from Maconomy into Cinode.
Customer Refresh Schedule
Controls how often the customer synchronisation runs.
During initial setup, set this to Never until your field mappings are confirmed.
Afterwards, switch to a scheduled option such as Hourly or Daily.
Customer ID Components
Defines which parts of the Maconomy data are used to build the unique customer identifier.
This varies between organisations depending on how customers are structured in Maconomy.
Examples:Customer number
Organisation number
Customer group or category
Region + customer number
You may select one or multiple components.
Customer ID Separator
The character placed between ID components when multiple fields form the customer ID.
Examples:-→ 1234-5678_→ north_2024
Cinode Customer ID
Specifies which identifier Cinode should use when matching and updating customers.
Options:
External – use the ID from Maconomy (
externalIdin Cinode)Internal – use Cinode’s internal ID
In most cases, External is recommended since Maconomy is the master system.
Customer Field Mapping
Defines how Maconomy fields map to Cinode fields.
Example mappings:
customername→nameaddress1→streetorgnumber→corporateIdentityNumber
Add, edit, or remove mappings depending on your data structure.
3. Project Filters and Mapping
Project Filters
Allows you to limit which projects are imported from Maconomy.
You can create your own filtering logic using AND/OR conditions, for example:
Only active projects
Projects of a specific type
Projects belonging to certain customers
Customer and Project Mapping
After completing customer mapping, you can map project fields similarly.
Project IDs, fields, and filters can be customised to ensure:
Projects sync correctly
They link to the right customer in Cinode
They appear in the correct pipeline stage
Troubleshooting
Missing or incomplete customer data
Check that all required Maconomy fields are added in Customer Fields → Source.
Customers not updating
Verify:
The Cinode Customer ID matches the ID type provided by Maconomy.
The
transactiontimestampfield exists and updates when records change.