inQuba Journey (Preview)
Seamlessly publish data to the inQuba Customer Journey APIs and effectively track your customer journeys.
This connector is available in the following products and regions:
| Service | Class | Regions |
|---|---|---|
| Logic Apps | Standard | All Logic Apps regions except the following: - Azure Government regions - Azure China regions - US Department of Defense (DoD) |
| Power Automate | Premium | All Power Automate regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD) |
| Power Apps | Premium | All Power Apps regions except the following: - US Government (GCC) - US Government (GCC High) - China Cloud operated by 21Vianet - US Department of Defense (DoD) |
| Contact | |
|---|---|
| Name | inQuba Support |
| URL | https://inquba.com |
| support@inquba.com |
| Connector Metadata | |
|---|---|
| Publisher | Inquba Customer Intelligence Pty Ltd |
| Website | https://inquba.com/ |
| Privacy policy | https://www.inquba.com/data-privacy/ |
| Categories | Data;Communication |
The inQuba Journey Connector allows for seamless integration between your existing systems and the inQuba Journey platform. Easily send data through the connector to quickly visualize your customer journeys and gain insights into what your customers are saying and doing. The connector offers easy to use REST APIs that allow you to publish customer journeys and events that are consumed by the inQuba platform.
Prerequisites
You will need the following in order to utilize the inQuba Journey Connector:
- A registered inQuba Journey Instance deployed
- An active Azure subscription
- A Microsoft Power Apps or Power Automate plan with custom connector feature;
You may purchase a subscription by visiting the Azure Market place or by visiting the inQuba website and contacting sales.
How to get credentials
Authorization is required on all inQuba APIs. Once you have completed the inQuba registration process, please contact your account manager or inQuba Support to obtain your API credentials. These credentials will then be used on the Journey connector for all API operations.
Get started with your connector
The inQuba Journey Connector requires authorization for all actions. Please always start with using the "Acquire Access Token" action before using the "Create Event" or "Create Transaction" actions.
Retrieve your event or transaction attribute definitions and credentials from inQuba. These attribute definitions will indicate the required attributes for interacting with your customers or tracking their customer journeys. You may contact your account manager or inQuba Support for the relevant definitions and credentials.
Use your provided details in the Acquire Access Token action:
Use either the Create Event or Create Transaction action. Please use dynamic content from the Acquire Access Token action to update the 'Authroization Token' field. Please add the value 'Bearer ' and then select Dynamic content using the Authorization Token value from the previous step as shown below.
Thereafter you may fill out out the required details on the action's form and may proceed to integrate with the inQuba platform.
An example of a popular flow using Dynamics is shown below. The flow below triggers when a flow step is executed in Dynamics:
Known issues and limitations
The create event and create transaction API currently only support single event and transaction payloads per request. For multiple events and transactions it is recommended to initiate many iterated requests.
Common errors and remedies
Response contains a HTTP 401 error
Please verify that your credentials are correct and match the supplied credentials as provided by inQuba. You may contact inQuba Support to verify your credentials.
Response contains a HTTP 404 error
Please ensure you are using the correct tenant name and host URL as provided by inQuba. You may contact inQuba Support to verify your tenant name.
Response contains a HTTP 500 error
Please ensure your event or transaction attributes array is correctly defined by either using the attributes array input or verifying the raw attributes are correct. You may contact inQuba Support to verify your configuration.
FAQ
How many requests can I send using the event or transactions endpoint? There is no hard limit on the number of requests that can be sent however processing of journeys and events are limited by your paid for subscription tier. Subscription pricing can be found here.
Where can I find the Open API definitions for events and transactions? Swagger documentation is available for the Events and Transactions API.
Are non production endpoints available for testing? Yes. Please contact your account manager or inQuba Support to obtain your test credentials.
What data sources does the connector support? The connector supports any data sources that can be used within Power Automate. You may add the connector as a step to any flow you configure.
Throttling Limits
| Name | Calls | Renewal Period |
|---|---|---|
| API calls per connection | 100 | 60 seconds |
Actions
| Acquire Access Token |
Authenticate with the inQuba API and receive an authorization token that will be used for all API interactions. |
| Create Event |
Publish an event record to the inQuba API. A bearer token is required to interact with the API. |
| Create Transaction |
Publish a transaction to the inQuba Journey API. A bearer token is required to interact with the API. |
Acquire Access Token
Authenticate with the inQuba API and receive an authorization token that will be used for all API interactions.
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
Tenant Name
|
TenantName | True | string |
Name of Tenant as registered with inQuba. |
|
Host URL
|
HostURL | True | string |
Host of Token endpoint must be supplied without scheme name. Eg. api.inqubacx.com |
|
Username
|
username | True | string |
Account Username as supplied by inQuba. |
|
Password
|
password | True | string |
Account Password as supplied by inQuba. |
|
Client ID
|
client_id | True | string |
Client ID as supplied by inQuba. |
|
Client Secret
|
client_secret | True | string |
Client Secret as supplied by inQuba. |
Returns
| Name | Path | Type | Description |
|---|---|---|---|
|
Authorization Token
|
access_token | string |
Authorization token that will be used for all API interactions. |
Create Event
Publish an event record to the inQuba API. A bearer token is required to interact with the API.
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
Tenant Name
|
TenantName | True | string |
Name of Tenant as registered with inQuba. |
|
Authorization Token
|
AuthorizationToken | True | string |
Authorization Token for authorizing the API request to inQuba. |
|
Event Definition Code
|
eventDefinitionCode | string |
The event code you are publishing this request for. |
|
|
Is Test
|
isTest | boolean |
A flag indicating whether or not this event should be published as test or live. |
|
|
Code
|
code | string |
Event Attribute Code |
|
|
Value
|
value | string |
Event Attribute Value |
Returns
- SuccessStatus
- string
Create Transaction
Publish a transaction to the inQuba Journey API. A bearer token is required to interact with the API.
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
Tenant Name
|
TenantName | True | string |
Name of Tenant as registered with inQuba. |
|
Authorization Token
|
AuthorizationToken | True | string |
Authorization Token for authorizing the API request to inQuba. |
|
Transaction Definition Code
|
transactionDefinitionCode | string |
The transaction code you are publishing this request for. |
|
|
Is Test
|
isTest | boolean |
A flag indicating whether or not this transction should be published as test or live. |
|
|
Code
|
code | string |
Transaction Attribute Code |
|
|
Value
|
value | string |
Transaction Attribute Value |
Returns
- SuccessStatus
- string
Definitions
string
This is the basic data type 'string'.