Tribal - Maytas (Preview)
Streamline the day-to-day administration of training, reduce administration costs and improving efficiency, manage courses, monitor learner success rates
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 | Tribal Group |
| URL | https://www.tribalgroup.com |
| servicedesk@tribalgroup.com |
| Connector Metadata | |
|---|---|
| Publisher | Tribal Group |
| Website | https://www.tribalgroup.com |
| Privacy policy | https://www.tribalgroup.com/privacy-policy |
| Categories | Business Management |
Streamline the day-to-day administration of training, reduce administration costs and improve efficiency, manage courses, monitor learner success rates.
Prerequisites
To use the Tribal - Maytas Connector you will need to be Tribal Edge user for your module of choice.
How to get credentials
To access the Tribal - Maytas Connector you must have a user on your tenant that has permissions to:
- Subscribe to Events
- Perform any actions/queries within Tribal Maytas e.g. if you want to read data you will need read permission
In Power Automate when you create a connection you will be prompted for:
- The type of environment you wish to access i.e. Live, Testing or Development.
- The region that you are in EMEA or APAC
- Your tenant you received upon joining Tribal Edge
Upon entering credentials you will be asked for consent, the below are required
- Events Connector Endpoint
- Connect to the web hooks
Get started with your connector
The purpose of the Tribal - Maytas connector is to allow you integrate with any Power Automate connector and extend the Tribal Edge logic beyond what it can provide internally. The Tribal connector provides triggers to be notified on e.g. an assessor has had details updated and actions that can be performed within Tribal Edge e.g. create a new trainee.
Below highlights 2 common scenarios.
- Use the Excel connector to retrieve rows from an excel spreadsheet hosted in the cloud and use the Tribal create and update actions to populate reference data.
- Use the Tribal connector to listen for if a person has been updated, retrieve details about that person and notify a staff member through the Teams Connector.
Known issues and limitations
- Triggers that are produced via Tribal Edge only continue unique identifiers which need further querying. A separate action to retrieve details, which are protected by permissions, can be performed to find out more.
- Triggers and actions are currently in development, these will become available in the connector as and when they are ready.
Common errors and remedies
- When performing an action, you may get a permissions error. This can be resolved by requesting permissions from your administrator.
Creating a connection
The connector supports the following authentication types:
| Default | Parameters for creating connection. | All regions | Not shareable |
Default
Applicable: All regions
Parameters for creating connection.
This is not shareable connection. If the power app is shared with another user, another user will be prompted to create new connection explicitly.
| Name | Type | Description | Required |
|---|---|---|---|
| Environment | string | Environment | True |
| Region | string | Region | True |
| Edge Tenant Id | string | Tenant Id for Tribal Edge | True |
Throttling Limits
| Name | Calls | Renewal Period |
|---|---|---|
| API calls per connection | 100 | 60 seconds |
Actions
| Create an entity |
Create a specified entity, required and optional inputs will be provided upon choosing your entity |
| HTTP Request |
Send a HTTP request. Headers, verbs and relative URLs need to be provided. |
| Read a collection of entities |
Retrieve a collection of entities of your choice, further optional odata filters can be applied to tailor what is returned. |
| Read an entity |
Retrieve a specific entity of your choice, further optional odata filters can be applied to tailor what is returned. |
| Update an entity |
Update a specified entity, optional inputs will be provided upon choosing your entity. Any inputs not specified will not be included in the change. |
Create an entity
Create a specified entity, required and optional inputs will be provided upon choosing your entity
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
Entity
|
name | True | string |
The name of the entity to post |
|
body
|
body | True | dynamic | |
|
Correlation Id
|
x-correlation-id | string |
Correlation Id added in the x-correlation-id header |
Returns
HTTP Request
Send a HTTP request. Headers, verbs and relative URLs need to be provided.
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
key
|
key | string |
key |
|
|
value
|
value | string |
value |
|
|
Verb
|
verb | True | string |
HTTP Verb |
|
Body
|
body | string |
Body of the request |
|
|
Relative URL e.g. odata/main/trainee
|
relativeUrl | True | string |
Relative URL |
Read a collection of entities
Retrieve a collection of entities of your choice, further optional odata filters can be applied to tailor what is returned.
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
Entity
|
name | True | string |
The name of the entity to read a collection |
|
Filter
|
$filter | string |
OData filter to perform |
|
|
Take
|
$top | integer |
Number of items to take |
|
|
Skip
|
$skip | integer |
Number of items to skip |
|
|
Select
|
$select | string |
Columns to select |
|
|
Expand
|
$expand | string |
Columns to expand |
|
|
Correlation Id
|
x-correlation-id | string |
Correlation Id added in the x-correlation-id header |
Returns
Read an entity
Retrieve a specific entity of your choice, further optional odata filters can be applied to tailor what is returned.
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
Entity
|
name | True | string |
The name of the entity to read |
|
Id
|
id | True | string |
The id of the entity to read |
|
Select
|
$select | string |
Columns to select |
|
|
Expand
|
$expand | string |
Columns to expand |
|
|
Correlation Id
|
x-correlation-id | string |
Correlation Id added in the x-correlation-id header |
Returns
Update an entity
Update a specified entity, optional inputs will be provided upon choosing your entity. Any inputs not specified will not be included in the change.
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
Entity
|
name | True | string |
The name of the entity to update |
|
Id
|
id | True | string |
The id of the entity to update |
|
body
|
body | True | dynamic | |
|
Correlation Id
|
x-correlation-id | string |
Correlation Id added in the x-correlation-id header |
Returns
Triggers
| When an event happens |
This operation triggers when a specified event happens |
When an event happens
This operation triggers when a specified event happens
Parameters
| Name | Key | Required | Type | Description |
|---|---|---|---|---|
|
Name
|
name | True | string |
The name of the event |
|
Event Type
|
eventType | True | string |
The type of event e.g. Updated or Created |