It really depends on what level of detail you are looking to diagram.
If the detail is very coarse, you might not need to represent the recursion at all. You'd just represent it as a calculation step, with the overall inputs and outputs shown.
At the next finer level of detail, you could perhaps represent it as simple iteration - what I mean is not an exact representation of the algorithm, but something that gives the gist of what it does. You might also find that your use of recursion can be converted to simple iteration anyway - in other words, the algorithm itself can be aligned with an easier diagrammatic representation.
If absolute detail of the recursive nature of the algorithm is required, you'd have to model the existence of a stack, and the iterative fetching and storing of intermediary data in this stack. In other words, making explicit everything that is otherwise implicit in a language that allows recursive calls.