Netsuite: Destination Connector

[Mohith93]

Issue Type:
New Feature / Connector Request

Description

We need to build a NetSuite Destination Connector that will allow users to send data from Multiwoven to their NetSuite account. This connector will help users automate and streamline the process of syncing data such as sales orders, customer information, and transaction records into NetSuite.

Requirements

Authentication:
The connector should support Token-Based Authentication (TBA) or OAuth 2.0 to interact with the NetSuite API securely.

Configuration:
The connector should require the following configuration parameters:
account_id: The NetSuite account ID.
consumer_key: The consumer key generated in NetSuite for API access.
consumer_secret: The consumer secret associated with the consumer key.
token_id: The token ID generated in NetSuite for API access.
token_secret: The secret associated with the token.
Optional: application_id (used for tracking purposes in NetSuite).

Connector Features:
The destination connector should be able to:
Create or update records in NetSuite, such as:
Customers
Sales Orders
Invoices
Transactions

Allow users to map their data fields in Multiwoven to NetSuite’s data structure for the appropriate record type.

Provide feedback on the success or failure of the data sync.

API Interaction:
The connector should use the NetSuite REST API (preferred) or SuiteTalk Web Services (as an alternative) to send data.

Data Format:
The data sent to NetSuite must follow NetSuite’s required schema for each record type (e.g., customer, sales order, etc.). Ensure that field mappings can be defined in a flexible way, allowing users to map their source data fields to the corresponding NetSuite fields.

Error Handling:
The connector should handle errors gracefully, providing meaningful error messages for the user, including invalid token errors, schema validation issues, and field mapping errors.

Steps to Implement

Authentication Setup:
Implement Token-Based Authentication (TBA) or OAuth 2.0 authentication to enable secure communication with the NetSuite API.

Connector Configuration:
Create a config file that accepts the required NetSuite credentials (account_id, consumer_key, consumer_secret, token_id, and token_secret).

API Integration:
Implement the logic to send data to the relevant NetSuite API endpoints. Support record creation and updating for entities such as customers, sales orders, and invoices.

Field Mapping:
Develop functionality to allow users to map Multiwoven data fields to the appropriate NetSuite fields. This should allow flexible mapping configurations depending on the data and record type.

Error Handling & Logging:
Ensure comprehensive error handling for scenarios like authentication failures, missing or invalid data, or API rate limits.
Provide detailed logs that help users troubleshoot any issues during data sync.

Testing:
Write unit tests and integration tests to ensure the connector works as expected.
Simulate API interactions using mock responses to ensure robustness.

Documentation:
Provide a detailed document explaining how to configure and use the connector.
Include examples of data field mappings and sample payloads for sending different types of records.

Acceptance Criteria
The connector successfully sends data to NetSuite for the supported record types (customers, sales orders, invoices, etc.).
Proper error handling is in place, and meaningful error messages are logged.
Unit and integration tests provide sufficient coverage for common scenarios.
Comprehensive documentation is available for users to easily configure and use the connector.

Resources
NetSuite REST API Documentation
NetSuite SuiteTalk Web Services
NetSuite Token-Based Authentication

[linear]

BE-463 Netsuite: Destination Connector

[aazam-gh]

I'd like to take this issue up!

[Mohith93]

Hi @aazam-gh

I hope you're doing well! I wanted to follow up on this issue, you've been working on.

Could you provide an update on the current status or let me know if you’re facing any challenges? I'm happy to assist or answer any questions you may have.

Thank you for your continued contributions to the project. Your efforts are greatly appreciated, and we’re excited to see your progress!