ab544d4f95
* Create readme.md * Create readme.md * Create apiDefinition.swagger.json * Create apiProperties.json * Update readme.md * Create script.csx * Create settings.json * Tulip R1 * New Icon File * Updating icon * Updating icon * Add files via upload * New Icon * Add files via upload * Delete settings.json Not required in public repsository. * Delete icon.png Not required in open source repository * Fixing typos * Delete custom-connectors/Tulip directory Removed because it was in the wrong location * Delete icon.png Saved in wrong location * Updated data type mapping Now covers all data types that are available in Tulip Tables except for linked records. * Added filed mappings and tips for use Added a table to explain the field / variable type mappings between Tulip tables and Power Automate. Explained the requirements for each and tips for use. |
||
|---|---|---|
| .. | ||
| apiDefinition.swagger.json | ||
| apiProperties.json | ||
| readme.md | ||
| script.csx | ||
readme.md
Tulip Connector
The Tulip Connector allows you to integrate with the data in your Tulip Instance. Enxtending your Tulip frontline operations applications into your power automate, Teams and M365 workflows.
Prerequisites
You will need the following to proceed:
- Active Tulip instance and subscription (tulip.co)
- Tulip API bot credentials for your Tulip Account with access to the appropriate scopes. ( Tulip Account or Workspace owner can provide credentials)
Setting up the connector
On initial use, you will need to enter your Tulip Bot Credentials and Tulip Instance URL. This will provide you with the connection between Power Automate and your Tulip Instance. See Adding an API to see how to create a bot in your Tulip instance. Then you will be able to configure the connector within your Power Automate flow. note: if / where using the create record, you will need to create with a unique id
Supported Operations
The connector supports the following operations:
Get Record: Returns a record from a Tulip Table based on a provided record idCreate Record: Creates a new record in a Tulip Table. Note: requires a unique id to be defined. You can use the expression rand(100000000, 99999999) for example.Put Record: Updates a record in a Tulip Table based on provided id and values to update
Managing Field Types
The Tulip fields types are mapped the follow way:
| Tulip Table Field Type | Power Automate Variable Type | Comments |
|---|---|---|
| text | string | none |
| number | number | none |
| integer | integer | none |
| boolean | boolean | none |
| datetime | string | Needs to be a string in the W3 Complete date plus hours, minutes and seconds format : YYYY-MM-DDThh:mm:ssTZD (eg 1997-07-16T19:20:30+01:00) [ref] |
| interval | number | Number of seconds for the interval in number format, will be converted to MM:SS interval format in Tulip table |
| color | object | needs to be an object in the format { "r": number, "g":number, "b": number, "a": number} e.g For black with no transparency { "r":0, "g":0, "b":0, "a":0} [ref] |
| image / file / video | string | String needs to be a valid and accessable URL for the image / video / file |
| user / station / machine | string | needs to be a valid id of a user/ station / machine in the instance you are connected to |
Known Issues & Limitation
- Linked Record Type - The connector is known to be able to handle the creation or updating of linked records.
- Individual Records - Only handling individual table records. Likely to be expanded in the future.
- Duplication of Record ID in Update Record Function - The update record requires two ids, these must be identical. This is due to it being required by the Tulip API in both the path and the body. We are looking for a fix and will update here when it is implemented.