For HTTP tasks inside plans, you can add references to metadata from the plan itself. Using contextual information from the plan, relevant flows or other HTTP tasks, you can augment the information reported from the webhook.
If you are learning about Plans and how to use them, check out this article first.
General Syntax
All references can be entered with
$in the Trifacta application.Nodes in the tree are separated with a
.period
All plan metadata references follow the following basic syntax:
|
Reference values that contain whitespace must be listed in the following manner:
|
Note that this has type-ahead functionality. So you can begin by entering $ sign and follow the suggestions of what possible references to use as you type ahead.
$plan References
These references apply to the plan definition or current plan run.
Text to enter:
|
You can follow that up with different attributes like name, duration, startTime, runId, user, taskCount etc. To learn more, read this article.
$http References
These references apply to HTTP tasks in the plan run.
Enter the following, after which you can see the two-letter codes for the HTTP tasks that have already executed in the current plan run:
|
You can follow that up with name, status, duration, statusCode etc.
For a complete list of http references you can use, check out this detailed documentation guide.
Response references
These references apply to the response returned as part of the task execution.
Enter the following, after which you can see the two-letter codes for the HTTP tasks that have already executed in the current plan run:
|
The response references you can use are body, json and headers.
$flow References
These references apply to flow tasks in the plan run.
Enter the following, after which you can see the two-letter codes for the HTTP tasks that have already executed in the current plan run:
|
To learn more, read this detailed article.
Specifying metadata references in your http task