Resources · Make integration

Sage Intacct Make integrationAutomate Sage Intacct with Make.

Can Make keep your Sage Intacct records in sync with the rest of your stack? The Sage Intacct Make integration gives you 7 modules to watch, find, create, update and delete records. This guide is for finance and ops teams, and it walks you from the connection to a live first scenario.

Enterprise app This app is reserved to Make's Enterprise plan.

Try the Sage Intacct integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Sage Intacct Make integration let you automate?

The Sage Intacct Make integration links your Intacct company to Make, so records can move in and out of the ERP without anyone retyping them. You build a scenario (the automation itself, a chain of modules) and each module does one job: spot an updated record, look one up, create it, change it or remove it.

Push changes to the rest of the business. Watch Records notices when a record is updated in Sage Intacct. Behind it, Get a Record pulls the full record, and any other app in your scenario can receive the change, a spreadsheet for the controller or a message for the sales team.

Feed the ERP from outside. When a deal closes in a CRM or a form comes in, Create a Record writes the matching entry into Sage Intacct. Search Records runs first to check whether the record already exists, and Update a Record corrects it instead of creating a duplicate.

Reach the rest of the API. The listed modules cover generic records. For any other endpoint in the Sage Intacct API, Make an API Call reuses the same connection.

Two limits to know up front. The Sage Intacct app is reserved for the Make Enterprise plan, and the app side needs a paid Sage Intacct account plus an active Web Services developer license. Before you commit, the Make pricing page explains the plans. The same app may also exist as an n8n node; the n8n vs Make comparison lays out the differences. If you would rather hand the build to someone, the Make agency team can take it on.

Connect

How do you connect Sage Intacct to Make?

  1. 01

    Open the connection window

    Add any Sage Intacct module to your scenario and click Create a connection. A connection is your Sage Intacct account linked to Make once; every Sage Intacct module in every scenario reuses it afterward.

  2. 02

    Name it and fill in the credentials

    Give the connection a name you will recognize later, for example the company it points to. Then enter the values Sage Intacct gives you in the Client ID and Client Secret fields, or authorize Make on the Sage Intacct page if it asks you to.

  3. 03

    Save and check the module

    Click Save. Make returns to the module, which now shows the new connection in its list. From here, Make can read what your account exposes and offer it in the module fields.

First scenario

Your first scenario with Sage Intacct

GoalWhen a record is updated in Sage Intacct, Make fetches the full record and hands it to the next app.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Search for Sage Intacct and pick Watch Records as the first module.

  2. 02

    Link the account and set the trigger

    Click Create a connection and finish the three steps above. Then fill in the Watch Records fields; once the connection exists, Make lists what it can read in your company.

  3. 03

    Add Get a Record

    Click the + on the right of the trigger and add Get a Record. Map the record ID from Watch Records into it, so each bundle (one updated record) is fetched in full.

  4. 04

    Send it somewhere useful

    Add the module of the app that should receive the data, such as a sheet or a chat tool. Map the fields you care about from Get a Record into it.

  5. 05

    Test with Run once

    Update a record in Sage Intacct, then click Run once. Open the bubble above each module to read the bundles it received and confirm the data landed where you expected.

  6. 06

    Schedule and switch it on

    Open the clock on Watch Records to set the schedule, which is every 15 minutes by default. Switch the scenario on, and Make will check for updated records at that pace.

Triggers

What can start a Sage Intacct scenario?

1 module starts a scenario when something happens in Sage Intacct. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Sage Intacct as soon as it happens.

Sage Intacct1Watch Records

Watch Records

Scheduled trigger

In Make“Triggers when a record is updated.”

Watch Records starts your scenario with every Sage Intacct record that has been updated since the last check, so each change reaches the rest of your tools as its own bundle. It is the only trigger in the app, so any scenario that has to react to a change in the ERP starts here.

How it fires
scheduled. Make checks the app on the scenario's schedule, every 15 minutes by default, as the clock badge on the module shows.
When to use it
a customer or vendor record gets corrected in the ERP and a CRM or a shared sheet has to reflect it.
Watch out
it is scheduled, so a change shows up at the next run of the scenario, not the second it is saved in Sage Intacct.
Modules

What can Make do in Sage Intacct?

Sage Intacct gives you 6 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Records

5 modules
Sage Intacct1

Search Records

Search

In Make“Retrieves a list of records optionally filtered by criteria.”

Search Records finds the Sage Intacct records that match the criteria you set, or returns the whole list when you leave the filter empty. The result can be zero, one or many bundles, and each one moves through the rest of the scenario separately.

