Connect to Sage Intacct

Connect PlaidCloud to Sage Intacct and pull financial and accounting data. This guide takes you from Web Services credentials to a working pull. For the field reference, see the Sage Intacct REST Connector.

Prerequisites

You need, in Sage Intacct:

• Web Services enabled for your company — Sage support provisions your Sender ID and Sender password, which become the connection’s Client ID and Client Secret.
• A Web Services user for PlaidCloud, with permissions on every object your queries will read.
• Your Company ID.

Record the Company ID, Web Service User Username, Client ID (Sender ID), and Client Secret (Sender password) before you start.

Caution

The Client ID/Client Secret and the Web Service User Username are separate. The Client ID/Client Secret authenticate the application to Sage; the Web Service User Username, combined with the Company ID, authenticates the login within your company. All three are required, and the Client ID/Client Secret are secrets.

Create the Connection

PlaidCloud has a dedicated Sage Intacct connection type — you don’t configure this as a generic REST connection.

1. Open Tools > Connections and click New Connection.

2. Choose Sage Intacct from the menu.

3. Fill in the fields:

   Field	Value
   Name	A friendly name, e.g. Intacct Prod.
   Client ID	Your Intacct Sender ID.
   Client Secret	Your Intacct Sender password.
   Web Service User Username	The Web Services user login.
   Company ID	The Intacct company you’re connecting to.

4. Click Create.

Smoke-Test the Connection

Confirm the credentials work before building on them.

1. Add a REST Request step to a workflow and set Connection to your Sage Intacct connection.

2. Point it at a small, bounded read against an object your user can see.

3. Click Send Test Request.

Caution

Use Send Test Request, not the Preview tab. A green result means the Client ID/Client Secret and the Web Service User Username both authenticated. If it errors, the message carries Sage’s own detail — usually a permission gap on the Web Services user or a bad Client ID/Client Secret.

Note

Sage Intacct requests are single-request — there is no pagination to configure. Leave the Pagination controls alone.

Pull Data

For routine pulls, Sage Intacct has dedicated import steps that map straight to Intacct objects:

• Import Sage AP — AP bill headers
• Import Sage AP Lines — AP bill line detail
• Import Sage Intacct Query — a query against any Intacct object

Pick the step, choose your Sage Intacct connection, set the object or query, and run it. As with any import, define amount and date columns with their real types so they arrive typed rather than as text.

Verify and Schedule

1. Run the step and check the target table — row counts and column types.

2. For an ongoing feed, schedule the workflow.

Troubleshooting

Symptom	Likely cause
Authentication failure	A wrong Client ID/Client Secret (provisioned by Sage) or a wrong Web Service User Username.
Permission / object-not-found error	The Web Services user lacks permission on the object being read.
Empty or unexpected result	A wrong Company ID.

Related

• Analyze Sage Intacct Financials — day-one tutorial: pull a trial balance and shape it into a departmental P&L on a dashboard.
• Sage Intacct REST Connector — field reference.
• REST Request Step
• Create and Manage a Connection