@@ -14,7 +14,7 @@ When you define a bip, you are defining the characteristics of a [directed graph
When a message is received from a web hook, incoming email or generated from a trigger, it appears on a bips graph from the 'source' node. The source data is then normalized into a JSON structure and 'exported' via RabbitMQ for consumption as 'imports' by adjacent nodes. This pipeline continues until all nodes have been visited.
A node in a bip usually represents a [Remote Procedure Call](https://en.wikipedia.org/wiki/Remote_procedure_call)(RPC) on an external service and are generally referred to as 'actions'.
A node in a bip usually represents a [Remote Procedure Call](https://en.wikipedia.org/wiki/Remote_procedure_call)(RPC) on an external service, which is a discrete 'action' provided by a 'pod'.
Prior to consumption by an action, imports can be modified in different ways. These modifications are called 'transforms', or ['personalizations'](https://bip.uservoice.com/knowledgebase/articles/502740-personalizing-your-integrations) in the UI. As a message is pushed through a graph, an object is built containing exports from visited nodes which can be plucked out with [JSONPath](http://goessner.net/articles/JsonPath). Using these JSONPath expressions and a simple [templating system](https://github.com/bipio-server/bipio/wiki/Transforms-And-Templates), imports can be composed as you like.
