The Celigo flow is between Shopify and NetSuite. We can restrict mapping of fields using Celigo. Follow the procedure to map fields only when record is updated. To perform mapping of email field only when email is updated, click on the settings option 2. Select advanced option and select updating a record from the drop… Continue reading Restrict mapping of fields using Celigo
Category: Celigo
How can restrict the updations in the Fields of Shopify using Celigo
Celigo flow is between the NetSuite and Shopify. We can restrict the updations in the fields of the Shopify. when a record is created in the NetSuite and run the flow. Then the value will set in the Shopify. After the creation, any updations happened it will not affect the fields. Please follow the below… Continue reading How can restrict the updations in the Fields of Shopify using Celigo
How to add Inventory HandleBars in NetSuite- Wafair custom flow.
How to add Inventory HandleBars in NetSuite- Wafair custom flow.
Error when updating metafields on a product using Celigo Flow
Error {“errors”:{“key”:[“must be unique within this namespace on this resource”]}} Solution You can use the Product API to update or create a metafield when you call PUT /products/PRODUCT_ID.json But after you save a product you don’t get the metafields, so you need to call first /metafields.json?metafield[owner_id]=PRODUCT_ID&metafield[owner_resource]=product
Error in Customer flow, unable to add new Shopify customer to NetSuite.
Error: Multiple matches were found for customer record with criteria: [[“email”,”is”,”test@gmail.com”],”AND”,[“custentity_celigo_shopify_store”,”is”,”@NONE@”]]. Please use different secondary lookup criteria and try again. Solution: Check if there are multiple customer records in NetSuite for test@gmail.com. To resolve this, t’s either you need to make sure that there’s no duplicate customer record in NetSuite with email address or you… Continue reading Error in Customer flow, unable to add new Shopify customer to NetSuite.
MY API
My API is a custom HTTP endpoint used by client applications to execute scripts in integrator.io. 1. Calls to My API endpoints trigger a script inside the integrator io platform. 2. The script then implements logic to invoke flows, exports, and imports. 3. The script handles the request and returns a response back to… Continue reading MY API
UNIVERSAL CONNECTORS
Universal connectors allow you to connect data with applications that do not have a pre-built connector within integrator.io. When to use a Universal Connector: A prebuilt connector, also known as an application-specific connector, is not available for the application you want to integrate. When a recent API update is not accounted for by an… Continue reading UNIVERSAL CONNECTORS
Types of Universal Connectors in Celigo
HTTP The HTTP(S), HyperText Transfer Protocol (secure), allows you to connect to another server. In integrator.io, you will use HTTP(s) connections to provide credentials and perform requests to different cloud applications that expose an API based on HTTP(s) standards. REST API REST API, REpresentational State Transfer, is an API that conforms to the design principles of… Continue reading Types of Universal Connectors in Celigo
HTTP CONNECTOR
Creating a connection with the HTTP connector is more complex than configuring a connection with a pre-built connector because it requires more customization. Base URI is a component of configuring an HTTP connection. As we continue to configure HTTP connectors, exports, and imports you will be asked to identify the relative URI. Base URI: The starting… Continue reading HTTP CONNECTOR
Export vs. Import in Celigo
Export An export is a flow step that retrieves data from an application. A flow can have multiple export steps, but any complete flow must include at least one export, data loader, or webhook listener flow step. Start creating an export from a source application in either of the following ways: From the Tools menu, select Flow builder. Then, click Add source.– or… Continue reading Export vs. Import in Celigo