| ... | ... | @@ -13,12 +13,11 @@ Templates can also be interpolated with variables from upstream channels or meta |
|
|
|
|
|
|
|
`[%(source|channel id)#export_attribute%]`
|
|
|
|
|
|
|
|
"export attribute" in the example means the name of an attribute exported by an upstream channel, keyed by either an explicit channel id, or `source` (ie: whatever the bip receives or generates).
|
|
|
|
|
|
|
|
For example `[%source#subject%]`. This means you can concatenate exports together to create an import, and include your own text :
|
|
|
|
"export attribute" in the example means the name of an attribute exported by an upstream channel, keyed by either an explicit channel id, or `source` (ie: whatever the bip receives or generates). This means you can concatenate exports and text together to create a custom import. With the previous email example, lets assume we're using an `smtp` bip and want to pass through some of the details to an email channel on its hub :
|
|
|
|
|
|
|
|
```
|
|
|
|
{
|
|
|
|
"body_text" : "I got an email from [%_client#repr%] with the subject [%source#subject%]!!"
|
|
|
|
"subject" : "[%source#subject%]",
|
|
|
|
"body_text" : "I got an email from [%_client#repr%] : [%source#body_text%]"
|
|
|
|
}
|
|
|
|
``` |
|
|
\ No newline at end of file |
