NetSuite with Abstra: take your processes beyond the ERP

Connecting NetSuite to your processes has never been more straightforward.

With Abstra's connector, you can bring the ERP into your operational workflows and start automating tasks that were previously distributed across systems, emails, and parallel controls.

The result is simple: less manual effort and more fluidity in operations.

How connectors work in Abstra

Within Abstra, connectors are the layer that enables integrating external systems in a structured way.

They function as reusable connection points within workflows, allowing you to interact with NetSuite without having to build complex integrations from scratch.

With this, you can:

• Query data directly in the ERP
• Create or update records automatically
• Work with documents within NetSuite
• Integrate the ERP with other systems in your day-to-day operations

All of this within a single workflow.

The NetSuite connector in practice

Integration with NetSuite was designed to cover different operational needs, from simple queries to complete workflows.

It combines different ways of accessing the ERP:

• SuiteQL for structured queries
• REST APIs for creating and updating records
• SOAP for specific operations (such as attachments)
• File Cabinet for file management

This combination allows you to handle both data and documents in an integrated way.

File management within NetSuite

In day-to-day finance, documents are part of the process — invoices, contracts, receipts.

With Abstra, you can structure this workflow within NetSuite itself.

Sending files

Files can be sent directly to the File Cabinet with format and content control:

import base64
from abstra.connectors import run_connection_action

with open("invoice.pdf", "rb") as f:
    encoded = base64.b64encode(f.read()).decode('utf-8')

run_connection_action("netsuite", "add_file", {
    "name": "invoice.pdf",
    "content": encoded,
    "fileType": "PDF"
})

Query and organization

Files can be searched via SuiteQL, allowing you to locate documents by name, date, or other criteria.

This facilitates both organization and the use of these files in other processes.

Association with records

It's also possible to link documents to specific transactions, such as purchase orders or invoices.

run_connection_action("netsuite", "attach", {
    "attachTo": {"type": "purchaseOrder", "internalId": "501628"},
    "attachedRecord": {"type": "file", "internalId": "654321"}
})

This link is made via SOAP operations and ensures that documents remain associated with the correct context within the ERP.

Query attachments

Files attached via SOAP follow a different query logic.

For this reason, Abstra provides a specific action to retrieve these documents from transactions.

Working with purchase orders

Another common use is the automation of purchase orders.

With the connector, you can interact with POs at different levels.

Search and filter orders

Using SuiteQL, it's possible to create queries with different filters:

• Status
• Dates
• Vendors
• Custom fields

Access complete data

You can retrieve all information from an order, including items, values, and approval status.

This allows you to use this data in validations or subsequent workflows.

Create orders automatically

Orders can also be created directly via API:

po_result = run_connection_action("netsuite", "post_purchase_order", {
    "data": {
        "entity": {"id": vendor_id},
        "subsidiary": {"id": subsidiary_id},
        "tranDate": "2025-01-01"
    }
})

Using custom fields

NetSuite allows you to adapt the ERP with specific fields (such as custbody).

These fields can be used to:

• Create business rules
• Filter data
• Adapt the workflow to your company's reality

A complete workflow example

By combining these capabilities, it's possible to structure a complete process within Abstra:

1. Purchase order creation
2. Upload of the related document
3. Association of the file with the order
4. Workflow continuation with validations

All of this within a single integrated workflow.

How to get started

You can work with the connector in two ways:

With AI support

Describe what you want to do and Abstra generates the workflow automatically.

Example:

"Create an order in NetSuite and attach the corresponding contract"

Via code

For more specific scenarios:

from abstra.connectors import run_connection_action

result = run_connection_action(
    "netsuite",
    "query",
    {"query": "SELECT id FROM vendor FETCH FIRST 10 ROWS ONLY"}
)

Best practices

Some care helps keep the workflow more organized:

• Use clear names for files
• Ensure correct encoding (base64)
• Validate permissions in NetSuite
• Structure SuiteQL queries well
• Handle errors in the workflow

Conclusion

The integration between NetSuite and Abstra expands how you work with the ERP.

Instead of acting only on isolated records, you start building complete workflows, connecting data, documents, and decisions within the same environment.

This facilitates the organization of processes and opens space for more structured evolution over time.

FAQ — ERP Integration with Abstra

What does it mean to integrate an ERP into Abstra?

Integrating an ERP into Abstra means connecting the system to automated workflows, allowing data, documents, and actions to be part of a continuous process.

In practice, this goes beyond "querying data".

You can structure complete workflows that involve reading, validating, decision-making, and updating in the ERP — all within the same environment.

Does Abstra replace the ERP?

No.

Abstra functions as a complementary layer to the ERP.

The ERP remains the system of record and control (financial, accounting, operational), while Abstra acts in orchestrating processes around it — automating tasks, connecting systems, and organizing workflows.

Do I need a technical team to integrate an ERP with Abstra?

Not necessarily.

Abstra allows two forms of construction:

• Via AI (natural language description)
• Via code (Python), for more advanced scenarios

This allows financial and operational teams to participate directly in building workflows, with technical support when needed.

Which ERPs can be integrated?

Abstra has ready-made connectors for various ERPs, including:

• SAP
• NetSuite
• Other systems such as Omie, Bling, Sankhya, among others

Additionally, it's possible to integrate any system that has an accessible API or interface.

Is it possible to connect the ERP with other systems?

Yes.

One of the main advantages is precisely connecting the ERP with other tools, such as:

• Banks
• Email
• Spreadsheets
• BI tools
• CRMs
• External portals

This allows you to create end-to-end integrated workflows.

Can integration automate complete processes?

Yes.

With Abstra, you can automate entire processes, such as:

• Accounts payable and receivable
• Financial reconciliation
• Closing
• Procurement (P2P)
• Billing and collection

Automation includes everything from data entry to validations, exceptions, and ERP updates.

How does Abstra handle business rules?

Rules are defined directly in the workflow.

You can configure validations, conditions, approvals, and exceptions — ensuring the process follows company logic.

This allows you to adapt automation to operational reality without rigidifying the workflow.

Is it safe to integrate the ERP with Abstra?

Yes.

The platform uses:

• Secure authentication (e.g., tokens, OAuth)
• Access control by user and workflow
• Complete execution logs
• Traceability of actions taken

This ensures governance and visibility over automated processes.

What about audit and control?

Every execution within Abstra is recorded.

This means you can:

• Know what was executed
• When it happened
• Which data was used
• Which action was taken

This level of traceability facilitates audits and increases operational control.

Does Abstra work with existing processes?

Yes.

The idea is not to replace everything, but to evolve what already exists.

You can start by automating specific parts of a process (such as document validation or ERP integration) and expand gradually.

How long does it take to implement an integration?

It depends on process complexity.

Simpler cases can be implemented quickly (days), while more structured workflows may take longer.

The important thing is that implementation can be incremental, without the need for large initial projects.