Adding Custom Metadata to Actions invoked via API
T
Tom Mizrahi
Currently invoking actions via API only allows to add "properties" (inputs) under the payload.
We'd like to have the ability to add metadata information.
For example with like to impersonate the API action request as if it was coming from a specific user (rather from the owner of the token).
Gur Shafriri
While we consider adding additional context to the action in a more native way, there is currently another way to do this via advanced input configurations (see docs) - by adding a hidden entity input and set a default entity.
See this property definition for example:
"impersonated_user": {
"format": "entity",
"type": "string",
"title": "Impersonated User",
"blueprint": "_user",
"default": "<email of impersonated user>"
"visible": false
{
This property will not be shown in the self-service form and will make the full entity details of the specific user you requested available when configuring the action payload. This specific example depends on having users as blueprint, but can be implemented with any blueprint.
If needed, you can also set this default dynamically using JQ and will make the full entity details of
Matan Grady
Merged in a post:
Adding Custom Metadata to Actions invoked via API
T
Tom Mizrahi
Currently invoking actions via API only allows to add "properties" (inputs) under the payload.
We'd like to have the ability to add metadata information.
For example with like to impersonate the API action request as if it was coming from a specific user (rather from the owner of the token).