When to use it
before creating a record from a form or a CRM, to check whether that customer already exists.
Watch out
without a filter, every returned record costs an operation in the modules that follow.
Sage Intacct2

Create a Record

Action

In Make“Creates a new record.”

Create a Record adds a new entry to Sage Intacct from data that arrives elsewhere, so nobody has to rekey it in the ERP. You map the values from earlier modules into the fields Make shows once the connection is set.

When to use it
a deal is marked won in the CRM and the matching customer has to exist in accounting.
Watch out
put Search Records in front of it if the same data can arrive twice, or you will end up with duplicates.
Sage Intacct3

Get a Record

Action

In Make“Retrieves a record by its ID.”

Get a Record fetches one Sage Intacct record in full when you already hold its ID. It returns a single bundle, which suits the case where another app, a sheet or a form, only hands you that identifier.

When to use it
a trigger tells you a record changed and you need all its details before sending them on.
Watch out
it needs an exact ID; if all you have is a name or an email, use Search Records instead.
Sage Intacct4

Update a Record

Action

In Make“Updates a record by its ID.”

Update a Record changes an existing Sage Intacct record, identified by its ID, with the values you map in. Your ERP stays in line with the system where the data actually changes, without a manual correction pass.

When to use it
a customer updates their billing address in the CRM and accounting must follow.
Watch out
the module does not look the record up for you, so chain it after Search Records or Get a Record to supply the ID.
Sage Intacct5

Delete a Record

Action

In Make“Deletes a record by its ID.”

Delete a Record removes a Sage Intacct record by its ID. It helps you clean up entries created by mistake in a test run or by a scenario that fired on the wrong data.

When to use it
a test record was created during setup and should not stay in the live company.
Watch out
treat every deletion as final, add a filter in front of it and try it on a harmless record with Run once first.

Other

1 module
Sage Intacct6

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets you reach any endpoint of the Sage Intacct API directly from your scenario, reusing the connection you already created. It fills the gap whenever the five record modules and the search do not cover what you need.

When to use it
you need an operation the listed modules leave out, and the Sage Intacct API documentation lists an endpoint for it.
Watch out
you write the request yourself, so read the endpoint's documentation before running it.
Need help

Need help automating Sage Intacct with Make?

A person reads every message.

FAQ

Sage Intacct and Make: common questions

01Is the Sage Intacct Make integration free?
No. The Sage Intacct app is reserved for the Make Enterprise plan, so the Free plan cannot use it at all. The Free plan still gives you 2 active scenarios with the 3,000+ standard apps, which is enough to learn the editor before moving to Enterprise. On the Sage Intacct side, you also need a paid account. Make counts usage in operations, one per module run on one bundle, and the paid plans measure them per month. Keep that in mind before planning a project: without Enterprise, no Sage Intacct module will show up in your scenarios.
02What do you need to connect Sage Intacct to Make?
Three things. A Make account on the Enterprise plan, a paid Sage Intacct account, and an active Sage Intacct Web Services developer license. With those in hand, you add a Sage Intacct module, click Create a connection, enter the Client ID and Client Secret values, and save. The connection is then shared by every Sage Intacct module you add later, in any scenario. If the connection fails, check the license and the two credential values first, since those are the prerequisites the Make documentation names.
03Does the Sage Intacct trigger in Make react in real time?
No. Watch Records is a scheduled trigger: Make asks Sage Intacct for updated records each time the scenario runs, instead of being notified the moment a change happens. A new scenario runs every 15 minutes by default. Paid plans, including Enterprise, allow an interval as short as 1 minute, so you can tighten the delay if your process needs it. On the Free plan the minimum interval is 15 minutes, but that plan cannot run this app anyway, so plan for Enterprise from the start.
04What if a Sage Intacct module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Sage Intacct API with the connection you already set up, so you are not limited to the five record modules and the search. Check the Sage Intacct API documentation for the endpoint you need, build the request in the module, and test it with Run once before switching the scenario on. Each run of the module counts as one operation, like any other module in the scenario.
05Should you use Make or n8n for Sage Intacct?
It depends on your criteria. On Make, Sage Intacct comes with 7 ready modules, including a scheduled trigger, and requires the Enterprise plan. The same app often has an n8n node as well, so compare the modules each side offers against the records you actually need to move. If Make already runs your other automations, keeping Sage Intacct in the same place avoids juggling two tools. Look at the actual records your finance team needs to move, then check which tool covers them with the least custom work.
Same platform

Other docs you might need on this stack.

Browse all integrations