Connectors

Sage Intacct

Manage Sage Intacct Accounts Receivable customers and invoices (including the submit / reverse / reclassify / generate-PDF workflows) through the REST API, with generic requests for everything else. Covers OAuth auth, the system key, and the ia::result envelope.

On this page

Connecting Sage Intacct Scope How Sage Intacct actions are structured Reading the response Customers Invoices Generic Request Example Step Name Step Reference Execution Settings Caching Locking

Connecting Sage Intacct

Every action needs a Sage Intacct connection configured with OAuth 2.0 (authorization-code) credentials for the Sage Intacct REST API. The access token is sent as a Bearer token automatically. Requests go to https://api.intacct.com/ia/api/v1.

Scope

This connector is deliberately narrow: it covers the Accounts Receivable customer and Accounts Receivable invoice objects only. Everything else in Sage Intacct (GL, AP, order entry, projects, other AR objects) is reachable through the Generic Request actions, or ask for more tags to be added to the connector's manifest.

How Sage Intacct actions are structured

Each action is one operation. They all appear under a single Sage Intacct group in the action picker (plus a Generic Request group) — this page splits them into Customers and Invoices for readability. Names read like "List", "Create", "Get" (retrieve one, operationId get-accounts-receivable-customer-key), "Update", "Delete", plus the invoice workflow actions "Submit", "Reclassify", "Reverse", "Generate PDF". Since the object name isn't in the action name, tell customer actions from invoice actions by their operation id / description.

Common fields:

key — path parameter on the Get / Update / Delete actions: Sage Intacct's system-assigned key for the record (a number like 81), not the user-facing id. Read it from {{<stepReference>.response.data['ia::result'].key}} on a list or create.
Request Body — a structured field for Create / Update / the workflow actions, plus an Override Request Body toggle and Request Body (Raw) text field. Sage Intacct objects are deep; Override Request Body with hand-written JSON is usually easiest.
Additional Query Parameters — the REST list query options go here: fields, filters, orderBy, size (page size), start (offset).
Additional Headers, Forward All Headers — as on every connector.

Reading the response

Every action's result is at {{<stepReference>.response...}} (see Step Reference): {{<stepReference>.response.status}}, {{<stepReference>.response.statusText}}, {{<stepReference>.response.headers.<name>}}, and {{<stepReference>.response.data.<field>}} for the body.

Sage Intacct wraps every REST response in an ia::result / ia::meta envelope. Because those keys contain ::, address them with bracket syntax:

A single record (Get / Create / Update) — {{<stepReference>.response.data['ia::result']}} is the record, e.g. {{<stepReference>.response.data['ia::result'].key}}, {{<stepReference>.response.data['ia::result'].id}}, {{<stepReference>.response.data['ia::result'].name}}.
A list — {{<stepReference>.response.data['ia::result']}} is the array; {{<stepReference>.response.data['ia::meta'].totalCount}} and {{<stepReference>.response.data['ia::meta'].count}} describe paging.
A delete — 204 No Content; confirm with {{<stepReference>.response.status}}.
A workflow action — the result payload for that operation under {{<stepReference>.response.data['ia::result']}}.

A non-2xx response does not fail the step — Sage Intacct returns 400 for most problems, with error detail at {{<stepReference>.response.data['ia::error']}} (an object with a code and a errors array). Branch on {{<stepReference>.response.status}}.

Customers

List — GET /objects/accounts-receivable/customer.
Create — POST /objects/accounts-receivable/customer. Body: the customer object; id and name are required. Example: { "id": "CUST-002", "name": "Starluck", "taxId": "12-3456789", "creditLimit": 50000, "status": "active" }.
Get — GET /objects/accounts-receivable/customer/{key}. key is the system key.
Update — PATCH /objects/accounts-receivable/customer/{key}. Send only the fields to change.
Delete — DELETE /objects/accounts-receivable/customer/{key}.

The customer object includes contacts (with default, billTo, shipTo sub-objects each holding a mailingAddress), creditLimit, onHold, paymentTerm, glGroup, and a parent reference for customer hierarchies.

Invoices

List — GET /objects/accounts-receivable/invoice.
Create — POST /objects/accounts-receivable/invoice. Body: the invoice header plus a lines array. Key header fields: customer ({ "id": "<customerId>" }), invoiceDate, dueDate (or paymentTerm), referenceNumber, description. Each line needs a glAccount (or dimensions), txnAmount, and optionally memo.
Get — GET /objects/accounts-receivable/invoice/{key}.
Update — PATCH /objects/accounts-receivable/invoice/{key}.
Delete — DELETE /objects/accounts-receivable/invoice/{key}.

Workflow actions (all POST /workflows/accounts-receivable/invoice/<action>, body identifies the target invoice, typically by key or id):

Submit (/submit) — submit a draft invoice for approval / posting.
Reclassify (/reclassify) — move a posted invoice's GL/dimension coding.
Reverse (/reverse) — reverse a posted invoice (body includes the reversal date).
Generate PDF (/generate-pdf) — render the invoice; the result carries a document reference / URL under ia::result.

Generic Request

