Hello Grist team.
Integration with n8n is very good, but it takes a long time and requires third party services, why not simplify tasks for users?
The idea came up to use REQUEST to request data in another document using https://{subdomain}.getgrist.com/api/docs/{docId}/tables/{tableId}/records
The idea was not bad but it was a trigger formula Authorship columns - Grist Help Center I found only user.UserRef it doesn’t look like a user API key.
Why can’t we get the API key for the current user, because it’s current and it won’t affect security?
On the other hand, what if several values are returned?
In my search I found something tasty _grist_External_database. … Mmm…
