Hello Tulip! Please consider adding this functionality in the software. This is very helpful for email notification. At the moment, the only way around is to include the logged in user in the email notification.
@Beth Hi Beth. Would you mind moving this to the product suggestions? I also need this. In my use case, I wanted to get that information from the expression editor though.
Hey everyone, kind of a broad FYI but don’t forget to checkout the NextGen APIs which Tulip has on their support docs but not in your instance.
You can build this connector function pretty easily.
Thanks a lot for reminding me of this one!
I’ve always found the Tulip API endpoints rather confusing so here is an overview, in case someone is as puzzled as I am.
As far as I know, and as far as the documentation says, Tulip officially provides two APIs, each one having:
- a different URL prefix
- different version numbers
- different capabilities
One is called the Tulip API, the other one is called the Tulip Next-Gen API (often simply Next-Gen API). Very confusingly, the “next-gen” API (which always makes me think it’s a new version of a previous API) has version number 1. Strangely, I’ve never found any trace of a “v2” API.
Both APIs seem to be officially supported and usable with the usual API tokens.
Here is a table comparing the two, with every information I could find as of today:
| Criteria | Tulip API | Tulip “Next-Gen” API |
|---|---|---|
| Documentation location(s) | - https://{instance-name}.tulip.co/apiDocs - https://support.tulip.co/apidocs/introduction-1 |
https://support.tulip.co/apidocs/introduction |
| Base prefix | https://<instance-name>.tulip.co/api/v3/{entity-name} |
https://<instance-name>.tulip.co/api/{namespace}/v1/{entity-name} |
| Workspaced prefix | https://<instance-name>.tulip.co/api/v3/w/{workspace-id}/{entity-name} |
https://<instance-name>.tulip.co/api/{namespace}/v1/w/{workspace-id}/{entity-name} |
| Version number | 3 | 1 |
| Uses namespacing? | no | yes |
| Capabilities | Roughly focuses on shop floor and users: - Create/read/update/Delete stations, station groups and interfaces. - Read user, user groups and roles. |
Roughly focuses on machines and tables: - Read apps, app groups, machines, machine types and machine activity archive status. - Create/read/update/delete table, table records, queries, aggregations and record links. - Create users, machine activity archive, machine attribute values and signed cloud storage URLs. |
I hope this will be useful.
@OlgaStroilova Hi Olga. Any news about this? It’s been roughly 6 years since the first message 
If we consider the users who posted here (18 minus the official Tulip team accounts) and the 11 votes in User names in “Show Message”? - Product Suggestions - Tulip Community, I think this topic definitely deserves more attention. Everyone referred to it in slightly different ways and places which scattered the votes and expressions of interest. Had this issue been posted once and voted for properly, this would be at least a 20-vote product suggestion.
Thanks @fti and others, I’m digging into this and will circle back.