Sage Intacct Real-Time Webhooks

Back to Webhooks

Overview

By default, Rutter picks up changes in Sage Intacct during Incremental Syncs. With real-time webhooks, Sage Intacct notifies Rutter as soon as a record is created or updated, and Rutter sends you the usual webhooks for that change within seconds. Using webhooks allows you to reduce your sync frequency while still ensuring your data is fresh.

Notes:

  • You must set up webhooks for each Sage Intacct customer. The process is simple but requires some action from your customers.
  • Real-time webhooks are supported only by our Sage Intacct v2 (REST) implementation. Our Sage Intacct v1 implementation does not support them.

Sage Intacct real-time webhooks are Sage Intacct Triggers that live in each Sage Intacct company you connect. There are two ways to create them:

To configure your application to receive Rutter events, see Webhook Setup. To verify events sent to your endpoint, see Webhook Security.

Who Does What

The setup is split between you and your end user:

  • You (the Rutter customer) prepare the setup: download the webhook package for Option 1, or gather the values in Prerequisites and build the webhook URL for Option 2.
  • Your end user (the business that owns the Sage Intacct company) installs the package or creates the triggers in their own Sage Intacct company. Triggers live inside each Sage Intacct company, so only a user with Platform Services access to that company can create them.

How It Works

  1. A record is created or updated in Sage Intacct (e.g., an AP bill is posted).
  2. The Sage Intacct Trigger on that object sends the event to Rutter, signed with your Sage Intacct application's client_secret.
  3. Rutter verifies the signature and fetches the latest version of the record from Sage Intacct.
  4. Rutter sends your usual webhooks, such as BILL_CREATED or BILL_UPDATED, with the same payloads as changes found during an Incremental Sync.

Supported Objects

Each Rutter object is driven by a trigger on the listed Sage Intacct object:

Rutter ObjectSage Intacct Object
AccountsGLACCOUNT, BANKACCOUNT, CHECKINGACCOUNT, SAVINGSACCOUNT, CREDITCARD
Bank DepositsDEPOSIT
Bank TransfersFUNDSTRANSFER
Bill Credit MemosAPADJUSTMENT
Bill PaymentsAPPAYMENT
BillsAPBILL
ClassesCLASS
CustomersCUSTOMER, CONTACT
DepartmentsDEPARTMENT
EmployeesEMPLOYEE
ExpensesCCTRANSACTION
Invoice Credit MemosARADJUSTMENT
Invoice PaymentsARPAYMENT
InvoicesARINVOICE
ItemsITEM
Journal EntriesGLBATCH
LocationsLOCATION
ProjectsPROJECT
SubsidiariesLOCATIONENTITY
TasksTASK
Tax RatesTAXDETAIL (not delivered in real time, see note below)
VendorsVENDOR

Tax Rates

Sage Intacct does not run triggers when a tax detail (TAXDETAIL) is edited, so changes to Tax Rates are not delivered in real time. They are picked up during Incremental Syncs.

The webhook package is a Sage Intacct Platform Services application that creates a trigger and template for each Supported Object that the Rutter Connection is configured to sync and that is available in the Sage Intacct company. Each package is built for one Rutter Connection and leaves out objects the Connection does not sync, as well as unavailable objects, such as PROJECT when the Projects module is not enabled.

Prerequisites for Option 1

  • An active Rutter Connection for the Sage Intacct company. Rutter matches each event to Connections by Sage Intacct company ID, so events from a company with no Connection are ignored.

Step 1: Download the Package

  1. In the Rutter Dashboard, go to Platforms and open Sage Intacct (v2).
  2. Open the Webhooks tab.
  3. Find the Connection for the Sage Intacct company and click Download Webhook Package.
  4. Send the downloaded .xml file to your end user.

The package uses the client_id saved for Sage Intacct (v2) in the Rutter Dashboard, so save your Sage Intacct application's client_id and client_secret there first (see our Sage Intacct v2 Guide).

Step 2: Install the Package

Instruct your customer to do the following:

  1. In Sage Intacct, go to Platform Services → Applications.
  2. Click Install from XML, select the package file, and confirm the install.

The triggers are active as soon as the install finishes. To pick up objects added in a newer package, install the new file the same way; it updates the existing application in place.

Option 2: Create Triggers Manually

Prerequisites for Option 2

  • An active Rutter Connection for the Sage Intacct company. Rutter matches each event to Connections by Sage Intacct company ID, so events from a company with no Connection are ignored.
  • Your Rutter organization ID. In the Rutter Dashboard, go to Settings → Organization and click Copy Org ID.
  • Your Sage Intacct application's client_id. Your end user enters it as each trigger's Client ID. It's the same client_id saved for Sage Intacct (v2) in the Rutter Dashboard. It isn't secret, but never share the client_secret.

