About the Kustomer category

anon99371720 · September 21, 2022, 11:12am

Put topics about this connector package here.
Always check the ‘How to use the Alumio connector packages’ topic.

Extra information

System documentation: Kustomer API Reference

Connector package documentation

1. Setting up HTTP Client Kustomer

1.1 Steps

In the Alumio Dashboard, go to Clients → HTTP Clients. Create a new HTTP Client and select Kustomer HTTP Client as the HTTP Client.
Fill in the Base URI, and Bearer Token.
(For more information, see Kustomer Authentication Reference)
You can optionally enable logging of request to get the log of the authentication.
Save the HTTP Client for use.

2. Subscribing to Entities from Kustomer

2.1 Steps

Go to Connections → Incoming and create a new incoming configuration and select Kustomer Subscriber as the subscriber.
Select the entity you want to subscribe to from Kustomer.
Add any request parameters needed to subscribe to the entity.
You can optionally add a transformer to transform the request parameters into something you will request from Kustomer.
Select the Kustomer HTTP Client to use.
You can also optionally enable pagination to allow Alumio fetches paginated entities.

2.2 General Concept

We follow Kustomer documentation on building this connector, so you can easily use the connector based on Kustomer API Reference.

HTTP Client

The HTTP Client configuration you will use to access Kustomer.

Entity

The entity you want to subscribe to Kustomer. Please refer to the entities from Kustomer API Reference page.

Request Parameters

These are the parameters you can provide to get the needed entity based on the Kustomer API Reference.

Please look at the example below on how to fill path field when subscribing “Get attachments by ID” entity.

Based on the documentation, we can see that the end point require “id” as a path. That is why we set the “id” inside the path key in the Request Parameters.

Path is the path parameter of the url. For example the {id}.
Query is defined set of parameters attached to the end of a url.
Example: www.url.com?type=true&start=0

Alumio will then make a request to Kustomer with the URL /v1/attachments/123

3. Publishing Entity to Kustomer

3.1 Steps

Go to Connections → Outgoing, create a new outgoing configuration and select Kustomer Publisher as the publisher.
Select the Action that you want the publisher to perform with the data.
Select the Kustomer entity you want the data to be published to.
You can optionally add any path data to the request on the key path.
You can optionally add any query data to the request on the key query.
You can optionally add any payload data to the request on the key payload.
Select the HTTP Client to use.

3.2 General Concept

Like the subscriber, the publisher has similar methods on how to use it. The difference is the payload that will be submitted by the publisher originating from the data (from routes, from transformers in outgoing configuration), though you can also add or modify payload using the Request Transformer.

Action

Currently, we support Create (HTTP POST method), Put (HTTP PUT method), Patch (HTTP PATCH method), and Delete (HTTP DELETE method) on submitting data to Kustomer.

Entity

We support publishing to most Kustomer endpoints.
Please refer to Kustomer API Reference page.

For example, we want to use “Delete Klass”. Please select “Delete” as the Action and “Delete Klass” as the entity of the publisher.

Based on the documentation, we can see that the end point require “id” as a path. That is why we set the “id” inside the path key in the data.

Alumio will send an API request to Kustomer with URL /v1/klasses/123

Path is the path parameter of the url. For example the {id}.
Query is defined set of parameters attached to the end of a url.
Example: www.url.com?type=true&start=0
Payload is the data contained within a request.