The Maconomy integration keeps Cinode in step with your customer and project data automatically. Maconomy stays your single source of truth, and Cinode reflects it without anyone copying data across.

Sales, delivery and reporting teams see the same customer list, the same active projects and the same pipeline state as the rest of the business, every time they log in.

Automatic, scheduled sync of customers and projects from Maconomy into Cinode. Independent schedules for each, so you can refresh customers daily and projects hourly if that fits your business.

Flexible field mapping that adapts to how your Maconomy environment is structured. You decide which Maconomy fields populate which Cinode fields, including combining several fields into one where it makes sense.

Project filtering so only the work you care about flows through. Active projects only, specific project types, certain customers, your rules.

Automatic placement of new projects into the right pipeline and stage in Cinode, so your sales team does not have to sort them after the fact.

Efficient delta sync. Only records that have changed since the last run are pulled in, so the integration stays light even on large datasets.

Setup runs in three short stages: connect the two systems, configure customer sync, then configure project sync. Each stage is guided in the Cinode Marketplace.

In the Cinode Marketplace, open the Maconomy integration and run the Configuration step. This establishes the secure link to your Maconomy environment and only needs to be done once per company.

When prompted, connect to Cinode. A green indicator confirms the connection is active. Click Next to continue.

Customer sync keeps the customer list in Cinode aligned with Maconomy. New customers in Maconomy appear in Cinode automatically, and updates to existing customers flow through on the next refresh.

Set the Customer Refresh Schedule to control how often the sync runs. Keep it on Never while you confirm your field mappings, then switch to Hourly or Daily once you are happy.

Define how Cinode recognises a customer using Customer ID Components, one or more Maconomy fields that together form a unique identifier. Common choices include the customer number, organisation number, or a combination such as region plus customer number. If you use more than one component, the Customer ID Separator is the character placed between them.

Choose whether Cinode should treat that identifier as External (Maconomy's ID, stored as externalId in Cinode) or Internal (Cinode's own ID). External is the right choice for most setups, since Maconomy is the master system.

Finally, map your Maconomy fields to Cinode fields under Customer Field Mapping. Most mappings are one-to-one (for example, customername to name), but you can also combine several Maconomy fields into a single Cinode field where needed.

Project sync brings the right projects from Maconomy into Cinode and lands them where your team expects to see them. New projects appear in the pipeline stage you choose, and existing projects stay up to date as Maconomy changes.

The Project Refresh Schedule runs independently from customers, so you can pick whatever cadence suits your business.

Use Project Filters to decide which projects flow through. Build your own rules using AND, OR and NOT conditions with a full set of operators (equals, not equals, greater than, less than, true, false). Typical uses include only syncing active projects, only certain project types, or only projects belonging to specific customers.

Just like customers, projects need an identifier. Use Project ID Components and Project ID Separator to build a unique key, and Cinode Project ID to choose External or Internal matching.

Map your Maconomy project fields to Cinode under Project Field Mapping, then choose where new projects should land using Cinode Project Pipeline. Both the pipeline and the default stage are configurable.

Field mappings support multi-field templates if a single Cinode field should be populated from several Maconomy fields. Use placeholders like {0} and {1} in the order the fields are listed. For example, {0} - {1} combines a customer number and customer name with a separator.

If you have several ID components, the separator joins them into a single value:

Each scheduled run pulls only records that have changed in Maconomy since the previous run, with a short overlap window to catch any updates that landed close to the previous execution. This keeps the integration fast and lightweight, even on large customer or project lists. Change detection relies on the transactiontimestamp field on Maconomy records.

Check that all required Maconomy fields are added in Customer Fields → Source.

Verify that the Cinode Customer ID matches the ID type provided by Maconomy, and confirm that the transactiontimestamp field exists on the record and updates whenever the record changes.

Confirm that Cinode Project Pipeline is set to the correct pipeline and default stage. New projects from Maconomy always land in that stage, and subsequent stage changes happen in Cinode.