Building integrations

You’ve designed the process and configured the agent. The agent can read PDFs, but it can’t reach your ERP, your vendor master, or your ledger on its own. Connectors are the bridge — reusable connections to outside systems that an agent or a process step can call. You set them up once at Settings → Integrations, then hand them to whatever needs them. You’ll add three for the invoice flow.

The connector catalog

Screenshot placeholderSettings → Integrations — the connector catalogReplace with real capture from app.superagent.studio

At Settings → Integrations (organization level) you’ll find your connectors and the catalog of types you can add. For a new organization the list is empty. We’ll add three:

Connector	Type	What it does
ERP — Purchase Orders	API Call	Looks up a PO by number, returns vendor and total
ERP — Vendor Master	API Call	Verifies a vendor name and tax ID is on file
Accounting — Ledger	API Call	Posts the approved invoice to the right GL account

Add the first connector

Screenshot placeholderAdd Integration — connector type, name, scope, and setupReplace with real capture from app.superagent.studio

Click Add Integration and set:

• Connector Type — API Call (HTTP/REST) for an HTTP-based ERP API (other types cover Slack, databases, object storage, and more).
• Name — erp-purchase-orders.
• Project Scope — organization-wide, or limited to one project.
• Setup — the endpoint and the credentials, which are stored as a secret and referenced by name.

Save, and use the connector’s test action to confirm it can reach the ERP.

Give it to the agent

Screenshot placeholderThe agent's Tools & Integrations tab with connectors addedReplace with real capture from app.superagent.studio

Open the agent you configured on the previous page and go to its Tools & Integrations tab. Add the connectors the agent should call — ERP — Purchase Orders and ERP — Vendor Master — and click Save Tool Configuration. The agent can now call them as tools while it reasons.

The third connector — Accounting — Ledger — doesn’t go on the agent. It’s called by the post-to-ledger step at the end of the process, not by the extraction agent. Bind it there instead: a service task of type SDK Connector.

One connector, many uses

A connector lives at the organization level. Set its Project Scope to organization-wide and any project’s agents and processes can use it — you manage the connection (and its credentials) once.

Next

Running and monitoring →Deploy the process, watch invoices flow through it, and dig into a specific run when something looks off.