By default, the integrator.io NetSuite connection communicates via custom RESTlets in the Celigo integration bundle. However, you can route your connection to a different NetSuite RESTlet by specifying HTTP headers in integrator.io API exports or imports, acting as a proxy for requests to your NetSuite connection.
Contents
Setup
A. Configure your NetSuite connection
First, create or edit a standard NetSuite connection. Record the connection ID at the end of the URL for use below as the NetSuite connection ID.
B. Establish an integrator.io (application) connection
Next, set up an integrator.io connection. Note that integrator.io API tokens last for only one hour, unless your account has the API Management feature enabled.
C. Retrieve RESTlet parameters
Before you can interact with the RESTlet, you must get the Script ID and Deployment ID from the NetSuite script record.
Export (read) from a RESTlet
In Flow Builder, create an export to the application integrator.io, selecting the integrator.io connection that you just created. Define the export as follows:
Name: Give the export a name.
Form view: Choose REST API.
HTTP method: Choose POST.
Headers:
| name | suggested value |
| Integrator-NetSuite-ScriptId | The Script ID from above |
| Integrator-NetSuite-DeployId | The Deployment ID from above |
| Integrator-Method | The method to use with your RESTlet call, most likely GET for an export |
Relative URI: Enter the proxy URI for your NetSuite connection, referencing your NetSuite connection ID that you copied above, in the format, /v1/connections/<id>/proxy.
HTTP request body: Enter an empty JSON object, {}.
Export type: Choose All.
Click Preview to see your RESTlet data.
Import (write) to a RESTlet
In your flow, create an import using the integrator.io application and the connection to it that you built earlier. Define the import as follows:
Name: Give the import a name.
Form view: Choose REST API.
HTTP Method: Choose POST.
Headers:
| name | suggested value |
| Integrator-NetSuite-ScriptId | The Script ID from above |
| Integrator-NetSuite-DeployId | The Deployment ID from above |
| Integrator-Method | The method to use with your RESTlet call, most likely POST for an import |
Relative URI: Enter the proxy URI for your NetSuite connection, referencing your NetSuite connection ID that you copied above, in the format, /v1/connections/<id>/proxy.
Now, within this import the integrator.io connection functions like any other REST connection. You can specify a request body in the HTTP request body setting, or you can use regular field mapping. If you go with the latter, you can provide a sample request under Do you have a sample destination record? in the import settings to make mapping easier.
Comments
2 comments
I've been unable to figure out how to pass parameters to the RESTlet. I've tried adding them to the HTTP headers, to the request body and to the URL as params. My RESTlet isn't seeing any of the parameters.
Is it possible?
Hi, Steve Klett. Thanks for sharing your results here.
If you haven't tried this yet, as a start, can you turn on connection debugging and verify that the parameters are getting sent correctly from the integrator․io side?
My next suggestion would be to share your NetSuite screens and flow in Partner Office Hours, and you can get some real-time analysis of why the values are not getting passed.
Please sign in to leave a comment.