About the Aha! category

o.plokha · September 26, 2024, 10:31am

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

Extra information

System documentation: Aha! API Reference

Connector package documentation

1. Setting up HTTP Client Aha!

1.1 Steps

In the Alumio Dashboard, go to Clients → HTTP Clients. Create a new HTTP Client.
Select Aha! HTTP Client as PlatForm and click next step
Fill in the Base URI, Token URL, Authorize URL, Client ID and Client Secret.
(See the Aha! Authentication Documentation for more information)
Click on “Grant access to Aha!” and you will be redirected to Aha! website to get the key for the client.
You can optionally enable logging of request to get the log of the authentication.
Click next step, fill the name of the HTTP Client and finally you can save the HTTP Client for use.

2. Subscribing to Entities from Aha!

2.1 Steps

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

2.2 General Concept

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

Entity

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

Request Parameters

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

Please look at the example below on how to fill path field when we want retrieve list comments by subscribing “Comments API - List comments on a goal” entity.

From the end point, we can see that we need to set the goal id as parameters. That is why we set the “goal_id” inside the path key in the Request Parameters.

Alumio will then make a request to Aha! with the URL /api/v1/goals/7416189478687263166/comments

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

HTTP Client

The HTTP Client configuration you will use to access Aha!.

3. Publishing Entity to Aha!

3.1 Steps

Go to Connections → Outgoing, create a new outgoing configuration and select “Aha! Publisher” as the publisher.
Select the Method that you want the publisher to perform with the data.
Select the Aha! entity you want the data to be published to.
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.

Method

Currently, we support HTTP Post method, HTTP Put method and HTTP Delete method on submitting data to Aha!.

Entity

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

For example, we want to update a product. Please select “Put” as the Method and “Products API - Update a product”.

From the documentation, we can see that we need to set a path parameter and a body parameters. That is why we set the “id” inside the path key and body parameters inside the payload key in the data.

Alumio will send an API request to Aha! with URL /api/v1/products/7416573148990007139

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.