Step 1: Build Your Webhook URL

Every trigger posts to the same Rutter URL. Replace <YOUR_ORGANIZATION_ID> with your Rutter organization ID. One URL serves every Sage Intacct company connected to your Rutter organization.

Webhook URL
1
https://production.rutterapi.com/versioned/webhooks/ingest/sage_intacct_v2?oid=<YOUR_ORGANIZATION_ID>&version=2025-02-28

Send your end user this URL and your Sage Intacct client_id.

Step 2: Create a Trigger on the Object

Instruct your customer to do the following:

  1. In Sage Intacct, go to Platform Services → Objects.
  2. Select one of the Supported Objects (for example, AP bill for Bills).
  3. Open the Triggers tab and click New trigger. If the object has no Triggers tab, it does not support triggers.
  4. Select HTTP post as the trigger type and click Next.
Triggers section of a Sage Intacct object with the New trigger linkSage Intacct trigger type selection with HTTP post selected

Step 3: Configure the Trigger

Instruct your customer to fill in the trigger fields as follows:

FieldValue
This trigger is deployedEnabled. The trigger does not fire otherwise.
Trigger activationAfter create and After update
Trigger nameSomething descriptive, for example Rutter - AP Bill
Use webhook deliveryEnabled
Client IDThe Sage Intacct client_id from Prerequisites
EncodingJSON
Target URLThe webhook URL from Step 1
Sage Intacct trigger configured for Rutter real-time webhooks

The Client ID must match your Rutter Dashboard

Sage Intacct signs each delivery with the client_secret of the application whose Client ID is set on the trigger. Rutter verifies that signature against the client_secret saved in the Rutter Dashboard and rejects any request that fails, so the trigger's Client ID must belong to that same application.

Step 4: Assign an HTTP Post Template

A trigger does not fire until it has a document template. The template tells Rutter which record changed. Instruct your customer to do the following:

  1. Next to Document template, click + to create a new template and enter a template name.
  2. Set Template type to HTTP post.
  3. Set the template body to the snippet below, replacing APBILL with the object's name from Supported Objects.
  4. Save the template and select it on the trigger.
Template body
1
{"key": "{!APBILL.RECORDNO!}"}

Step 5: Set the Condition Formula and Save

Instruct your customer to do the following:

  1. Set Trigger condition formula to true so the trigger fires for every event on the object. You can narrow it later, for example to posted invoices only.
  2. Save the trigger.
Sage Intacct trigger condition formula set to true

Step 6: Repeat for Every Object

Instruct your customer to repeat Steps 2 to 5 of Option 2 for every Sage Intacct object in Supported Objects that you want real-time updates for. Each object needs its own trigger and its own template. Rutter ignores events for objects that the Connection is not configured to sync.

Deletions

Deletions are not delivered through real-time webhooks for Sage Intacct. Deleted records are detected during Incremental Syncs; see Monitoring Deleted Objects.

FAQ

1. How can I check whether webhooks are coming in?

  1. Create or update a record for a Supported Object in the connected Sage Intacct company.
  2. In the Rutter Dashboard, open Webhook Logs and filter by the Connection and expected webhook type, such as BILL_CREATED or BILL_UPDATED.
  3. Look for a new event matching the record you changed and inspect its payload. Check your receiving endpoint's logs to confirm your application received the event.

Webhook Logs show events Rutter sends to your application, rather than the incoming requests from Sage Intacct. Events found during Incremental Syncs also appear here, so look for an event within seconds of your test change to check the real-time flow. If no event appears, follow the checks in Why am I not receiving webhooks after a change in Sage Intacct?.

2. Why am I not receiving webhooks after a change in Sage Intacct?

If you installed the webhook package, check that the Rutter Real-Time Webhooks application appears in Platform Services → Applications and that the object is in the package; objects the Connection was not configured to sync or that were unavailable in the company when you downloaded it are left out. For manual triggers, check that the trigger is deployed, has a document template assigned, and that its condition formula evaluates to true for the change. Also confirm the Sage Intacct company has an active Rutter Connection, and that the object is configured to sync in the Rutter Dashboard.

3. Why are events from my trigger rejected?

The trigger's Client ID belongs to a different Sage Intacct application than the client_id and client_secret saved in the Rutter Dashboard. Update the trigger's Client ID to match.

4. Why does the Dashboard say Rutter can't access the Sage Intacct company?

Rutter checks which objects the company has before building the package. If that check fails, the Connection usually needs to be reauthorized. Reconnect it through Rutter Link, then download the package again.

5. What happens if Rutter is temporarily unavailable?

Sage Intacct retries a delivery up to 4 times if it does not receive a successful response.

Sage Intacct Real-Time Webhooks