Integrations / NetSuite

NetSuite

NetSuite SuiteTalk REST records for customers, vendors, employees, invoices, sales orders, and finance operations evidence.

OAuth 1.0

Indexes

Actions

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

A NetSuite account with REST/TBA enabled.

Administrator who can create an integration record and a token-based authentication role.

Vendor setup

Get the credential

Create an integration record

In NetSuite, go to Setup → Integration → Manage Integrations → New. Name it for Telara. Enable Token-Based Authentication. Copy consumer key and consumer secret — NetSuite shows them once.

Create a TBA token

Create (or pick) a role with the permissions this page lists. Assign it to a user, then Setup → Users/Roles → Access Tokens → New. Copy token id and token secret once.

Paste in Telara

Settings → Integrations → NetSuite. Enter account id, consumer key/secret, and token id/secret. Realm is the account id.

In Telara

Connect in Telara

OAuth 1.0

NetSuite token-based OAuth 1.0a fields for SuiteTalk REST request signing.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Fields Telara asks for

Account ID
Consumer Key
Consumer Secret
Token Id
Token Secret

Knowledge

What gets indexed

Resource	Coverage
Customer	Partial — not every record the vendor holds is synced
Invoice	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Customer	Up to 1 day	Removed records disappear on the next full sync
Invoice	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Customer, Invoice.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Sandbox and production accounts are different integration records and different tokens.

Missing REST web services on the role is the usual “auth works, no records” failure.