Five actions — Generic GET / POST / PUT / PATCH / DELETE Request — for any Sage Intacct REST endpoint outside AR Customers and Invoices.

path — required, relative to /ia/api/v1, e.g. /objects/accounts-payable/bill, /objects/general-ledger/journal-entry, /services/core/query.
Request Body (Raw) — the JSON body for write methods (including the /services/core/query object-query payload).

Example

Generic POST Request, path /services/core/query, body { "object": "accounts-receivable/invoice", "fields": ["key","id","totalDue","state"], "filters": [{ "$eq": { "state": "posted" } }] } — query posted invoices, which the dedicated List action can't filter on state directly.

Also applies here

Step Name

What it's for

Every step in a workflow gets a name — either one you set or a default based on the connector and action (e.g. "Get Order Details", "Send Welcome Email"). It's shown throughout the UI and in your execution history, and it's also the source for the step's Reference — a camelCase identifier auto-generated from the name (e.g. "Get Order Details" → getOrderDetails) — which is what you actually use in {{...}} expressions to read this step's output from later steps. See Step Reference.

Rules

Must be at least 2 characters, and 50 characters or fewer.
Must be unique within the workflow — reusing a name that's already taken will be rejected, with a suggested alternative (e.g. "Get Order Details 2").
Can't be empty.

Tips

Prefer a descriptive, human-readable name over a generic one — "Get Order Details" is easier to work with later than "HTTP Request 2", especially once a workflow has a dozen steps.
Renaming a step updates every reference to it elsewhere in the workflow automatically.

Step Reference

Syntax

Any input field can reference earlier data using {{expression}}. The expression is evaluated as JSONata — so simple dot-paths and more advanced queries (filters, functions) both work.

Referencing a step's output

Use the step's Reference — a camelCase identifier auto-generated from its Name (e.g. "Get Order Details" → getOrderDetails), shown read-only wherever the step's fields are configured — followed by the field path. Elsewhere in these docs this general pattern is written as {{<stepReference>.field.path}}:

{{getOrderDetails.response.data.id}}
{{getOrderDetails.response.status}}

The raw display name won't work here even though it's what you see in the UI — {{Get Order Details.response.data.id}} isn't valid, since a bare name containing spaces isn't a single JSONata identifier. Always use the camelCase Reference.

You can also reference steps by position instead of by reference:

{{steps[0].response.data.id}}

Referencing trigger data

{{trigger.headers.authorization}}
{{trigger.body.customerId}}
{{trigger.query.page}}
{{trigger.params.orderId}}
{{trigger.method}}
{{trigger.path}}

Referencing workflow variables

{{variables.myVariable}}

See Variables for the full list of variable types and more examples, including connection-type variables.

Referencing runtime variables

A separate, mutable namespace written by the Variable connector while a run is in progress — not the same as the workflow-level variables above:

{{runtimeVariables.myVariable}}

Notes

If an expression can't be resolved (a typo in a step name, a field that doesn't exist), it resolves to an empty string rather than failing the workflow — check your execution history if a value comes through blank.
Object values are automatically JSON-stringified when interpolated into a string field.

Execution Settings

Fire-and-forget

When enabled, the workflow doesn't wait for this step to complete before moving to the next one. Use it for steps whose result nothing downstream depends on — logging, analytics, notifications — so they don't add latency to the steps that matter.

Continue on error

When enabled, a failure in this step doesn't stop the workflow — execution continues to the next step. The failure is still recorded in the execution history; this just controls whether it's fatal.

Combine the two for steps that are genuinely optional to the outcome: fire-and-forget so they don't add latency, continue-on-error so a failure in them (e.g. an analytics endpoint being briefly down) doesn't take down an otherwise-successful workflow run.

Caching

What it does

When enabled, a step's result is cached for a configurable TTL (time-to-live, in seconds). If the step runs again with the same effective cache key before the TTL expires, the cached result is returned instead of re-running the step.

Configuring it

Enabled — turn caching on or off for this step.
TTL — how long (in seconds) a cached result stays valid.
Cache key template — an expression (supporting the same {{...}} step reference syntax used elsewhere) that determines what counts as "the same call". By default this is based on the step's resolved input; a custom template lets you cache more narrowly or broadly than that.

When to use it

Good candidates are steps that call something slow or rate-limited but return the same answer for the same input within a short window — a lookup against a rarely-changing external system, for example. Skip it for steps whose result must always be fresh (anything involving live inventory, pricing, or payment state).

Locking

What it does

When enabled, only one execution of this step (for a given lock key) can run at a time. If a second execution tries to run the same step while a lock is held, it waits until the lock is released or the hold period elapses.

Configuring it

Enabled — turn locking on or off for this step.
Lock key — an expression (supporting the same {{...}} step reference syntax used elsewhere) that determines what counts as "the same resource". By default the lock is scoped to the step itself; a custom key lets you lock per-customer, per-order, or any other identifier that needs serialized access.
Period — how long (in seconds) the lock is held before it's automatically released, in case an execution doesn't complete normally.

When to use it

Use it whenever concurrent executions could race on the same resource — e.g. two workflow runs both trying to update the same order's status at once. A lock key scoped to the order id ensures only one of them proceeds at a time.