Sage Intacct: Attach Document

Description

Attaches supporting documents to Sage Intacct records over your Sage Intacct connection, routed through PlaidCloud’s shared ERP write pipeline. Each row in the source table is one file — its bytes, its name, and the key of the Intacct record it attaches to — which the step creates as a Sage Intacct supporting document (supdoc) and links to that record. Validate Only checks every row without creating anything in Intacct; the result table records the outcome per attachment.

Use it to push files a workflow already has in hand — a rendered invoice PDF, a scanned receipt, an exported report — onto the Intacct transactions or records they belong with, in the same run that produces or posts them. It pairs naturally with Intacct: Post Journal Entry: post the entries, then attach their backup with the Intacct key each post returned.

Data-Shape Contract

Build the attachments table upstream with standard steps so each row is one complete file bound to one record:

parent_key — the Sage Intacct record the file attaches to. One file, one parent per row; attach the same file to several records by repeating it on several rows.
file_name — the supporting document’s file name, including extension (invoice-1043.pdf).
mime_type — the file’s content type (application/pdf, image/png), so Intacct stores and serves it correctly.
content_base64 — the file’s bytes, base64-encoded, in the row.

Configuration

Connection

Sage Intacct Connection — the Sage Intacct connection to attach through. Only Sage Intacct connections are offered; the same connection reads from and writes to Intacct.
Environment — the connection’s environment.

Data

Attachments Table — the source table above: one row per file, with parent_key, file_name, mime_type, and content_base64.
Result Table — output table id: one row per attachment with parent_key, file_name, supdoc_id, status, message.
Validate Only — checked by default. Preflight only; checks each row and writes the result table, but creates no supporting document in Intacct. A step configuration that omits this field entirely — for example one authored through the REST API, MCP, or a workflow bundle import — also defaults to Validate Only rather than a live attach.
Continue On Error — checked by default. Keeps attaching the remaining files after one fails; unchecked stops at the first failure.

Result Table

Every run — Validate Only or real — writes one row per source row to the result table:

Column	Description
`parent_key`	The Intacct record this attachment targets.
`file_name`	The file name from the source row.
`supdoc_id`	The Sage Intacct supporting-document id created for the file, when the attachment succeeded.
`status`	The outcome for this row — validated, attached, or failed.
`message`	A short, sanitized description of what went wrong, when the row failed.