Setting up Workato sync to connect BigQuery and NetSuite

1. Prerequisites

Before you start, ensure you have:

  • Workato Account with access to Google BigQuery and NetSuite connectors.
  • Google BigQuery Project with service account credentials (.json file).
  • NetSuite Integration Role with Web Services and REST API permissions.

2. Connect Workato to BigQuery

  1. Go to: Apps in Workato.
  2. Click New Connection and select Google BigQuery.
  3. Choose OAuth 2.0 or upload the Service Account JSON.
  4. Select the BigQuery Dataset containing customer data.

3. Connect Workato to NetSuite

  1. In Apps, add NetSuite as a new connection.
  2. Choose SuiteTalk (SOAP) or REST API.
  3. Enter:
  • NetSuite Account ID (XXXXX_SB1 for Sandbox).
  • Consumer Key & Secret (from NetSuite Integration setup).
  • Token ID & Secret (generated for the Workato role).
  1. Click Connect.

4. Create Workato Recipe (BigQuery → NetSuite)

  1. Go to Recipes → Click New Recipe.
  2. Choose Trigger: Google BigQuery
  • Trigger Type: “New Row in Table” (or “Updated Row”).
  • Table: Select the Customer Data Table.
  1. Add Action: Search NetSuite Customer
  • Search by Email or External ID.
  • If found, Update the customer record.
  • If not found, Create a new customer.

Example: Updating Customer Record

  • Fields from BigQuery → NetSuite Mapping:BigQuery FieldNetSuite Fieldcustomer_identityid (External ID)customer_namecompanyNameemailemailphonephoneaddressaddress1citycitystatestatezip_codezip

5. Add Error Handling & Logging

  • Use a “Monitor Failed Jobs” step to catch errors.
  • Log failed records in Google Sheets or Slack.
  • Optionally, send alerts via Slack or Email.

6. Test the Integration

  1. Add a Test Customer in BigQuery.
  2. Run the Workato recipe.
  3. Check if the customer appears in NetSuite (Lists > Relationships > Customers).

7. Schedule or Automate the Sync

  • Run every 15 minutes or hourly for real-time updates.
  • Use batch processing for large datasets.

Leave a comment

Your email address will not be published. Required fields are marked *