Field Mapping for IR import is as follows: Data.ReferenceNo – Created From(InternalId) “true” – Items:Replace All Lines Data.Items[*].ItemNumber – Items: Item(Field ID: itemname) Data.Items[*].ReceivedQuantity – Items: Quantity location(hardcoded value) – Items:To Location(InternalId)
Category: Celigo
Response mapping in Celigo
In Celigo we can map the response data in the destination fields. Let’s say I need to map a http response of WISEPOID after a successful import of Purchase Order to UNIS (or any other e-commerce site). Create a custom field in the destination Record where you want the data to store in. After the… Continue reading Response mapping in Celigo
Return a response code from Webhook listener
integrator.io returns a 204 HTTP status code for all successful webhook requests by default. There can be situations when the requested platform expects a response code other than 204. In such cases we can select an alternate successful HTTP status code for the listener. Edit the webhook listner Click on the Advanced option. Click Override… Continue reading Return a response code from Webhook listener
Error Categories in Celigo
Configure refresh token in HTTP connection
Refresh token can be set up by giving the following Refresh token (required): Enter a token that can serve as a refresh expired auth token. You can place this token in the body, headers or URL simply by referencing it with the handlebars placeholder {{connection.http.auth.token.refreshToken}}. Multiple layers of protection, including AES 256 encryption, are in place to… Continue reading Configure refresh token in HTTP connection
Secret URL Verification type in Celigo Webhook Connection
Celigo’s webhook listener typically supports secret URL verification as a security measure to ensure that webhook endpoints are legitimate and owned by the intended recipient. This process involves including a secret key or token in the URL, and the webhook listener verifies this secret before accepting requests. Here’s a general overview of how you might… Continue reading Secret URL Verification type in Celigo Webhook Connection
Setting up Http connection in Celigo
A. Set up an HTTP connection Start establishing the universal, or generic, HTTP connection in either of the following ways: Select Connections from the Resources menu. Next, click + Create connection at the top right. In the resulting Create source panel, select HTTP from the Application list, under the Universal connectors group. While working in a new or existing integration, you can add an application to a flow simply by… Continue reading Setting up Http connection in Celigo
Error Classifications in Celigo
Value Sample error messages Typical cause Invalid phone value: remove dashes The value provided causes a specific problem Order status == cancelled in target system. Target system rejects all updates An unexpected value prevents any changes to the record in the destination system Transaction was declined by processor. Issuer Declined Cannot change status field The… Continue reading Error Classifications in Celigo
Depreciation of REST API Connectors
The REST API connector is being deprecated. A better alternative, with similar functionality and additional settings, is the universal HTTP connector. While the REST API connector still appears in the + Create Connection pane, it now automatically defaults to the HTTP connector. Existing REST connections are still available and are not affected by the change. However, you can’t… Continue reading Depreciation of REST API Connectors
Configure Item Aliases for the Amazon Integration App
Problem: I have multiple Amazon items that are all the same NetSuite items. Solution: Configure a workaround called the ‘Item Alias Functionality’ as shown below. In the Amazon Integration App, go to Settings > Order section > General tab, check the Item aliases are configured in NetSuite checkbox. The following configuration is needed for the item record in NetSuite:… Continue reading Configure Item Aliases for the Amazon Integration App