Templates / Sales / Netsuite sales order from Ironclad contract

Netsuite sales order from Ironclad contract

Overview

This workflow creates a Sales order in Netsuite for a contract that is complete in Ironclad.

It is triggered by a workflow_completed action in Ironclad. It then checks if the counterparty has an existing Netsuite Customer record. If not, then a new one is created. Later, using the Netsuite ID, a Sales Order is generated to represent the Contract deal being closed.

The entire process typically requires a higher degree of customization than usual. A typical use case for this template could be where finance teams have required fields and usually have to represent multiple products on each Sales Order. You can customize this template to handle any situation based on your team's requirements.

Connectors Used

The following connectors are used in this template. This is provided for reference only - there is no need to read through the linked connector pages, as all you need to know for this template is explained here:

End Result

The image below shows a Salesoder in Netsuite created for a completed Contract in Ironclad:

end-result

Prerequisites

This workflow assumes the following:

  • You have API Access to Ironclad and Netsuite.

  • You can link Ironclad records to corresponding customers in Netsuite. The default template uses the counterparty name to try a name match to a Netsuite Customer, but another field can be used

  • You do not use a CRM or other tool to manage the sales process (i.e. Ironclad is used to create Sales Orders and not an alternative CRM)

Getting Live

To configure the workflow for your own use:

Workflow logic

create-netsuite-sales-order-when-ironclad-contract-workflow-ends > complete-wf

Implementation notes

Create a List of items to map into Create Sales Order step

In order to create a list of items in the following format, first you need to identify the source from which you may pull the data.

{
"key": "item",
"value": {
"items": [
{
"amount": 15000,
"item": {
"id": "10"
},
"billingschedule": {
"id": "1"
}
},
{
"amount": 0,
"item": {
"id": "13"
},
"billingschedule": {
"id": "1"
}
}
]
}
}

In this example, we are using Google Sheets as a generic placeholder to fetch the item data for any service or database you may wish to use.

Exactly how this is done will depend on the service you are pulling data from.

The key thing here is that the data being sent to Netsuite must be in the exact format as shown, regardless of where it has come from.

format-item-list

Once you have chosen the source of data you may configure your workflow as follows: